asn.dev

Observed topology

AS206388 ertebatatazinkia Gostaresh Ertebat Azin Kia Company PJSC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206388: 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
AS49100Pishgaman Toseeh Ertebatat Company (Private Joint Stock)UnclassifiedIPv4 IPv6774

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203684Imen Sanat Novin Alighapoo Private Joint Stock CompanyUnclassifiedIPv4 IPv6649
AS16235Pouya Nazm Najafabad Computer Co(PJS)UnclassifiedIPv4124
AS61129Islamic Azad UniversityUnclassifiedIPv462
AS219060Mizbani Mehr Hamin PJSCUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS49100Pishgaman Toseeh Ertebatat Company (Private Joint Stock)UnclassifiedIPv4 IPv61,851
AS203684Imen Sanat Novin Alighapoo Private Joint Stock CompanyUnclassifiedIPv4 IPv6831
AS16235Pouya Nazm Najafabad Computer Co(PJS)UnclassifiedIPv4124
AS61129Islamic Azad UniversityUnclassifiedIPv462
AS219060Mizbani Mehr Hamin PJSCUnclassifiedIPv460

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.