182.50.162.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
NZAllocated 26th February 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS45641seen on 272 paths from 34 vantage points
- Peer of AS18400seen on 1,520 paths from 142 vantage points
- Peer of AS56030seen on 5,951 paths from 131 vantage points
- Peer of AS9790seen on 12,239 paths from 122 vantage points
- Peer of AS4826seen on 6,178 paths from 2 vantage points
AU
SGOne 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, UK456414517746378529This path
- Sao Paulo45641451773356266213This path
- Oregon, US456414517729142335220130This path
- Singapore45641184005603097904826132337Shown above
- Amsterdam45641184005603097904826154126939213151This 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 80 of 80 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
- 26th February 2010
- Allocation block
- 182.50.160.0/22
- 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 |
|---|---|---|---|
| 182.50.160.0/22 | 1k | AS45641Advantage Limited | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 182.50.163.0/24 | 256 | AS45641Advantage Limited | 80/80 |
History
- AS4564112th 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.
Open 182.50.162.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.