192.58.129.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
Allocated 2nd July 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS53902seen on 53 paths from 53 vantage points
- Peer of AS1002seen on 295 paths from 80 vantage points
- Peer of AS137409seen on 6,062 paths from 2 vantage points
One 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
- Amsterdam539021002137409213151This path
- London, UK53902325712998529This path
- Sao Paulo539021002137409266213This path
- Singapore539021002137409132337Shown above
- Oregon, US5390232572335220130This 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
- ARIN — North America
- Country
United States
- Allocated
- 2nd July 2026
- Allocation block
- 192.58.129.0/24
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 192.58.129.0/24 | AS53902 | /24 |
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.58.128.0/24 | 256 | AS20431Verisign Anycast US 3N | 1/80 |
| 192.58.128.0/24 | 256 | AS22547Verisign Anycast US 0A | 1/80 |
| 192.58.128.0/24 | 256 | AS36631Verisign Anycast US 1A | 2/80 |
| 192.58.128.0/24 | 256 | AS40717Verisign Anycast GB 0J | 1/80 |
| 192.58.128.0/24 | 256 | AS396544Verisign Anycast US 0K | 2/80 |
| 192.58.128.0/24 | 256 | AS396545Verisign Anycast US 0L | 1/80 |
| 192.58.128.0/24 | 256 | AS396549Verisign Anycast GB 0A | 18/80 |
| 192.58.128.0/24 | 256 | AS396550Verisign Anycast GB 0B | 2/80 |
| 192.58.128.0/24 | 256 | AS396566Verisign Anycast NL 0L | 1/80 |
| 192.58.128.0/24 | 256 | AS396567Verisign Anycast NL 0M | 1/80 |
History
- AS5390212th 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.58.129.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.