150.82.0.0/16
At a glance
Addresses
/16 block
Visibility
80 of 80 vantage points
RPKI
Registry
JPAllocated 11th May 1993
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS23793seen on 1,281 paths from 80 vantage points
- Peer of AS2907seen on 67,501 paths from 129 vantage points
- Peer of AS2497seen on 22,890 paths from 34 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
US
BROne 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
- Singapore2379329076939132337This path
- Oregon, US237932907693920130This path
- London, UK237932907249712998529This path
- Sao Paulo23793290724973356266213Shown above
- Amsterdam237932907249717434549213151This 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
- Japan
- Allocated
- 11th May 1993
- Allocation block
- 150.82.0.0/16
- 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 |
|---|---|---|---|
| 150.83.0.0/16 | 65.5k | AS2907Science Information Network | 79/80 |
History
- AS2379312th 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 150.82.0.0/16 in the calculator/16 reference
Routing data derived from RouteViews MRT archives and public registry data.