asn.dev

Observed topology

AS39384 RACKFIBER

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39384: 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
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv6327
AS174Cogent Communications, LLCTransitIPv4 IPv6225
AS6939Hurricane Electric LLCTransitIPv4 IPv682
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv632
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv6327
AS174Cogent Communications, LLCTransitIPv4 IPv6225
AS6939Hurricane Electric LLCTransitIPv4 IPv682
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv632
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS25091IP-Max SAUnclassifiedIPv62

Provenance

Where this comes from

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