Observed topology
AS16905 LEARN
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS16905: 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 AS16905 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS30674 | Baylor University | Unclassified | IPv4 IPv6 | 61 |
| AS36695 | Region 5 Education Service Center | Unclassified | IPv4 | 36 |
| AS18777 | Texas State University | Unclassified | IPv4 | 30 |
| AS14382 | Education Service Center | Unclassified | IPv4 IPv6 | 25 |
| AS589 | University of North Texas | Unclassified | IPv4 | 24 |
| AS36658 | Angelo State University | Unclassified | IPv4 | 21 |
| AS10421 | Texas Tech University | Education | IPv4 | 20 |
| AS1832 | Southern Methodist University | Unclassified | IPv4 | 18 |
| AS46476 | Texas Tech University Health Sciences Center | Unclassified | IPv4 | 18 |
| AS40661 | Education Service Center, Region VI | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16905 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11537 | Internet2 | Unclassified | IPv4 IPv6 | 983 |
| AS4557 | Rice University | Education | IPv4 IPv6 | 459 |
| AS293 | ESnet | Unclassified | IPv4 | 212 |
| AS276 | University of Texas System | Unclassified | IPv4 | 175 |
| AS14085 | LEARN | Unclassified | IPv4 IPv6 | 150 |
| AS30674 | Baylor University | Unclassified | IPv4 IPv6 | 61 |
| AS36695 | Region 5 Education Service Center | Unclassified | IPv4 | 36 |
| AS18777 | Texas State University | Unclassified | IPv4 | 30 |
| AS14382 | Education Service Center | Unclassified | IPv4 IPv6 | 25 |
| AS589 | University of North Texas | Unclassified | IPv4 | 24 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.