2a14:7580:fffe::/48
At a glance
Subnets
/48 block
Visibility
60 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 AS204874seen on 139 paths from 139 vantage points
- Peer of AS52041seen on 153 paths from 69 vantage points
- Peer of AS32097seen on 6,775 paths from 127 vantage points
- Peer of AS174seen on 147,033 paths from 3 vantage points
- Peer of AS15576seen on 442,038 paths from 2 vantage points
GB
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.
Every path we see
- Amsterdam2048745204132097325734549213151This path
- London, UK20487452041320971741557651907Shown above
- Sao Paulo2048745204132097174719532590This path
- Singapore204874520413209712996939132337This 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
97%
Seen by 60 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
- 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 |
|---|---|---|
| 2a14:7580:fffe::/48 | AS204874 | /48 |
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 |
|---|---|---|---|
| 2a14:7580:ffff::/48 | 65.5k × /64 | AS204603LOWPINGS DIGITAL SERVICES S.R.L | 60/62 |
History
- AS20487412th 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.