Observed topology
AS800 ONEWEB
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS800: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 867 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 115 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 67 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 59 |
| AS5511 | Orange S.A. | Transit | IPv4 | 59 |
| AS37468 | Angola Cables | Unclassified | IPv4 | 14 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 9 |
| AS30844 | Liquid Telecommunications Ltd | Unclassified | IPv4 | 9 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 | 4 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS800 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29286 | SKYLOGIC S.P.A. | Residential | IPv4 | 354 |
Adjacency
Adjacent networks
Every AS seen directly next to AS800 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 867 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 469 |
| AS29286 | SKYLOGIC S.P.A. | Residential | IPv4 | 354 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 67 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 59 |
| AS5511 | Orange S.A. | Transit | IPv4 | 59 |
| AS37468 | Angola Cables | Unclassified | IPv4 | 14 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 9 |
| AS30844 | Liquid Telecommunications Ltd | Unclassified | IPv4 | 9 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 | 4 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.