192.58.128.0/24
Verisign Anycast GB 0AAS396549
Verisign Anycast SG 0DAS396729
Verisign Anycast DE 0EAS397197
Verisign Anycast BR 0EAS396659
Verisign Anycast CH 0AAS396761
Verisign Anycast US 2KAS396654
Verisign Anycast JP 0EAS396605
Verisign Anycast US 0KAS396544
Verisign Anycast AU 0AAS396738
Verisign Anycast FR 0CAS396707
Verisign Anycast GB 0BAS396550
Verisign Anycast US 3DAS396702
Verisign Anycast KW 0AAS396682
Verisign Anycast NL 0LAS396566
Verisign Anycast RU 0BAS396686
Verisign Anycast PL 0AAS396751
Verisign Anycast US 0LAS396545
Verisign Anycast US 2UAS397203
Verisign Anycast IN 0BAS396629
Verisign Anycast GB 0HAS397194
Verisign Anycast TZ 0AAS396646
Verisign Anycast US 1IAS396574
Verisign Anycast US 3HAS396727
Verisign Anycast US 1QAS396583
Verisign Anycast NO 0AAS396704
Verisign Anycast AU 0BAS396739
Verisign Anycast NL 0MAS396567
Verisign Anycast ZA 0BAS396675
Verisign Anycast IE 0AAS396653
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
18 of 80 vantage points
RPKI
Registry
USAllocated 30th November 2000
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.
- Amsterdam3971977342213151This path
- Sao Paulo39665926415266213This path
- Singapore39672926415132337This path
- London, UK39668226415429618529This path
- Oregon, US39670226415693920130This 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
23%
Seen by 18 of 80 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- 30th November 2000
- Allocation block
- 192.58.128.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.128.0/24 | AS10515 | /24 |
| 192.58.128.0/24 | AS19836 | /24 |
| 192.58.128.0/24 | AS20172 | /24 |
| 192.58.128.0/24 | AS20362 | /24 |
| 192.58.128.0/24 | AS20431 | /24 |
| 192.58.128.0/24 | AS211369 | /24 |
| 192.58.128.0/24 | AS21313 | /24 |
| 192.58.128.0/24 | AS22547 | /24 |
| 192.58.128.0/24 | AS25485 | /24 |
| 192.58.128.0/24 | AS26415 | /24 |
| 192.58.128.0/24 | AS27544 | /24 |
| 192.58.128.0/24 | AS32651 | /24 |
| 192.58.128.0/24 | AS36616 | /24 |
| 192.58.128.0/24 | AS36617 | /24 |
| 192.58.128.0/24 | AS36618 | /24 |
| 192.58.128.0/24 | AS36619 | /24 |
| 192.58.128.0/24 | AS36620 | /24 |
| 192.58.128.0/24 | AS36621 | /24 |
| 192.58.128.0/24 | AS36622 | /24 |
| 192.58.128.0/24 | AS36623 | /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.129.0/24 | 256 | AS53902Fluxorus Networks | 80/80 |
History
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.128.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.