2a14:7580:fffd::/48
At a glance
Subnets
/48 block
Visibility
3 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 London, UK.
Seen from London, UK
- Peer of AS203975seen on 3 paths from 3 vantage points
- Peer of AS152698seen on 144 paths from 141 vantage points
- Peer of AS63969seen on 10,335 paths from 142 vantage points
- Peer of AS58715seen on 11,572 paths from 142 vantage points
- Peer of AS9498seen on 121,884 paths from 140 vantage points
- Peer of AS6461seen on 13,835 paths from 2 vantage points
- Peer of AS3303seen on 93 paths from 1 vantage point
- Peer of AS8758seen on 93 paths from 1 vantage point
- Peer of AS211452seen on 162 paths from 19 vantage points
BD
IN
CHOne 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.
Route visibility
5%
Seen by 3 of 62 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- AS20397512th 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.