Observed topology
AS2686 ATGS-MMD-AS
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS2686: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,593 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 793 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 740 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 735 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 532 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 441 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 426 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 320 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 147 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 128 |
Transit
Downstream networks
Networks for which AS2686 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4249 | Eli Lilly and Company | Unclassified | IPv4 | 1,800 |
| AS3917 | Shell Information Technology International B.V. | Unclassified | IPv4 | 1,320 |
| AS1341 | Rockwell Collins, Inc. | Unclassified | IPv4 | 538 |
| AS2687 | AT&T Enterprises, LLC | Unclassified | IPv4 | 495 |
| AS2154 | HP Inc. | Unclassified | IPv4 | 298 |
| AS11857 | Money Services, Inc. | Unclassified | IPv4 | 292 |
| AS14381 | Caterpillar, Inc. | Unclassified | IPv4 | 240 |
| AS2155 | HP Inc. | Unclassified | IPv4 | 238 |
| AS21272 | Danone SA | Unclassified | IPv4 | 232 |
| AS12213 | Centersquare | Hosting | IPv4 | 220 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2686 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,054 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,085 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 2,026 |
| AS4249 | Eli Lilly and Company | Unclassified | IPv4 | 1,800 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,620 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 1,449 |
| AS3917 | Shell Information Technology International B.V. | Unclassified | IPv4 | 1,320 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,233 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,077 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 835 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.