Observed topology
AS26415 VERISIGN-INC - VeriSign Global Registry Services
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS26415: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4766 | Korea Telecom | Mobile | IPv4 | 62 |
Transit
Downstream networks
Networks for which AS26415 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS396654 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 16 |
| AS396729 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 13 |
| AS396704 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 10 |
| AS396761 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 10 |
| AS396738 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 9 |
| AS396686 | VeriSign Global Registry Services | Unclassified | IPv4 | 7 |
| AS396707 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 7 |
| AS396690 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 6 |
| AS396727 | VeriSign Global Registry Services | Unclassified | IPv4 | 6 |
| AS396619 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS26415 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4766 | Korea Telecom | Mobile | IPv4 | 62 |
| AS2381 | WiscNet | Unclassified | IPv4 IPv6 | 16 |
| AS396654 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 16 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 15 |
| AS396729 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 13 |
| AS396704 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 10 |
| AS396761 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 10 |
| AS396738 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 9 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 7 |
| AS396686 | VeriSign Global Registry Services | Unclassified | IPv4 | 7 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.