asn.dev

Observed topology

AS211101 maxlink Nasteka Maksim Viktorovich

Unclassified APNIC

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS211101: 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
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4589
AS201776Miranda-Media LtdUnclassifiedIPv4262
AS41039Timer, LLCUnclassifiedIPv4231
AS6939Hurricane Electric LLCTransitIPv4180
AS24482SG.GSHostingIPv429
AS37721Virtual Technologies & SolutionsResidentialIPv429
AS49673Truenetwork LLCUnclassifiedIPv429
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv429
AS8447A1 Telekom Austria AGResidentialIPv417
AS50673Serverius Holding B.V.UnclassifiedIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210067Chayka VladimirUnclassifiedIPv462

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4589
AS201776Miranda-Media LtdUnclassifiedIPv4309
AS41039Timer, LLCUnclassifiedIPv4246
AS6939Hurricane Electric LLCTransitIPv4180
AS210067Chayka VladimirUnclassifiedIPv462
AS24482SG.GSHostingIPv429
AS37721Virtual Technologies & SolutionsResidentialIPv429
AS49673Truenetwork LLCUnclassifiedIPv429
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv429
AS8447A1 Telekom Austria AGResidentialIPv417

Provenance

Where this comes from

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