Observed topology

AS212573 Technology-International-AS FastIraq, LLC

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212573: 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
AS21277	Allay Nawroz Telecom Company for Communication/Ltd.	Unclassified	IPv4 IPv6	106
AS174	Cogent Communications, LLC	Transit	IPv4	90

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS211513	Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.	Unclassified	IPv4	8

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	206
AS211513	Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.	Unclassified	IPv4	181
AS21277	Allay Nawroz Telecom Company for Communication/Ltd.	Unclassified	IPv4 IPv6	106
AS3223	Voxility LLP	Hosting	IPv4	65

Provenance

Where this comes from

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