asn.dev

Observed topology

AS39775 HYPERNET-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39775: 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
AS3216PJSC "Vimpelcom"MobileIPv4271
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv472
AS31133PJSC MegaFonMobileIPv460
AS50673Serverius Holding B.V.UnclassifiedIPv48
AS24482SG.GSHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS49673Truenetwork LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41925Limited Liability Company Izet Telecom UralUnclassifiedIPv465
AS56436Ministry of Information Technologies and Communications of Chelyabinsk RegionUnclassifiedIPv47
AS202835Prom-Komplekt LLCUnclassifiedIPv46

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4315
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv492
AS41925Limited Liability Company Izet Telecom UralUnclassifiedIPv473
AS31133PJSC MegaFonMobileIPv460
AS50673Serverius Holding B.V.UnclassifiedIPv417
AS6939Hurricane Electric LLCTransitIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS56436Ministry of Information Technologies and Communications of Chelyabinsk RegionUnclassifiedIPv47
AS202835Prom-Komplekt LLCUnclassifiedIPv46
AS24482SG.GSHostingIPv45

All 11 adjacent →

Provenance

Where this comes from

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