asn.dev

Observed topology

AS212221 RO-EFX-AS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212221: 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
AS3356Level 3 Parent, LLCTransitIPv4394
AS9002RETN LimitedUnclassifiedIPv4 IPv6154
AS5606GTS Telecom SRLUnclassifiedIPv4110
AS6939Hurricane Electric LLCTransitIPv443
AS20764CJSC RASCOMUnclassifiedIPv411
AS24482SG.GSHostingIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50939Space Ro SRLUnclassifiedIPv4 IPv6454
AS50887DC FIBER HOME SRLUnclassifiedIPv4230
AS60909NETXPERT CONNECT SRLUnclassifiedIPv4120
AS215417TIA CONECT SRLUnclassifiedIPv492
AS60089Conex Distribution SAUnclassifiedIPv447
AS16157S.R.L.UnclassifiedIPv46

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4830
AS50939Space Ro SRLUnclassifiedIPv4 IPv6454
AS9002RETN LimitedUnclassifiedIPv4 IPv6419
AS50887DC FIBER HOME SRLUnclassifiedIPv4230
AS5606GTS Telecom SRLUnclassifiedIPv4223
AS6939Hurricane Electric LLCTransitIPv4148
AS60909NETXPERT CONNECT SRLUnclassifiedIPv4120
AS215417TIA CONECT SRLUnclassifiedIPv492
AS60089Conex Distribution SAUnclassifiedIPv447
AS20764CJSC RASCOMUnclassifiedIPv426

All 12 adjacent →

Provenance

Where this comes from

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