2a14:7580:a01::/48
At a glance
Subnets
/48 block
Visibility
58 of 62 vantage points
RPKI
Registry
USAllocated 12th January 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS203923seen on 357 paths from 62 vantage points
- Peer of AS151338seen on 893 paths from 142 vantage points
- Peer of AS51847seen on 2,604 paths from 109 vantage points
- Peer of AS22981seen on 2,667 paths from 109 vantage points
- Peer of AS3491seen on 48,528 paths from 30 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
GB
HK
DEOne 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
- Singapore203923151338138997132337This path
- Amsterdam203923151338518472298134916939213151Shown above
- London, UK20392315133851847229813491900251907This path
- Sao Paulo20392315133851847229813491676232590This 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
94%
Seen by 58 of 62 full-feed vantage points
Globally propagatedObserved at 4 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
- United States
- Allocated
- 12th January 2024
- Allocation block
- 2a14:7580::/29
- 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
No prefix of the same length in the same parent block is announced.
History
- AS20392312th August 2026 — present
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.
Routing data derived from RouteViews MRT archives and public registry data.