asn.dev

Observed topology

AS214171 FOOJAN Foojan Cloud

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214171: 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
AS60248Sefroyek Pardaz Engineering PJSCUnclassifiedIPv4246
AS42337Respina Networks & Beyond PJSCUnclassifiedIPv4 IPv6220
AS213759Tose'eh Lian Yas Ertebat PJSCUnclassifiedIPv4 IPv6160
AS213969Rayanesh Pardis Saman PJSCUnclassifiedIPv463

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215671Peimayesh Ertebat Oxin Co.(PJSC)UnclassifiedIPv4124
AS211703Fanavaran Asak Mahan Asia Ltd.UnclassifiedIPv4123

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60248Sefroyek Pardaz Engineering PJSCUnclassifiedIPv4370
AS42337Respina Networks & Beyond PJSCUnclassifiedIPv4 IPv6343
AS213759Tose'eh Lian Yas Ertebat PJSCUnclassifiedIPv4 IPv6160
AS215671Peimayesh Ertebat Oxin Co.(PJSC)UnclassifiedIPv4124
AS211703Fanavaran Asak Mahan Asia Ltd.UnclassifiedIPv4123
AS213969Rayanesh Pardis Saman PJSCUnclassifiedIPv463

Provenance

Where this comes from

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