asn.dev

Observed topology

AS39614 DAWICO

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39614: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6396
AS9002RETN LimitedUnclassifiedIPv4 IPv6214
AS6939Hurricane Electric LLCTransitIPv4 IPv6179
AS3356Level 3 Parent, LLCTransitIPv4 IPv6103
AS12732GutCon GmbHUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv621
AS8218Zayo Infrastructure France SAUnclassifiedIPv611
AS6797GlobalConnect ABUnclassifiedIPv410
AS33891Core-Backbone GmbHHostingIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218529f-quadrat IT GmbHUnclassifiedIPv4 IPv694
AS48596InterNetworX Management GmbHUnclassifiedIPv4 IPv628

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6458
AS9002RETN LimitedUnclassifiedIPv4 IPv6244
AS6939Hurricane Electric LLCTransitIPv4 IPv6197
AS3356Level 3 Parent, LLCTransitIPv4 IPv6103
AS218529f-quadrat IT GmbHUnclassifiedIPv4 IPv694
AS12732GutCon GmbHUnclassifiedIPv4 IPv655
AS48596InterNetworX Management GmbHUnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv623
AS8218Zayo Infrastructure France SAUnclassifiedIPv612
AS6797GlobalConnect ABUnclassifiedIPv411

All 11 adjacent →

Provenance

Where this comes from

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