209.112.127.0/24
Verisign Anycast GB 0AAS396549
Verisign Anycast DE 0EAS397197
Verisign Anycast DE 0PAS397209
Verisign Anycast NL 0LAS396566
Verisign Anycast US 1QAS396583
Verisign Anycast GB 0BAS396550
Verisign Anycast GB 0HAS397194
Verisign Anycast NL 0MAS396567
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
25 of 80 vantage points
RPKI
Registry
USAllocated 29th January 2004
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
- London, UK39719773428529This path
- Singapore3965497342132337This path
- Sao Paulo39658373423356266213This path
- Oregon, US366317342693920130This 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
31%
Seen by 25 of 80 full-feed vantage points
Seen by few vantage pointsObserved 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
- 29th January 2004
- Allocation block
- 209.112.112.0/20
- 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 |
|---|---|---|
| 209.112.127.0/24 | AS10515 | /24 |
| 209.112.127.0/24 | AS19836 | /24 |
| 209.112.127.0/24 | AS20172 | /24 |
| 209.112.127.0/24 | AS20362 | /24 |
| 209.112.127.0/24 | AS20431 | /24 |
| 209.112.127.0/24 | AS211369 | /24 |
| 209.112.127.0/24 | AS21313 | /24 |
| 209.112.127.0/24 | AS22547 | /24 |
| 209.112.127.0/24 | AS25485 | /24 |
| 209.112.127.0/24 | AS27544 | /24 |
| 209.112.127.0/24 | AS32651 | /24 |
| 209.112.127.0/24 | AS36616 | /24 |
| 209.112.127.0/24 | AS36617 | /24 |
| 209.112.127.0/24 | AS36618 | /24 |
| 209.112.127.0/24 | AS36619 | /24 |
| 209.112.127.0/24 | AS36620 | /24 |
| 209.112.127.0/24 | AS36621 | /24 |
| 209.112.127.0/24 | AS36622 | /24 |
| 209.112.127.0/24 | AS36623 | /24 |
| 209.112.127.0/24 | AS36624 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 209.112.112.0/20 | 4.1k | AS26134Verisign Anycast US 0B | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 209.112.126.0/24 | 256 | AS26134Verisign Anycast US 0B | 79/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 209.112.127.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.