asn.dev

Observed topology

AS211623 NAML

Hosting RIPE

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS211623: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv632
AS213753InterEdge B.V.UnclassifiedIPv414
AS6204INTERKVM HOST SRLUnclassifiedIPv413
AS42093InterRacks B.V.HostingIPv46
AS5405Inter.link GmbHUnclassifiedIPv4 IPv63
AS61049Exascale LtdResidentialIPv4 IPv63
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29632Netassist International EOODUnclassifiedIPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62

All 26 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213619Tom Emming trading as NetbelaHostingIPv4 IPv661

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv680
AS213619Tom Emming trading as NetbelaHostingIPv4 IPv661
AS213753InterEdge B.V.UnclassifiedIPv414
AS6204INTERKVM HOST SRLUnclassifiedIPv413
AS29632Netassist International EOODUnclassifiedIPv66
AS42093InterRacks B.V.HostingIPv46
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS5405Inter.link GmbHUnclassifiedIPv4 IPv63
AS61049Exascale LtdResidentialIPv4 IPv63
AS213241TECHIT.BE SRLResidentialIPv63

All 28 adjacent →

Provenance

Where this comes from

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