Observed topology
AS7979 SERVERS-COM
Hosting ARIN Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS7979: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 30,450 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 24,159 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 21,334 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 11,897 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 8,345 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 8,134 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 7,098 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,237 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 657 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 451 |
Transit
Downstream networks
Networks for which AS7979 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33438 | Datum | Hosting | IPv4 IPv6 | 767 |
| AS13535 | Ning Interactive, Inc. | Unclassified | IPv4 IPv6 | 380 |
| AS214979 | Dijust Development LTD | Unclassified | IPv4 | 290 |
| AS45470 | 8 to Infinity Pte Ltd | Unclassified | IPv4 IPv6 | 147 |
| AS210986 | PE Mykhaylo Sydorenko | Unclassified | IPv4 | 116 |
| AS219275 | TA Consulting & Services GmbH | Unclassified | IPv4 | 116 |
| AS32244 | Liquid Web, L.L.C | Hosting | IPv4 IPv6 | 88 |
| AS393506 | MY.COM US, INC. | Unclassified | IPv4 | 59 |
| AS402722 | Arct | Unclassified | IPv4 | 59 |
| AS204315 | Game Insight UAB | Unclassified | IPv4 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS7979 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 30,588 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 24,760 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 21,654 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 12,189 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 8,585 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 8,397 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 7,098 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,321 |
| AS33438 | Datum | Hosting | IPv4 IPv6 | 767 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 660 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.