Observed topology
AS10310 YAHOO-1 - Yahoo Holdings Inc.
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS10310: 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 |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 932 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 843 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 561 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 388 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 349 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 237 |
| AS3462 | Data Communication Business Group | Residential | IPv4 | 157 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 137 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 123 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 104 |
Transit
Downstream networks
Networks for which AS10310 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26101 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 4,873 |
| AS36647 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 4,357 |
| AS34010 | Yahoo-UK Limited | Unclassified | IPv4 IPv6 | 3,024 |
| AS36646 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 2,703 |
| AS56173 | internet content provider | Unclassified | IPv4 IPv6 | 1,687 |
| AS7280 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 869 |
| AS10880 | Yahoo Holdings Inc. | Hosting | IPv4 IPv6 | 576 |
| AS14778 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 575 |
| AS14777 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 339 |
| AS36088 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 334 |
Adjacency
Adjacent networks
Every AS seen directly next to AS10310 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26101 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 4,873 |
| AS36647 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 4,357 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,762 |
| AS34010 | Yahoo-UK Limited | Unclassified | IPv4 IPv6 | 3,024 |
| AS36646 | Yahoo Holdings Inc. | Unclassified | IPv4 IPv6 | 2,703 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,380 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,938 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,916 |
| AS56173 | internet content provider | Unclassified | IPv4 IPv6 | 1,687 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 1,384 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.