192.68.126.0/24
Verisign Anycast JP 0EAS396605
Verisign Anycast US 1IAS396574
Verisign Anycast US 0LAS396545
Verisign Anycast US 0KAS396544
Verisign Anycast US 1MAS396576
Verisign Anycast US 2YAS397206
Verisign Anycast US 2RAS397200
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
45 of 80 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 London, UK.
Seen from London, UK
- Peer of AS19836seen on 305 paths from 89 vantage points
- Peer of AS7342seen on 6,414 paths from 142 vantage points
- Peer of AS1299seen on 403,291 paths from 2 vantage points
SE
AEOne 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
- London, UK19836734212998529Shown above
- Sao Paulo2254773423356266213This path
- Oregon, US198367342693920130This path
- Amsterdam198367342129934549213151This path
- Singapore396605734229148966132337This 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
56%
Seen by 45 of 80 full-feed vantage points
Partially 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
- 17th September 2013
- Allocation block
- 192.68.126.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.68.126.0/24 | AS10515 | /24 |
| 192.68.126.0/24 | AS19836 | /24 |
| 192.68.126.0/24 | AS20172 | /24 |
| 192.68.126.0/24 | AS20362 | /24 |
| 192.68.126.0/24 | AS20431 | /24 |
| 192.68.126.0/24 | AS211369 | /24 |
| 192.68.126.0/24 | AS21313 | /24 |
| 192.68.126.0/24 | AS22547 | /24 |
| 192.68.126.0/24 | AS25485 | /24 |
| 192.68.126.0/24 | AS27544 | /24 |
| 192.68.126.0/24 | AS32651 | /24 |
| 192.68.126.0/24 | AS36616 | /24 |
| 192.68.126.0/24 | AS36617 | /24 |
| 192.68.126.0/24 | AS36618 | /24 |
| 192.68.126.0/24 | AS36619 | /24 |
| 192.68.126.0/24 | AS36620 | /24 |
| 192.68.126.0/24 | AS36621 | /24 |
| 192.68.126.0/24 | AS36622 | /24 |
| 192.68.126.0/24 | AS36623 | /24 |
| 192.68.126.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.68.127.0/24 | 256 | AS7342VeriSign Infrastructure & Operations | 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.68.126.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.