asn.dev

Observed topology

AS20722 ALLNET-AS IALOMICIOAREI Nr.20

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20722: 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
AS6204INTERKVM HOST SRLUnclassifiedIPv4401
AS3356Level 3 Parent, LLCTransitIPv4340
AS6939Hurricane Electric LLCTransitIPv492
AS12310iNES GROUP SRLUnclassifiedIPv424
AS34304Teen Telecom SRLUnclassifiedIPv418
AS24482SG.GSHostingIPv415
AS20764CJSC RASCOMUnclassifiedIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45035SC 3D Media Creation SRLUnclassifiedIPv4118
AS28721Allnet Cloud SrlUnclassifiedIPv489
AS56795B1 TV CHANNEL S.R.L.UnclassifiedIPv444

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6204INTERKVM HOST SRLUnclassifiedIPv4485
AS3356Level 3 Parent, LLCTransitIPv4472
AS45035SC 3D Media Creation SRLUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv4103
AS28721Allnet Cloud SrlUnclassifiedIPv489
AS56795B1 TV CHANNEL S.R.L.UnclassifiedIPv444
AS34304Teen Telecom SRLUnclassifiedIPv436
AS12310iNES GROUP SRLUnclassifiedIPv424
AS24482SG.GSHostingIPv420
AS20764CJSC RASCOMUnclassifiedIPv415

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.