Observed topology
AS5580 GTT-ASIA GTT Communications Netherlands B.V.
Transit RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS5580: 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 |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,187 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 497 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 225 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 30 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 | 30 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 29 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 | 28 |
| AS45629 | JasTel Network International Gateway | Residential | IPv6 | 7 |
| AS4657 | StarHub Ltd | Residential | IPv4 IPv6 | 3 |
Transit
Downstream networks
Networks for which AS5580 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1341 | Rockwell Collins, Inc. | Unclassified | IPv4 IPv6 | 253 |
| AS9829 | National Internet Backbone | Residential | IPv4 IPv6 | 229 |
| AS19527 | Google LLC | Unclassified | IPv4 IPv6 | 225 |
| AS30058 | FDCservers.net | Unclassified | IPv4 IPv6 | 140 |
| AS25896 | IPC Network Services Inc. | Unclassified | IPv4 | 116 |
| AS13150 | CATO NETWORKS LTD | Unclassified | IPv4 | 101 |
| AS394977 | TAKE-TWO INTERACTIVE SOFTWARE, INC. | Unclassified | IPv4 IPv6 | 91 |
| AS10806 | AGENCE FRANCE PRESSE | Unclassified | IPv4 | 78 |
| AS131189 | Livecom Limited | Unclassified | IPv4 | 60 |
| AS9229 | SPEEDCAST Limited | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5580 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 3,085 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,384 |
| AS30058 | FDCservers.net | Unclassified | IPv4 IPv6 | 919 |
| AS1341 | Rockwell Collins, Inc. | Unclassified | IPv4 IPv6 | 363 |
| AS9829 | National Internet Backbone | Residential | IPv4 IPv6 | 287 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 225 |
| AS19527 | Google LLC | Unclassified | IPv4 IPv6 | 225 |
| AS25896 | IPC Network Services Inc. | Unclassified | IPv4 | 116 |
| AS13150 | CATO NETWORKS LTD | Unclassified | IPv4 | 101 |
| AS394977 | TAKE-TWO INTERACTIVE SOFTWARE, INC. | Unclassified | IPv4 IPv6 | 91 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.