192.253.254.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 11th March 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS205960seen on 1,811 paths from 76 vantage points
- Peer of AS138195seen on 6,877 paths from 76 vantage points
- Peer of AS138415seen on 5,979 paths from 91 vantage points
- Peer of AS17476seen on 11,771 paths from 75 vantage points
- Peer of AS3257seen on 225,174 paths from 52 vantage points
- Peer of AS1299seen on 380,949 paths from 2 vantage points
HK
KR
SE
AEOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- Amsterdam205960138195138415174763257250918298This path
- London, UK20596013819513841517476325712998529Shown above
- Sao Paulo205960138195138415174763257645335280This path
- Singapore205960138195138415174763257335623673This path
- Oregon, US2059601381951384151747632571299855142013This path
Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.
Route visibility
100%
Seen by 76 of 76 full-feed vantage points
Globally propagatedObserved at 5 of our collectors.
What this percentage counts
The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.
It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.
Registry and RPKI
- RIR
- ARIN — North America
- Country
- United States
- Allocated
- 11th March 2013
- Allocation block
- 192.253.240.0/20
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 192.253.255.0/24 | 256 | AS9009M247 Europe SRL | 75/76 |
History
Why these dates start where they do
A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.
Open 192.253.254.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.