192.31.80.0/24
Verisign Anycast GB 0AAS396549
Verisign Anycast JP 0EAS396605
Verisign Anycast DE 0FAS397198
Verisign Anycast US 1IAS396574
Verisign Anycast DE 0PAS397209
Verisign Anycast US 2VAS397204
Verisign Anycast US 0OAS396555
Verisign Anycast US 0GAS396540
Verisign Anycast US 2SAS397201
Verisign Anycast FR 0DAS396547
Verisign Anycast US 1QAS396583
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
35 of 80 vantage points
RPKI
Registry
USAllocated 30th November 2000
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Adjacentseen on 824 paths from 75 vantage points
- Peer of AS7342seen on 67 paths from 2 vantage points
SGOne 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
- Singapore3965497342132337Shown above
- Amsterdam396549734234549213151This path
- London, UK397198734212998529This path
- Sao Paulo39655573423356266213This path
- Oregon, US3965407342693920130This 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
44%
Seen by 35 of 80 full-feed vantage points
Partially propagatedObserved at 4 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.31.80.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.31.80.0/24 | AS10515 | /24 |
| 192.31.80.0/24 | AS19836 | /24 |
| 192.31.80.0/24 | AS20172 | /24 |
| 192.31.80.0/24 | AS20362 | /24 |
| 192.31.80.0/24 | AS20431 | /24 |
| 192.31.80.0/24 | AS211369 | /24 |
| 192.31.80.0/24 | AS21313 | /24 |
| 192.31.80.0/24 | AS22547 | /24 |
| 192.31.80.0/24 | AS25485 | /24 |
| 192.31.80.0/24 | AS27544 | /24 |
| 192.31.80.0/24 | AS32651 | /24 |
| 192.31.80.0/24 | AS36616 | /24 |
| 192.31.80.0/24 | AS36617 | /24 |
| 192.31.80.0/24 | AS36618 | /24 |
| 192.31.80.0/24 | AS36619 | /24 |
| 192.31.80.0/24 | AS36620 | /24 |
| 192.31.80.0/24 | AS36621 | /24 |
| 192.31.80.0/24 | AS36622 | /24 |
| 192.31.80.0/24 | AS36623 | /24 |
| 192.31.80.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
No prefix of the same length in the same parent block is announced.
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.31.80.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.