asn.dev

Observed topology

AS13367 COMCAST-13367

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13367: 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
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv62,341
AS3356Level 3 Parent, LLCTransitIPv4 IPv688

Transit

Downstream networks

All 74

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

ASNetworkTypeFamiliesPaths seen
AS5774United States Postal ServiceUnclassifiedIPv4301
AS26638Minneapolis Public SchoolsUnclassifiedIPv4238
AS14895Lawson SoftwareUnclassifiedIPv4178
AS31929Great River EnergyUnclassifiedIPv4151
AS54113Fastly, Inc.HostingIPv4 IPv6128
AS32530Opus CorporationUnclassifiedIPv4119
AS23531Sunrise BanksUnclassifiedIPv4117
AS20125Luther SeminaryUnclassifiedIPv4116
AS54017UCare MinnesotaUnclassifiedIPv4103
AS401523Auction HarmonyUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

All 76

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

ASNetworkTypeFamiliesPaths seen
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv64,957
AS3356Level 3 Parent, LLCTransitIPv4 IPv6835
AS5774United States Postal ServiceUnclassifiedIPv4301
AS26638Minneapolis Public SchoolsUnclassifiedIPv4238
AS14895Lawson SoftwareUnclassifiedIPv4178
AS31929Great River EnergyUnclassifiedIPv4151
AS54113Fastly, Inc.HostingIPv4 IPv6128
AS32530Opus CorporationUnclassifiedIPv4119
AS23531Sunrise BanksUnclassifiedIPv4117
AS20125Luther SeminaryUnclassifiedIPv4116

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.