asn.dev

Observed topology

AS36412 Drexel University

Unclassified ARIN

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11834Drexel UniversityEducationIPv4148
AS3777Haverford CollegeEducationIPv424
AS3795Bryn Mawr CollegeEducationIPv411
AS3782Swarthmore CollegeEducationIPv48
AS11534The School District of PhiladelphiaEducationIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS11834Drexel UniversityEducationIPv4148
AS11164Internet2EducationIPv477
AS33287Comcast Cable Communications, LLCUnclassifiedIPv452
AS11537Internet2UnclassifiedIPv451
AS3777Haverford CollegeEducationIPv424
AS33659Comcast Cable Communications, LLCUnclassifiedIPv416
AS3795Bryn Mawr CollegeEducationIPv411
AS3782Swarthmore CollegeEducationIPv48
AS11534The School District of PhiladelphiaEducationIPv45

Provenance

Where this comes from

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