asn.dev

Observed topology

AS35710 WEBERCLOUD weber.digital GmbH

Hosting RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS35710: 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
AS3320Deutsche Telekom AGMobileIPv4 IPv6552
AS6939Hurricane Electric LLCTransitIPv4 IPv6387
AS48200Opteamax GmbHUnclassifiedIPv4 IPv690
AS4809China Telecom Next Generation Carrier NetworkUnclassifiedIPv446
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS6797GlobalConnect ABUnclassifiedIPv413
AS8551Bezeq International Ltd.UnclassifiedIPv413
AS37100SEACOM LimitedUnclassifiedIPv413
AS24482SG.GSHostingIPv610
AS29632Netassist International EOODUnclassifiedIPv610

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48200Opteamax GmbHUnclassifiedIPv41

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS48200Opteamax GmbHUnclassifiedIPv4 IPv66,460
AS44393Securebit AGUnclassifiedIPv46,411
AS3320Deutsche Telekom AGMobileIPv4 IPv6552
AS6939Hurricane Electric LLCTransitIPv4 IPv6387
AS4809China Telecom Next Generation Carrier NetworkUnclassifiedIPv485
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS6797GlobalConnect ABUnclassifiedIPv413
AS8551Bezeq International Ltd.UnclassifiedIPv413
AS37100SEACOM LimitedUnclassifiedIPv413
AS24482SG.GSHostingIPv610

All 14 adjacent →

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.