Observed topology
AS3737 AS-PTD
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS3737: 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 | 597 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 500 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 262 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 222 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 24 |
| AS293 | ESnet | Unclassified | IPv4 | 23 |
| AS58057 | Securebit AG | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS3737 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14369 | Nmax | Unclassified | IPv4 IPv6 | 564 |
| AS14928 | PenTeleData Inc. | Residential | IPv4 IPv6 | 509 |
| AS397369 | LVHN | Unclassified | IPv4 | 330 |
| AS27621 | AMERICAN COMPUTER ASSOCIATES | Unclassified | IPv4 | 236 |
| AS398191 | Tri-Co Connections | Unclassified | IPv4 | 220 |
| AS22841 | Northampton Community College | Unclassified | IPv4 | 173 |
| AS394893 | Clair Global | Unclassified | IPv4 | 168 |
| AS396269 | Buckeye Partners L.P. | Unclassified | IPv4 | 118 |
| AS396462 | LKQ Corporation | Unclassified | IPv4 | 118 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 93 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3737 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 2,003 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,919 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 998 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 683 |
| AS14369 | Nmax | Unclassified | IPv4 IPv6 | 564 |
| AS14928 | PenTeleData Inc. | Residential | IPv4 IPv6 | 509 |
| AS397369 | LVHN | Unclassified | IPv4 | 330 |
| AS27621 | AMERICAN COMPUTER ASSOCIATES | Unclassified | IPv4 | 236 |
| AS394893 | Clair Global | Unclassified | IPv4 | 226 |
| AS398191 | Tri-Co Connections | Unclassified | IPv4 | 220 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.