Observed topology
AS210756 EdgeCenterLLC EdgeCenter LLC
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS210756: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 4,131 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,281 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 720 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 699 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 420 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 332 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 194 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 134 |
| AS6697 | Republican Unitary Telecommunication Enterprise Beltelecom | Residential | IPv4 IPv6 | 119 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 79 |
Transit
Downstream networks
Networks for which AS210756 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57578 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 424 |
| AS207059 | Unisender Smart LLC | Unclassified | IPv4 IPv6 | 358 |
| AS61976 | JSC Selectel | Unclassified | IPv4 IPv6 | 297 |
| AS201589 | "EDGEAM" LLC | Unclassified | IPv4 IPv6 | 285 |
| AS213922 | Volta LLC | Hosting | IPv4 | 252 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 199 |
| AS21051 | ASTRUM LLC | Hosting | IPv4 | 189 |
| AS8492 | "OBIT" Ltd. | Unclassified | IPv4 | 186 |
| AS25231 | State Budget Enterprise of Novosibirsk region "Novosibirsk region center of information technologies" | Unclassified | IPv4 | 140 |
| AS50299 | Thyphone Communications LLC | Unclassified | IPv4 | 118 |
Adjacency
Adjacent networks
Every AS seen directly next to AS210756 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 6,744 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 2,250 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 854 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 837 |
| AS42773 | Nemerov Evgeniy Vladimirovish PE | Unclassified | IPv4 | 776 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 633 |
| AS57578 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 520 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 518 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 417 |
| AS207059 | Unisender Smart LLC | Unclassified | IPv4 IPv6 | 358 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.