asn.dev

Observed topology

AS20657 ATLANTIS Sofia, Bulgaria

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20657: 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
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4181
AS47453ITservice 2009 LTDUnclassifiedIPv4164
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4163
AS6939Hurricane Electric LLCTransitIPv481
AS34224Neterra Ltd.UnclassifiedIPv478

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47226AKAT TECHNOLOGIES LTDUnclassifiedIPv48
AS43063SOPHARMA JSCoUnclassifiedIPv47
AS201114AMK Drives and controls Ltd.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4192
AS47453ITservice 2009 LTDUnclassifiedIPv4164
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4163
AS34224Neterra Ltd.UnclassifiedIPv483
AS6939Hurricane Electric LLCTransitIPv481
AS47226AKAT TECHNOLOGIES LTDUnclassifiedIPv48
AS43063SOPHARMA JSCoUnclassifiedIPv47
AS201114AMK Drives and controls Ltd.UnclassifiedIPv41

Provenance

Where this comes from

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