2a02:ee80:422c::/48
At a glance
Subnets
/48 block
Visibility
11 of 65 vantage points
RPKI
Registry
NLAllocated 4th December 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS3573seen on 22 paths from 11 vantage points
- Peer of AS42652seen on 4,761 paths from 147 vantage points
- Peer of AS8899seen on 131 paths from 3 vantage points
- Peer of AS8455seen on 23,764 paths from 7 vantage points
- Peer of AS51088seen on 27,685 paths from 2 vantage points
US
DE
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
- London, UK3573426528899896635280This path
- Sao Paulo3573426528899896635280This path
- Singapore35734265288998966132337This path
- Amsterdam35734265288998455510888298Shown above
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
17%
Seen by 11 of 65 full-feed vantage points
Seen by few vantage pointsObserved 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
- Netherlands
- Allocated
- 4th December 2012
- Allocation block
- 2a02:ee80::/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:ee80:422c::/47 | 131k × /64 | AS3573Accenture LLP | 11/65 |
| 2a02:ee80::/32 | 4.3B × /64 | AS3573Accenture LLP | 63/65 |
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
- AS357312th 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.