86.54.5.0/24
AS51202 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
Allocated 12th May 2005
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS203442seen on 138 paths from 138 vantage points
- Peer of AS51202seen on 1,062 paths from 38 vantage points
- Peer of AS20562seen on 1,970 paths from 1 vantage point
- Peer of AS8551seen on 1,077,043 paths from 1 vantage point
One 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
- Amsterdam203442512028298This path
- London, UK2034425120269398529This path
- Singapore203442512023389123673This path
- Sao Paulo2034425120250263291435280This path
- Oregon, US2034425120220562855142013Shown above
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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
Germany
- Allocated
- 12th May 2005
- Allocation block
- 86.54.4.0/23
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 86.54.5.0/24 | AS203442 | /24 |
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 |
|---|---|---|---|
| 86.54.4.0/24 | 256 | AS60742dawox GmbH | 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 86.54.5.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.