asn.dev

Observed topology

AS35708 4b42 UG

Unclassified RIPE Route Server

Upstreams 0 carry this network
Downstreams 89 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 87
Upstream graph Who carries AS35708, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS35708 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35708: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 89

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

ASNetworkTypeFamiliesPaths seen
AS42WoodyNet, Inc.UnclassifiedIPv4 IPv681
AS401753BIXCE IncUnclassifiedIPv4 IPv622
AS219412Lewis BrownUnclassifiedIPv613
AS215760Adam GrazioliUnclassifiedIPv612
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv611
AS208694LEON AARON TIEKOETTERUnclassifiedIPv611
AS212034Zezhu YuUnclassifiedIPv610
AS60900Adrian Trifonov trading as Ssmidge TechnologiesUnclassifiedIPv69
AS148971Keibiin's Holdings LimitedUnclassifiedIPv69
AS213409Daniil KovalHostingIPv69

All 89 downstreams →

Adjacency

Adjacent networks

All 89

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

ASNetworkTypeFamiliesPaths seen
AS42WoodyNet, Inc.UnclassifiedIPv4 IPv689
AS209898ungleich glarus agUnclassifiedIPv633
AS401753BIXCE IncUnclassifiedIPv4 IPv622
AS215760Adam GrazioliUnclassifiedIPv617
AS219412Lewis BrownUnclassifiedIPv613
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv611
AS208694LEON AARON TIEKOETTERUnclassifiedIPv611
AS212034Zezhu YuUnclassifiedIPv610
AS60900Adrian Trifonov trading as Ssmidge TechnologiesUnclassifiedIPv69
AS148971Keibiin's Holdings LimitedUnclassifiedIPv69

All 89 adjacent →

Provenance

Where this comes from

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