122.56.114.0/24
At a glance
Addresses
/24 block
Visibility
82 of 82 vantage points
RPKI
Registry
NZAllocated 1st November 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS9325seen on 82 paths from 82 vantage points
- Peer of AS4771seen on 40,869 paths from 147 vantage points
- Peer of AS4648seen on 25,263 paths from 66 vantage points
- Peer of AS1299seen on 341,426 paths from 5 vantage points
- Peer of AS25091seen on 667,091 paths from 2 vantage points
SE
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
- Sao Paulo93254771464835280This path
- London, UK932547714648129935280This path
- Singapore932547714648335623673This path
- Oregon, US932547714648693920130This path
- Amsterdam9325477146481299250918298Shown 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
100%
Seen by 82 of 82 full-feed vantage points
Globally propagatedObserved at 5 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
- 1st November 2006
- Allocation block
- 122.56.0.0/15
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 122.56.115.0/24 | 256 | AS4648Spark New Zealand | 82/82 |
History
- AS932522nd September 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.
Open 122.56.114.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.