Observed topology
AS213759 TELIA
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS213759: 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 |
|---|---|---|---|---|
| AS43754 | Asiatech Data Transmission company | Unclassified | IPv4 | 120 |
Transit
Downstream networks
Networks for which AS213759 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50558 | Rayaneh Pardazan Baran Co. Ltd. | Unclassified | IPv4 IPv6 | 1,315 |
| AS206854 | Lesun communication furtherance engineers Co, (Ltd.) | Unclassified | IPv4 IPv6 | 893 |
| AS44375 | Asmanfaraz Sepahan Company (P.J.S) | Unclassified | IPv4 IPv6 | 213 |
| AS214171 | Foojan Cloud Computing Co. PJS | Unclassified | IPv4 IPv6 | 158 |
| AS41152 | Ertebatat Fara Gostar Shargh PJSC | Unclassified | IPv4 | 123 |
| AS59691 | Pouya shabakeh Asr Co. (LTD.) | Unclassified | IPv4 | 62 |
| AS48289 | Dadeh Pardazan Sabz Alborz Co.(P.J.S.) | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS213759 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43754 | Asiatech Data Transmission company | Unclassified | IPv4 IPv6 | 3,196 |
| AS50558 | Rayaneh Pardazan Baran Co. Ltd. | Unclassified | IPv4 IPv6 | 1,315 |
| AS206854 | Lesun communication furtherance engineers Co, (Ltd.) | Unclassified | IPv4 IPv6 | 1,019 |
| AS44375 | Asmanfaraz Sepahan Company (P.J.S) | Unclassified | IPv4 IPv6 | 339 |
| AS214171 | Foojan Cloud Computing Co. PJS | Unclassified | IPv4 IPv6 | 158 |
| AS41152 | Ertebatat Fara Gostar Shargh PJSC | Unclassified | IPv4 | 123 |
| AS59691 | Pouya shabakeh Asr Co. (LTD.) | Unclassified | IPv4 | 62 |
| AS48289 | Dadeh Pardazan Sabz Alborz Co.(P.J.S.) | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.