Observed topology
AS5050 PSC-EXT
Education ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS5050: 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.
Transit
Downstream networks
Networks for which AS5050 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7925 | West Virginia Network for Educational Telecomputing | Education | IPv4 | 189 |
| AS1207 | Pittsburgh Supercomputing Center | Unclassified | IPv4 | 185 |
| AS1206 | Pittsburgh Supercomputing Center | Unclassified | IPv4 | 184 |
| AS23102 | Robert Morris University | Unclassified | IPv4 | 117 |
| AS36407 | Software Engineering Institute | Unclassified | IPv4 IPv6 | 104 |
| AS3783 | Allegheny Intermediate Unit | Education | IPv4 | 96 |
| AS19281 | Quad9 | Hosting | IPv4 | 58 |
| AS4130 | University of Pittsburgh | Education | IPv4 IPv6 | 53 |
| AS9 | Carnegie Mellon University | Unclassified | IPv4 IPv6 | 46 |
| AS12118 | West Virginia University | Unclassified | IPv4 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5050 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 993 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 472 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 257 |
| AS11537 | Internet2 | Unclassified | IPv4 IPv6 | 245 |
| AS7925 | West Virginia Network for Educational Telecomputing | Education | IPv4 | 189 |
| AS1207 | Pittsburgh Supercomputing Center | Unclassified | IPv4 | 185 |
| AS1206 | Pittsburgh Supercomputing Center | Unclassified | IPv4 | 184 |
| AS11164 | Internet2 | Education | IPv4 IPv6 | 175 |
| AS23102 | Robert Morris University | Unclassified | IPv4 | 117 |
| AS3783 | Allegheny Intermediate Unit | Education | IPv4 IPv6 | 116 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.