asn.dev

Observed topology

AS19679 DROPBOX - Dropbox, Inc.

Hosting ARIN Content

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

Transit

Upstream networks

All 57

Networks observed carrying traffic for AS19679: 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 IPv6750
AS3356Level 3 Parent, LLCTransitIPv4 IPv6504
AS6939Hurricane Electric LLCTransitIPv4 IPv6486
AS4637Telstra GlobalUnclassifiedIPv4 IPv6254
AS2914NTT America, Inc.TransitIPv4 IPv6219
AS174Cogent Communications, LLCTransitIPv4 IPv6212
AS6461Zayo BandwidthTransitIPv456
AS7474SingTel Optus Pty LtdUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv633
AS9002RETN LimitedUnclassifiedIPv4 IPv631

Transit

Downstream networks

inferred

Networks for which AS19679 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

All 57

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6750
AS3356Level 3 Parent, LLCTransitIPv4 IPv6504
AS6939Hurricane Electric LLCTransitIPv4 IPv6486
AS4637Telstra GlobalUnclassifiedIPv4 IPv6254
AS2914NTT America, Inc.TransitIPv4 IPv6219
AS174Cogent Communications, LLCTransitIPv4 IPv6212
AS6461Zayo BandwidthTransitIPv456
AS7474SingTel Optus Pty LtdUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv633
AS9002RETN LimitedUnclassifiedIPv4 IPv631

Provenance

Where this comes from

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