Observed topology
AS25019 SAUDINETSTC-AS Saudi Telecom Company JSC
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS25019: 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 |
|---|---|---|---|---|
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 163,239 |
Transit
Downstream networks
Networks for which AS25019 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39891 | Saudi Telecom Company JSC | Mobile | IPv4 IPv6 | 383,793 |
| AS48932 | Saudi Arabian Airlines | Unclassified | IPv4 | 521 |
| AS21002 | Ministry of Finance of Saudi Arabia | Unclassified | IPv4 IPv6 | 338 |
| AS54994 | Meteverse Limited. | Unclassified | IPv4 IPv6 | 256 |
| AS200025 | Saudi Arabian Mining Company (Ma'aden) JSC | Unclassified | IPv4 | 238 |
| AS198406 | TASNEE National Company LTD | Unclassified | IPv4 | 213 |
| AS49474 | Elm Company PJS | Unclassified | IPv4 IPv6 | 200 |
| AS396986 | Bytedance Inc. | Hosting | IPv4 IPv6 | 193 |
| AS210275 | Saudi Information Technology Company CJSC | Unclassified | IPv4 IPv6 | 192 |
| AS41594 | Banque Saudi Fransi | Unclassified | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25019 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 551,859 |
| AS39891 | Saudi Telecom Company JSC | Mobile | IPv4 IPv6 | 383,793 |
| AS48932 | Saudi Arabian Airlines | Unclassified | IPv4 | 521 |
| AS21002 | Ministry of Finance of Saudi Arabia | Unclassified | IPv4 IPv6 | 338 |
| AS54994 | Meteverse Limited. | Unclassified | IPv4 IPv6 | 256 |
| AS200025 | Saudi Arabian Mining Company (Ma'aden) JSC | Unclassified | IPv4 | 238 |
| AS198406 | TASNEE National Company LTD | Unclassified | IPv4 | 213 |
| AS49474 | Elm Company PJS | Unclassified | IPv4 IPv6 | 200 |
| AS396986 | Bytedance Inc. | Hosting | IPv4 IPv6 | 193 |
| AS210275 | Saudi Information Technology Company CJSC | Unclassified | IPv4 IPv6 | 192 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.