asn.dev

Observed topology

AS39835 GoeTel goetel GmbH

Residential RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS39835: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6892
AS33891Core-Backbone GmbHHostingIPv4 IPv6188
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv654
AS24482SG.GSHostingIPv4 IPv622
AS212024Marc SchmittUnclassifiedIPv4 IPv622
AS213241TECHIT.BE SRLResidentialIPv4 IPv622
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv619
AS8551Bezeq International Ltd.UnclassifiedIPv417
AS37100SEACOM LimitedUnclassifiedIPv417
AS20485Joint Stock Company TransTeleComUnclassifiedIPv416

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205376Dirk MeyerUnclassifiedIPv4 IPv6369
AS197639Hogrefe Verlag GmbH & Co. KGUnclassifiedIPv631

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,193
AS205376Dirk MeyerUnclassifiedIPv4 IPv6369
AS33891Core-Backbone GmbHHostingIPv4 IPv6238
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv655
AS197639Hogrefe Verlag GmbH & Co. KGUnclassifiedIPv631
AS24482SG.GSHostingIPv4 IPv630
AS212024Marc SchmittUnclassifiedIPv4 IPv630
AS213241TECHIT.BE SRLResidentialIPv4 IPv630
AS8551Bezeq International Ltd.UnclassifiedIPv421
AS37100SEACOM LimitedUnclassifiedIPv421

All 14 adjacent →

Provenance

Where this comes from

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