192.42.177.0/24
Verisign Anycast US 0OAS396555
Verisign Anycast FR 0BAS396546
Verisign Anycast US 0KAS396544
Verisign Anycast GB 0BAS396550
Verisign Anycast FR 0FAS396599
Verisign Anycast US 0WAS396563
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
26 of 82 vantage points
RPKI
Registry
USAllocated 17th September 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS396555seen on 316 paths from 56 vantage points
- Peer of AS7342seen on 6,449 paths from 147 vantage points
- Peer of AS2914seen on 83,562 paths from 1 vantage point
KHOne 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
- Sao Paulo396555734235280This path
- London, UK10515734212998529This path
- Singapore3965557342291423673Shown above
- Oregon, US3965557342693920130This path
- Amsterdam1051573421299250918298This 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
32%
Seen by 26 of 82 full-feed vantage points
Seen by few vantage pointsObserved 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
- 17th September 2013
- Allocation block
- 192.42.176.0/23
- 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.42.177.0/24 | AS10515 | /24 |
| 192.42.177.0/24 | AS19836 | /24 |
| 192.42.177.0/24 | AS20172 | /24 |
| 192.42.177.0/24 | AS20362 | /24 |
| 192.42.177.0/24 | AS20431 | /24 |
| 192.42.177.0/24 | AS211369 | /24 |
| 192.42.177.0/24 | AS21313 | /24 |
| 192.42.177.0/24 | AS22547 | /24 |
| 192.42.177.0/24 | AS25485 | /24 |
| 192.42.177.0/24 | AS27544 | /24 |
| 192.42.177.0/24 | AS32651 | /24 |
| 192.42.177.0/24 | AS36616 | /24 |
| 192.42.177.0/24 | AS36617 | /24 |
| 192.42.177.0/24 | AS36618 | /24 |
| 192.42.177.0/24 | AS36619 | /24 |
| 192.42.177.0/24 | AS36620 | /24 |
| 192.42.177.0/24 | AS36621 | /24 |
| 192.42.177.0/24 | AS36622 | /24 |
| 192.42.177.0/24 | AS36623 | /24 |
| 192.42.177.0/24 | AS36624 | /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.42.176.0/24 | 256 | AS19836Verisign Anycast US 2M | 8/82 |
| 192.42.176.0/24 | 256 | AS21313Verisign Anycast FR 0A | 2/82 |
| 192.42.176.0/24 | 256 | AS22547Verisign Anycast US 0A | 1/82 |
| 192.42.176.0/24 | 256 | AS27544Verisign Anycast NL 0N | 1/82 |
| 192.42.176.0/24 | 256 | AS36617Verisign Anycast US 0M | 1/82 |
| 192.42.176.0/24 | 256 | AS36623Verisign Anycast JP 0D | 3/82 |
| 192.42.176.0/24 | 256 | AS36630Verisign Anycast US 3O | 3/82 |
| 192.42.176.0/24 | 256 | AS36631Verisign Anycast US 1A | 2/82 |
| 192.42.176.0/24 | 256 | AS40717Verisign Anycast GB 0J | 4/82 |
| 192.42.176.0/24 | 256 | AS211369Verisign Anycast FR 0E | 6/82 |
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.42.177.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.