asn.dev

Observed topology

AS33962 DATAHOUSE-EKT Ekt branch

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33962: 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
AS29076Citytelecom LLCHostingIPv4 IPv683
AS12389PJSC RostelecomResidentialIPv4 IPv678
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv655
AS1299Arelion Sweden ABTransitIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44128Internet-Pro LLCUnclassifiedIPv4 IPv6102
AS44428HOST EXPERT LLCUnclassifiedIPv462
AS57973LLC VKUnclassifiedIPv462
AS51346Opened Joint Stock Company "Tojiktelecom"UnclassifiedIPv457
AS57898DNS Retail Ltd.UnclassifiedIPv424

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6212
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6158
AS29076Citytelecom LLCHostingIPv4 IPv6153
AS44128Internet-Pro LLCUnclassifiedIPv4 IPv6102
AS44428HOST EXPERT LLCUnclassifiedIPv462
AS57973LLC VKUnclassifiedIPv462
AS51346Opened Joint Stock Company "Tojiktelecom"UnclassifiedIPv457
AS57898DNS Retail Ltd.UnclassifiedIPv424
AS1299Arelion Sweden ABTransitIPv63

Provenance

Where this comes from

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