asn.dev

Observed topology

AS213759 TELIA

Unclassified RIPE

Upstreams 1 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 5
Upstream graph Who carries AS213759, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS213759 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS43754Asiatech Data Transmission companyUnclassifiedIPv4120

Transit

Downstream networks

inferred

Networks for which AS213759 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS50558Rayaneh Pardazan Baran Co. Ltd.UnclassifiedIPv4 IPv61,315
AS206854Lesun communication furtherance engineers Co, (Ltd.)UnclassifiedIPv4 IPv6893
AS44375Asmanfaraz Sepahan Company (P.J.S)UnclassifiedIPv4 IPv6213
AS214171Foojan Cloud Computing Co. PJSUnclassifiedIPv4 IPv6158
AS41152Ertebatat Fara Gostar Shargh PJSCUnclassifiedIPv4123
AS59691Pouya shabakeh Asr Co. (LTD.)UnclassifiedIPv462
AS48289Dadeh Pardazan Sabz Alborz Co.(P.J.S.)UnclassifiedIPv460

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS213759 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS43754Asiatech Data Transmission companyUnclassifiedIPv4 IPv63,196
AS50558Rayaneh Pardazan Baran Co. Ltd.UnclassifiedIPv4 IPv61,315
AS206854Lesun communication furtherance engineers Co, (Ltd.)UnclassifiedIPv4 IPv61,019
AS44375Asmanfaraz Sepahan Company (P.J.S)UnclassifiedIPv4 IPv6339
AS214171Foojan Cloud Computing Co. PJSUnclassifiedIPv4 IPv6158
AS41152Ertebatat Fara Gostar Shargh PJSCUnclassifiedIPv4123
AS59691Pouya shabakeh Asr Co. (LTD.)UnclassifiedIPv462
AS48289Dadeh Pardazan Sabz Alborz Co.(P.J.S.)UnclassifiedIPv460

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.