Observed topology

AS200370 FPCC-AS

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

Upstream graph Who carries AS200370, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS200370 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200370: 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
AS12880	Iran Information Technology Company PJSC	Residential	IPv4	928

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS49680	Armaghan Rahe Talaie	Unclassified	IPv4	696
AS56632	Aryan Satellite Co. (Private Joint Stock)	Unclassified	IPv4	354
AS204203	Atrin Information & Communications Technology Company PJS	Unclassified	IPv4	292
AS203247	Islamic Azad University	Unclassified	IPv4	232
AS203951	Toseh Samanehay-e Narmafzari-e Negin (Tosan) PJSC	Unclassified	IPv4	111

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12880	Iran Information Technology Company PJSC	Residential	IPv4	2,613
AS49680	Armaghan Rahe Talaie	Unclassified	IPv4	696
AS56632	Aryan Satellite Co. (Private Joint Stock)	Unclassified	IPv4	354
AS204203	Atrin Information & Communications Technology Company PJS	Unclassified	IPv4	292
AS203247	Islamic Azad University	Unclassified	IPv4	232
AS203951	Toseh Samanehay-e Narmafzari-e Negin (Tosan) PJSC	Unclassified	IPv4	111

Provenance

Where this comes from

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