2001:dce:d453::/48
At a glance
Subnets
/48 block
Visibility
60 of 62 vantage points
RPKI
Registry
NZAllocated 19th June 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS45285seen on 259 paths from 139 vantage points
- Peer of AS45809seen on 303 paths from 50 vantage points
- Peer of AS9790seen on 21,637 paths from 92 vantage points
- Peer of AS9507seen on 8,765 paths from 69 vantage points
- Peer of AS9002seen on 4,831 paths from 1 vantage point
AU
GB
DEOne 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, UK45285458095585051907This path
- Singapore452854580955850132337This path
- Sao Paulo452854580955850719532590This path
- Amsterdam4528545809979095079002213151Shown 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
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
- APNIC — Asia-Pacific
- Country
- New Zealand
- Allocated
- 19th June 2006
- Allocation block
- 2001:dce::/32
- Status
- assigned
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2001:dce:d452::/48 | 65.5k × /64 | AS38064InternetNZ (.nz tld) | 1/62 |
| 2001:dce:d452::/48 | 65.5k × /64 | AS45285InternetNZ (.nz tld) | 60/62 |
History
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.