Observed topology
AS21700 NEPTUNE-NETWORKS
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS21700: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 181 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 147 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 123 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 7 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 4 |
| AS13030 | Init7 (Switzerland) Ltd. | Hosting | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS21700 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS400967 | Assured Networks | Hosting | IPv4 IPv6 | 403 |
| AS19949 | FNFISP | Unclassified | IPv4 | 399 |
| AS53727 | Penguin Networks | Unclassified | IPv4 IPv6 | 299 |
| AS401363 | Lyncross LLC | Unclassified | IPv4 IPv6 | 170 |
| AS63229 | Nocturnal Networks | Unclassified | IPv4 IPv6 | 150 |
| AS53343 | sc Network | Unclassified | IPv4 IPv6 | 149 |
| AS961 | Achieve Wireless Inc | Unclassified | IPv4 IPv6 | 131 |
| AS18470 | GraceWorks, LLC | Unclassified | IPv4 IPv6 | 130 |
| AS203943 | ALEXANDER NICHOLSON | Unclassified | IPv6 | 111 |
| AS400550 | Suburban Marine, Inc. | Unclassified | IPv6 | 111 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21700 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,973 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,301 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 795 |
| AS400967 | Assured Networks | Hosting | IPv4 IPv6 | 403 |
| AS19949 | FNFISP | Unclassified | IPv4 | 399 |
| AS53727 | Penguin Networks | Unclassified | IPv4 IPv6 | 299 |
| AS401363 | Lyncross LLC | Unclassified | IPv4 IPv6 | 170 |
| AS63229 | Nocturnal Networks | Unclassified | IPv4 IPv6 | 150 |
| AS53343 | sc Network | Unclassified | IPv4 IPv6 | 149 |
| AS961 | Achieve Wireless Inc | Unclassified | IPv4 IPv6 | 131 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.