Observed topology
AS214329 BGP bgp.sa
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS214329: 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 IPv6 | 25 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 15 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 11 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 4 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 4 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 2 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 2 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 2 |
Transit
Downstream networks
Networks for which AS214329 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51130 | Homaye Jahan Nama Co. ( Private Joint Stock) | Unclassified | IPv4 | 55 |
| AS202776 | MOECLUB LTD | Unclassified | IPv6 | 53 |
| AS46953 | FENGYE INC | Unclassified | IPv4 | 49 |
| AS218998 | Johan Garcia | Unclassified | IPv4 | 44 |
| AS47794 | Etihad GO Company For communications | Unclassified | IPv4 IPv6 | 41 |
| AS212793 | Xiwei Ye | Unclassified | IPv6 | 41 |
| AS3225 | GULFNET COMMUNICATIONS CO. WLL | Residential | IPv4 | 17 |
| AS29357 | NATIONAL MOBILE TELECOMMUNICATIONS COMPANY K.S.C.P. | Unclassified | IPv4 | 14 |
| AS51375 | STC BAHRAIN B.S.C CLOSED | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS214329 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 116 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 76 |
| AS51130 | Homaye Jahan Nama Co. ( Private Joint Stock) | Unclassified | IPv4 | 55 |
| AS202776 | MOECLUB LTD | Unclassified | IPv6 | 53 |
| AS46953 | FENGYE INC | Unclassified | IPv4 | 49 |
| AS218998 | Johan Garcia | Unclassified | IPv4 | 44 |
| AS47794 | Etihad GO Company For communications | Unclassified | IPv4 IPv6 | 41 |
| AS212793 | Xiwei Ye | Unclassified | IPv6 | 41 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 32 |
| AS3225 | GULFNET COMMUNICATIONS CO. WLL | Residential | IPv4 | 17 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.