192.26.93.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
Allocated 10th February 1987
AS paths to this prefix
One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.
- Singapore46976939132337This path
- Oregon, US4697693920130This path
- London, UK4697752155391249712998529This path
- Sao Paulo469775215539124973356266213This path
- Amsterdam4697752155391249717434549213151This 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
99%
Seen by 79 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
- 10th February 1987
- Allocation block
- 192.26.93.0/24
- 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 |
|---|---|---|---|
| 192.26.92.0/24 | 256 | AS10515Verisign Anycast US 0Z | 2/80 |
| 192.26.92.0/24 | 256 | AS27544Verisign Anycast NL 0N | 1/80 |
| 192.26.92.0/24 | 256 | AS36630Verisign Anycast US 3O | 3/80 |
| 192.26.92.0/24 | 256 | AS40717Verisign Anycast GB 0J | 2/80 |
| 192.26.92.0/24 | 256 | AS396540Verisign Anycast US 0G | 2/80 |
| 192.26.92.0/24 | 256 | AS396547Verisign Anycast FR 0D | 1/80 |
| 192.26.92.0/24 | 256 | AS396549Verisign Anycast GB 0A | 35/80 |
| 192.26.92.0/24 | 256 | AS396555Verisign Anycast US 0O | 3/80 |
| 192.26.92.0/24 | 256 | AS396574Verisign Anycast US 1I | 6/80 |
| 192.26.92.0/24 | 256 | AS396583Verisign Anycast US 1Q | 1/80 |
History
- AS469712th 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 192.26.93.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.