asn.dev

Observed topology

AS54103 MODMC-54103-AS - MOD Mission Critical, LLC

Unclassified ARIN

Upstreams 9 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 3
Upstream graph Who carries AS54103, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS54103 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS54103: 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 IPv611,129
AS3257GTT Communications Inc.TransitIPv4 IPv610,115
AS54004Cablevision Lightpath LLCUnclassifiedIPv42,520
AS174Cogent Communications, LLCTransitIPv41,335
AS7922Comcast Cable Communications, LLCResidentialIPv4264
AS3356Level 3 Parent, LLCTransitIPv4218
AS20055Wholesail networks LLCResidentialIPv4190
AS6461Zayo BandwidthTransitIPv4118
AS852TELUS Communications Inc.ResidentialIPv438

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40061UnitedLayer, LLCUnclassifiedIPv4 IPv610
AS6260MOD Mission Critical, LLCUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv611,129
AS3257GTT Communications Inc.TransitIPv4 IPv610,125
AS54004Cablevision Lightpath LLCUnclassifiedIPv42,520
AS174Cogent Communications, LLCTransitIPv41,335
AS7922Comcast Cable Communications, LLCResidentialIPv4264
AS3356Level 3 Parent, LLCTransitIPv4219
AS20055Wholesail networks LLCResidentialIPv4190
AS6461Zayo BandwidthTransitIPv4118
AS852TELUS Communications Inc.ResidentialIPv438
AS40061UnitedLayer, LLCUnclassifiedIPv4 IPv610

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.