asn.dev

Observed topology

AS35908 VPLSNET

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35908: 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
AS1299Arelion Sweden ABTransitIPv4 IPv616,616
AS6939Hurricane Electric LLCTransitIPv4 IPv64,297
AS4213Krypt TechnologiesHostingIPv4 IPv63,293
AS174Cogent Communications, LLCTransitIPv4 IPv61,904
AS45652VPLS ASIAUnclassifiedIPv4360
AS3257GTT Communications Inc.TransitIPv4 IPv681
AS396356Latitude.shHostingIPv458
AS24723Atman Sp. z o.o.HostingIPv435

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11051Evocative, Inc.HostingIPv4186
AS45652VPLS ASIAUnclassifiedIPv4121

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv616,766
AS6939Hurricane Electric LLCTransitIPv4 IPv64,411
AS4213Krypt TechnologiesHostingIPv4 IPv63,296
AS174Cogent Communications, LLCTransitIPv4 IPv61,929
AS45652VPLS ASIAUnclassifiedIPv4481
AS11051Evocative, Inc.HostingIPv4186
AS3257GTT Communications Inc.TransitIPv4 IPv696
AS396356Latitude.shHostingIPv458
AS24723Atman Sp. z o.o.HostingIPv435

Provenance

Where this comes from

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