asn.dev

Observed topology

AS16010 MagticomAS Magticom Ltd.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16010: 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
AS44327DELTA COMM LLCUnclassifiedIPv4 IPv62,734

Transit

Downstream networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS25249Magticom Ltd.UnclassifiedIPv4780
AS44327DELTA COMM LLCUnclassifiedIPv4240
AS57881JSC ENERGO-PRO GeorgiaUnclassifiedIPv4136
AS201356JSC "VTB Bank Georgia"UnclassifiedIPv4122
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4120
AS139341ACEHostingIPv4 IPv692
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv691
AS47644JSC TBC BANKUnclassifiedIPv471
AS218574Primenet LLCUnclassifiedIPv460
AS203039Cavea Plus LLCHostingIPv459

All 36 downstreams →

Adjacency

Adjacent networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS44327DELTA COMM LLCUnclassifiedIPv4 IPv66,255
AS25249Magticom Ltd.UnclassifiedIPv4785
AS57881JSC ENERGO-PRO GeorgiaUnclassifiedIPv4136
AS201356JSC "VTB Bank Georgia"UnclassifiedIPv4122
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4120
AS203039Cavea Plus LLCHostingIPv4119
AS139341ACEHostingIPv4 IPv692
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv691
AS47644JSC TBC BANKUnclassifiedIPv471
AS218574Primenet LLCUnclassifiedIPv460

All 36 adjacent →

Provenance

Where this comes from

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