asn.dev

Observed topology

AS55 UPENN

Unclassified ARIN Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6130
AS174Cogent Communications, LLCTransitIPv4 IPv6103
AS11164Internet2EducationIPv4 IPv680
AS11537Internet2UnclassifiedIPv4 IPv637

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS69University of PennsylvaniaUnclassifiedIPv463
AS46274Penn MedicineUnclassifiedIPv428

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6162
AS174Cogent Communications, LLCTransitIPv4 IPv6126
AS11164Internet2EducationIPv4 IPv695
AS69University of PennsylvaniaUnclassifiedIPv463
AS11537Internet2UnclassifiedIPv4 IPv658
AS46274Penn MedicineUnclassifiedIPv428

Provenance

Where this comes from

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