Observed topology
AS210316 ELEKOMS-AS
Unclassified Spamhaus ASN-DROP RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 196 |
Transit
Downstream networks
Networks for which AS210316 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202502 | LLC "ATOM3" | Unclassified | IPv4 | 360 |
| AS201572 | ECO-INITIATIVE LLC | Unclassified | IPv6 | 68 |
| AS200499 | Enterprises Holding LTD | Unclassified | IPv6 | 34 |
| AS200671 | START BUILDING LTD | Unclassified | IPv6 | 34 |
| AS201292 | Agrofirma Aleks PP | Unclassified | IPv6 | 34 |
| AS201380 | LLC "Alfa Biznes" | Unclassified | IPv6 | 34 |
| AS201836 | Garant-Plus-Inform LLC | Unclassified | IPv6 | 34 |
| AS202144 | TOV CHEMPIR | Unclassified | IPv6 | 34 |
| AS202171 | PP "TORERO" | Unclassified | IPv6 | 34 |
| AS202388 | KP "CLUB NADIYA" | Unclassified | IPv6 | 34 |
Adjacency
Adjacent networks
Every AS seen directly next to AS210316 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 964 |
| AS202502 | LLC "ATOM3" | Unclassified | IPv4 | 360 |
| AS201572 | ECO-INITIATIVE LLC | Unclassified | IPv6 | 68 |
| AS200499 | Enterprises Holding LTD | Unclassified | IPv6 | 34 |
| AS200671 | START BUILDING LTD | Unclassified | IPv6 | 34 |
| AS201292 | Agrofirma Aleks PP | Unclassified | IPv6 | 34 |
| AS201380 | LLC "Alfa Biznes" | Unclassified | IPv6 | 34 |
| AS201836 | Garant-Plus-Inform LLC | Unclassified | IPv6 | 34 |
| AS202144 | TOV CHEMPIR | Unclassified | IPv6 | 34 |
| AS202171 | PP "TORERO" | Unclassified | IPv6 | 34 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.