asn.dev

Observed topology

AS40237 UNITED-TELEPHONE

Unclassified ARIN

Upstreams 4 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 4
Upstream graph Who carries AS40237, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS40237 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40237: 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.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6325
AS3356Level 3 Parent, LLCTransitIPv4 IPv6267
AS6939Hurricane Electric LLCTransitIPv4 IPv674
AS174Cogent Communications, LLCTransitIPv4 IPv668

Transit

Downstream networks

inferred

Networks for which AS40237 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS22504LORETTO COMMUNICATION SERVICES, INC.UnclassifiedIPv4799
AS30676Tullahoma Utilities AuthorityUnclassifiedIPv4406
AS399094MIDDLE TENNESSEE ELECTRIC MEMBERSHIP CORPORATION THEUnclassifiedIPv4112
AS19841ISNSUnclassifiedIPv458
AS399978City of FranklinUnclassifiedIPv458
AS63431EMF BroadcastingUnclassifiedIPv415

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS40237 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6833
AS22504LORETTO COMMUNICATION SERVICES, INC.UnclassifiedIPv4799
AS1299Arelion Sweden ABTransitIPv4 IPv6698
AS174Cogent Communications, LLCTransitIPv4 IPv6483
AS30676Tullahoma Utilities AuthorityUnclassifiedIPv4425
AS6939Hurricane Electric LLCTransitIPv4 IPv6187
AS399094MIDDLE TENNESSEE ELECTRIC MEMBERSHIP CORPORATION THEUnclassifiedIPv4112
AS19841ISNSUnclassifiedIPv458
AS399978City of FranklinUnclassifiedIPv458
AS63431EMF BroadcastingUnclassifiedIPv415

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.