asn.dev

Observed topology

AS210756 EDGECENTERLLC

Hosting RIPE Content

Upstreams 15 carry this network
Downstreams 23 this network carries
Adjacent (IPv4) 38
Adjacent (IPv6) 16
Upstream graph Who carries AS210756, and who carries them, drawn as a map up to the transit-free core. 8 exchanges Where AS210756 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 15

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.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv64,008
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,286
AS31133PJSC MegaFonMobileIPv4 IPv6698
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6617
AS8359MTS PJSCMobileIPv4 IPv6456
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6315
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv6196
AS50673Serverius Holding B.V.UnclassifiedIPv4132
AS6697Republican Unitary Telecommunication Enterprise BeltelecomResidentialIPv4 IPv6119
AS24482SG.GSHostingIPv4 IPv678

Transit

Downstream networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS57578Misaka Network, Inc.HostingIPv4 IPv6442
AS207059Unisender Smart LLCUnclassifiedIPv4 IPv6353
AS201589"EDGEAM" LLCUnclassifiedIPv4 IPv6285
AS61976JSC SelectelUnclassifiedIPv4 IPv6256
AS213922Volta LLCHostingIPv4248
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4194
AS21051ASTRUM LLCHostingIPv4186
AS8492"OBIT" Ltd.UnclassifiedIPv4183
AS25231State Budget Enterprise of Novosibirsk region "Novosibirsk region center of information technologies"UnclassifiedIPv4138
AS50299Thyphone Communications LLCUnclassifiedIPv4115

Adjacency

Adjacent networks

All 39

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv66,624
AS3216PJSC "Vimpelcom"MobileIPv4 IPv62,289
AS31133PJSC MegaFonMobileIPv4 IPv6854
AS42773Nemerov Evgeniy Vladimirovish PEUnclassifiedIPv4810
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6733
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4622
AS8359MTS PJSCMobileIPv4 IPv6556
AS57578Misaka Network, Inc.HostingIPv4 IPv6541
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv6420
AS207059Unisender Smart LLCUnclassifiedIPv4 IPv6353

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.