2a02:c6c1:e::/48
At a glance
Subnets
/48 block
Visibility
63 of 63 vantage points
RPKI
Registry
GBAllocated 25th September 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS58061seen on 962 paths from 139 vantage points
- Peer of AS200590seen on 7,012 paths from 126 vantage points
- Peer of AS9198seen on 119,016 paths from 135 vantage points
- Peer of AS12389seen on 412,266 paths from 105 vantage points
- Peer of AS6939seen on 303,328 paths from 6 vantage points
LV
KZ
RU
US
FROne 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
- London, UK5806120059035168321635280This path
- Amsterdam5806120059091981238969398298This path
- Sao Paulo58061200590919812389693935280Shown above
- Singapore580612005909198123896939132337This 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 63 of 63 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 Kingdom
- Allocated
- 25th September 2012
- Allocation block
- 2a02:c6c0::/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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a02:c6c0::/29 | 34.4B × /64 | AS58061Scalaxy B.V. | 63/63 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a02:c6c1:f::/48 | 65.5k × /64 | AS29802HIVELOCITY, Inc. | 62/63 |
History
- AS5806112th 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.