asn.dev

Observed topology

AS210316 ELEKOMS-AS

Unclassified Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210316: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6196

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS202502LLC "ATOM3"UnclassifiedIPv4360
AS201572ECO-INITIATIVE LLCUnclassifiedIPv668
AS200499Enterprises Holding LTDUnclassifiedIPv634
AS200671START BUILDING LTDUnclassifiedIPv634
AS201292Agrofirma Aleks PPUnclassifiedIPv634
AS201380LLC "Alfa Biznes"UnclassifiedIPv634
AS201836Garant-Plus-Inform LLCUnclassifiedIPv634
AS202144TOV CHEMPIRUnclassifiedIPv634
AS202171PP "TORERO"UnclassifiedIPv634
AS202388KP "CLUB NADIYA"UnclassifiedIPv634

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6964
AS202502LLC "ATOM3"UnclassifiedIPv4360
AS201572ECO-INITIATIVE LLCUnclassifiedIPv668
AS200499Enterprises Holding LTDUnclassifiedIPv634
AS200671START BUILDING LTDUnclassifiedIPv634
AS201292Agrofirma Aleks PPUnclassifiedIPv634
AS201380LLC "Alfa Biznes"UnclassifiedIPv634
AS201836Garant-Plus-Inform LLCUnclassifiedIPv634
AS202144TOV CHEMPIRUnclassifiedIPv634
AS202171PP "TORERO"UnclassifiedIPv634

Provenance

Where this comes from

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