asn.dev

Observed topology

AS39781 DIABOLOCOM Diabolocom SAS

Hosting RIPE Network Services

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS39781: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6189
AS9002RETN LimitedUnclassifiedIPv4 IPv6159
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS30781Free Pro SASHostingIPv4 IPv688
AS24482SG.GSHostingIPv4 IPv613
AS34019Hivane AssociationUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613
AS6696VERIXI SAUnclassifiedIPv48
AS34927iFog GmbHHostingIPv47

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47314VINCI SAUnclassifiedIPv430
AS9149Groupement des cartes bancaires GIEUnclassifiedIPv412

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6194
AS9002RETN LimitedUnclassifiedIPv4 IPv6176
AS6939Hurricane Electric LLCTransitIPv4 IPv6124
AS30781Free Pro SASHostingIPv4 IPv695
AS47314VINCI SAUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv615
AS34019Hivane AssociationUnclassifiedIPv4 IPv614
AS9149Groupement des cartes bancaires GIEUnclassifiedIPv412

All 13 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.