Observed topology
AS226 LOS-NETTOS-AS
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS226: 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 AS226 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS27609 | USC-University Hospital | Unclassified | IPv4 | 1,935 |
| AS4 | University of Southern California | Unclassified | IPv4 IPv6 | 1,644 |
| AS127 | Jet Propulsion Laboratory | Unclassified | IPv4 IPv6 | 1,153 |
| AS47 | University of Southern California | Unclassified | IPv4 | 677 |
| AS85 | The Aerospace Corporation | Unclassified | IPv4 IPv6 | 528 |
| AS62988 | Art Center College of Design | Unclassified | IPv4 | 309 |
| AS25789 | Loyola Marymount University | Unclassified | IPv4 | 245 |
| AS5108 | City of Pasadena | Unclassified | IPv4 | 146 |
| AS394353 | B.Root-Server-OPS | Unclassified | IPv4 IPv6 | 86 |
| AS47065 | USC / UFMG PEERING Research Testbed | Education | IPv4 IPv6 | 68 |
Adjacency
Adjacent networks
Every AS seen directly next to AS226 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,824 |
| AS27609 | USC-University Hospital | Unclassified | IPv4 | 1,935 |
| AS4 | University of Southern California | Unclassified | IPv4 IPv6 | 1,644 |
| AS567 | Los Nettos | Unclassified | IPv4 IPv6 | 1,479 |
| AS127 | Jet Propulsion Laboratory | Unclassified | IPv4 IPv6 | 1,153 |
| AS47 | University of Southern California | Unclassified | IPv4 | 677 |
| AS85 | The Aerospace Corporation | Unclassified | IPv4 IPv6 | 528 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 376 |
| AS62988 | Art Center College of Design | Unclassified | IPv4 | 309 |
| AS25789 | Loyola Marymount University | Unclassified | IPv4 | 245 |
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.