2a10:ccc1:485::/48
At a glance
Subnets
/48 block
Visibility
2 of 64 vantage points
RPKI
Registry
CHAllocated 1st April 2021
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 AS20473seen on 55,079 paths from 142 vantage points
- Peer of AS3491seen on 105,091 paths from 63 vantage points
- Peer of AS1299seen on 34 paths from 4 vantage points
- Peer of AS15412seen on 1,168 paths from 8 vantage points
- Peer of AS15802seen on 18,483 paths from 83 vantage points
- Peer of AS8966seen on 52,869 paths from 6 vantage points
US
HK
SE
GB
AE
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, UK20473349112991541215802896635280Shown above
- Sao Paulo20473349112991541215802896635280This 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
3%
Seen by 2 of 64 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
- Switzerland
- Allocated
- 1st April 2021
- Allocation block
- 2a10:ccc0::/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
- AS2047312th November 2026 — present
- AS204738th November 2026 — 8th November 2026
- AS204737th November 2026 — 7th November 2026
- AS204731st November 2026 — 1st November 2026
- AS2047318th October 2026 — 19th October 2026
- AS2047314th October 2026 — 14th October 2026
- AS2047327th September 2026 — 6th October 2026
- AS2047324th September 2026 — 24th September 2026
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.