asn.dev

Observed topology

AS39083 DAVID-FROEHLICH IT-Service David Froehlich

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39083: 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
AS56382vServer.site LTDUnclassifiedIPv4 IPv656
AS44592SkyLink Data Center BVHostingIPv4 IPv617
AS44103The Mastermind Holding B.V.UnclassifiedIPv613
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv4 IPv62
AS401753BIXCE IncUnclassifiedIPv4 IPv62
AS12586GHOSTnet GmbHHostingIPv41
AS202365Omer GOLGELIUnclassifiedIPv41
AS206499LOCIX LIMITEDUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50801David FroehlichUnclassifiedIPv4 IPv6285

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50801David FroehlichUnclassifiedIPv4 IPv6285
AS56382vServer.site LTDUnclassifiedIPv4 IPv6193
AS44592SkyLink Data Center BVHostingIPv4 IPv688
AS6939Hurricane Electric LLCTransitIPv4 IPv662
AS44103The Mastermind Holding B.V.UnclassifiedIPv613
AS24482SG.GSHostingIPv4 IPv67
AS401753BIXCE IncUnclassifiedIPv4 IPv67
AS12586GHOSTnet GmbHHostingIPv45
AS202365Omer GOLGELIUnclassifiedIPv45
AS206499LOCIX LIMITEDUnclassifiedIPv45

Provenance

Where this comes from

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