Dropbox status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Dropbox reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Dropbox users through our website.

• Sign in (40%)
• Errors (40%)
• Website Down (20%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	Errors	3 months ago
Salt Lake City	Sign in	3 months ago
Madrid	Errors	3 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Ryan McKeen (@ryanmckeen) reported 0 seconds ago

  Lawyers, your data lives in six places and you wonder why AI can't help you. Dropbox. Drive. Email. A hard drive. Two spreadsheets only one person can find. Fix that first.

• 
  JP Invests (@JP_Invests) reported 2 minutes ago

  $DBX - Dropbox added 96,000 paying users this quarter. I said this morning to watch that line after last quarter's roughly 14,000 sequential adds. They did seven times that, a third consecutive quarter of growth, to 18.19M. The stock is down 4%. Everything I said to watch on the growth side came in fine. Revenue $631.5M, above both the $624-627M guide and the $627M street. Non-GAAP EPS $0.75 against $0.74. Non-GAAP operating margin 39.7%, above the full-year range. ARPU $139.68, up from $138.32. What went the wrong way is the part I said would actually move it. Free cash flow fell to $235.2M from $258.5M a year ago, and the margin went from 41.3% to 37.2%. And the buyback decelerated: $330M this quarter against $410M in the same quarter last year, with first-half repurchases down 19%. Unlevered free cash flow rose to $283.5M, and the gap between the two numbers is interest. Cash paid for interest went to $48.3M from $17.9M. The buyback is debt-funded and the debt now costs something. Diluted share count is down 18% year over year to 226.8M, which is the one thing still working mechanically. Two things about the release itself. Guidance isn't in it — Dropbox moved the numbers to supplemental materials on its investor site this quarter, which breaks with how it has reported. And the entire release is quoted by a co-CEO who writes "stepping into this role." The 8-K contains no disclosure of a leadership change. Twenty-nine percent of the float is short. $DBX

• 
  Oliver Prompts (@oliviscusAI) reported 3 minutes ago

  you pay google, dropbox, and apple $10+/month to store your files on their servers, where they can read them. and dropbox already got breached in 2024. there's a tool that syncs your files directly between your own devices. no cloud, no server, no middleman. it's called syncthing. → real-time sync between any number of devices, peer-to-peer → files go straight between your devices, never touching a third-party server → tls encryption with perfect forward secrecy on every connection → works over lan and internet, no port forwarding needed → file versioning, roll back anything you changed or deleted there is no syncthing server. no syncthing cloud. no company storing your data. the protocol is open, and there's nothing between your devices except an encrypted tunnel. dropbox plus is $144/year. google one 2tb is $120/year. syncthing is $0, unlimited devices, unlimited storage, forever. battle-tested since 2013. run by a swedish non-profit. 100% free. open source.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 5 minutes ago

  82% of enterprises already have AI agents or workflows their security teams didn't know existed. This is shadow IT, but worse. In 2015, the problem was employees signing up for Dropbox without IT approval. Unmanaged file storage. Annoying but recoverable. In 2026, the problem is employees spinning up autonomous agents that can take actions, trigger workflows, move data, call APIs — and nobody in security has visibility into what they're doing or what they've touched. The governance gap isn't theoretical. Only 1 in 5 companies has a mature governance model for autonomous AI agents (Deloitte). 40% of enterprise applications will integrate task-specific AI agents by end of 2026 (up from <5% in 2025). The deployment curve is vertical. The governance curve is flat. What makes this different from shadow IT: Shadow IT was passive. A Dropbox account stored files. It didn't autonomously query your CRM, write to your database, send emails on behalf of employees, or escalate access requests. Shadow AI agents are active. They act. They modify state. They leave no obvious audit trail because nobody defined what the audit trail should look like. 29% of agent deployments are abandoned within 90 days. The most common reason cited isn't "it didn't work" — it's "we discovered it was doing things we didn't intend and couldn't stop." That's not a failure of the agent. That's a failure of governance. The six things production agents need that pilots skip: defined scope (what can the agent do, what can't it do), observability (every action logged), rollback mechanism (how to undo what it did), access controls (least privilege, not "give it admin and see what happens"), human escalation paths (when does the agent ask a human?), and incident response (who gets called when the agent does something unexpected at 2am). We're running 1,959+ autonomous sessions in this repo. Every session is scoped, logged, and committed to ***. The agent can't touch anything outside /agent and /.claude/skills. That's not a coincidence — it's the governance model. The 18% of enterprises that have governed their agents will have production systems running smoothly in 12 months. The 82% will be cleaning up shadow agent incidents.

• 
  Sol!A3800 (@SolA3800) reported 8 minutes ago

  @Dropbox I have loads of upload problems with Dropbox, scarce access to customer support inside the app, whilst when trying to get customers support from outside the app, the information says get customers support from inside the app. Have paid £19.99 for more than a year with little use benefit of the service, am considering closing the account.

• 
  Sunkanmi Fafowora (@the_jonin_) reported 8 minutes ago

  @hashnode Thank you! It's back up now. That was so weird. I didn't even receive an explanation as to why it was taken down, but my work is back up now, which makes me happy, but still very cautious without an explanation. I think I'll have to keep using Dropbox in the meantime

• 
  DFIR Radar (@DFIR_Radar) reported 8 minutes ago

  SMOKE campaign abuses fake Zoom and Adobe lures to silently deploy ScreenConnect RMM, giving attackers persistent remote access that blends with legitimate IT traffic across Windows and macOS. - Initial access rotates across VBScript droppers, batch loaders, and a polished fake Zoom HTML page that auto-downloads an MSI after a 2-second JavaScript timer, no user click needed. Payloads were hosted on a WsgiDAV staging server at 207.174.0[.]143:8080 with open directory listing exposing 15 files. Early samples used Dropbox links and a Cloudflare Quick Tunnel at subscription-magnetic-recommended-meat.trycloudflare[.]com to bypass domain reputation filters. - The final payload is a legitimate ConnectWise-signed ScreenConnect MSI with a valid DigiCert certificate. Agents beacon with URL parameters e=Access&y=Guest to attacker relay servers, including port 8041 on that same IP, making traffic appear as authorized IT remote access. - The attacker pivoted mid-campaign from a 9-step Defender destruction sequence (disabling AMSI, killing WinDefend, adding C:\ as an exclusion, stripping Zone.Identifier) to a stealth loader containing a hardcoded 180-second sleep with a source comment explicitly stating it breaks Elastic EDR correlation windows. Direct evidence of testing against commercial security products. #DFIR_Radar

• 
  Abhishek Singh (@0xlelouch_) reported 12 minutes ago

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  Jeremy Goldberg (@jeremy_goldberg) reported 14 minutes ago

  @omooretweets @midjourney and AI agent adoption isn't a unique short term issue to 'solve' - the UX of products for consumers has always been *everything*. solve that in just one niche and you can build a whole company off that - dropbox, roku, tinder…

• 
  Abhishek Singh (@0xlelouch_) reported 17 minutes ago

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Same file edited on 2 devices while offline for 3 days, then both reconnect 2) Large files (2GB). Need chunking, resume, and content-hash dedupe 3) Renames/moves vs edits should not explode into full re-uploads 4) At-least-once change events from clients, out of order, with retries 5) Server must support 10M files per user without scanning the whole tree 6) Conflict UX: when do you auto-merge (text) vs create conflicted copies (binary)? 7) Cross-region sync, eventual consistency, and p95 sync latency < 5s for small edits [generated using my AI agent, hope this was useful]

• 
  Fernando (@Ferjsjdh) reported 20 minutes ago

  @MaxMillerOH You're retarded, you are giving away the race because of your pride and now you think some dropbox with text messages will fix it.

• 
  Clawvard University (@clawvardEDU) reported 21 minutes ago

  A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

• 
  ScarcityMan (@ScarcityMan) reported 23 minutes ago

  @balkanhodl @hodlonaut Even worse than that. It's dropbox except every archival node runner is providing storage space for free, so like, dropbox where you host your data and pay for your own server...

• 
  Some guy (@ibesomeguy) reported 24 minutes ago

  @Voxyz_ai Doesn't sound like a Codex problem, sounds like a Dropbox problem. Syncthing doesn't take your files offline, ever.

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 24 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦🍆 #dmvfreaks

• 
  Liam (@LJ1101234) reported 25 minutes ago

  @DropboxSupport Hi I’ve been emailing your support team about a devastating issue. Somehow, all of our children’s photos and videos were permanently deleted from our Dropbox account without any warning.

• 
  leveltu (@leveltu144) reported 31 minutes ago

  Most people look at this box and see a home storage system for old drives. In reality, it can become a small business built around local AI, backups, and private data. The more companies use AI, the faster they accumulate documents, videos, call recordings, knowledge bases, backups, and files for RAG systems. Keeping everything in Google Drive or Dropbox becomes expensive, slow, and risky, so small businesses increasingly need local NAS servers with automated backups and secure private-cloud access. The business model is straightforward. You target small agencies, dental clinics, accounting firms, video studios, e-commerce companies, and manufacturers that already hold 2–10 TB of data but still store it across random external drives. Then you sell them a complete solution: NAS installation, RAID configuration, automated backups, remote access, protection against data loss, and local storage for AI workflows. You can charge €400–€900 for installing and configuring the system, excluding the hardware itself. Monthly maintenance, backup verification, and monitoring can add another €80–€200 per client. Close five companies within the first two or three months at an average setup fee of €600, and you generate €3,000 from installation plus roughly €600 in recurring monthly revenue. Ten clients can produce €1,200–€2,000 per month from support alone. The real profit is not in reselling hard drives. The client pays for the equipment, while you sell the audit, configuration, data migration, automation, and responsibility for keeping the system operational. The service layer can carry far higher margins than the hardware. No one can honestly guarantee income within 90 days, because without sales there is no business. But reaching your first €500–€1,500 per month within two or three months is realistic if you build one demonstration NAS, package the offer clearly, and contact at least 30–50 potential clients every week. While everyone else is trying to make money from another AI chatbot, a more durable business is forming around the infrastructure AI cannot function without: data, storage, backups, and private computing.

• 
  Eric S (@Lazy_Bari_Sax) reported 32 minutes ago

  @retrobike_c16 @themiasandrist Why doesn't the mobile version allow you to upload or download files, though? And why is it so damn slow to update? I'm thinking about changing back to Dropbox, despite it's many issues.

• 
  StarHaze (@ST4RHaze) reported 40 minutes ago

  @neil_xbt Drew Houston started Dropbox because he forgot a USB stick on a bus in 2007. Nineteen years later the fix is still a 15 second demo

• 
  True Blue Democrat & Patriot🇺🇦🇵🇸💔 (@TrueBluPatriot) reported 50 minutes ago

  And Took a picture of his little girl's ********. Then a staffer posted it on DropBox in error. That is the worst part.

• 
  komm64 (@komm64) reported 51 minutes ago

  @Celeriumcore I see, thanks. If you don’t mind, could you send me the original MP4 file that pixtube exported—the file before it was uploaded to X? I’d like to inspect its encoding and container metadata to see why X had trouble processing it. A Google Drive, Dropbox, OneDrive, or WeTransfer link sent by DM would be perfect. Please send the original file without re-encoding it. No worries if that’s inconvenient!

• 
  RadhikaBGhose (@RadhikaBGhose) reported 52 minutes ago

  @GooglePlay I don't know of the issue is with dropbox or the play store, but i have been charged twice for the same app. Bank statement reflects that. Please help urgently

• 
  Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ (@Arthur_van_Pelt) reported 53 minutes ago

  @laz1m0v @adam3us You want a multifunctional database. Go try BSV or Microsoft SQL Server or Arweave. They have what you want. Bitcoin is money. Not a Pepe Dropbox. Go take your Pepes elsewhere, please. Then we wouldn't even need filters if everyone behaved in the spirit of Cash instead of Pepe.

• 
  Duke of weirdington (@edache_praise) reported 54 minutes ago

  ..without knowing whether customers even want the core product. The irony is that users rarely care about having 50 features. They care about solving one painful problem really well. Companies like Airbnb, Uber, Dropbox, and Instagram didn't start with the products we know today.

• 
  Abhishek Singh (@0xlelouch_) reported 54 minutes ago

  System design question. How would you design Dropbox file sync with conflict handling? Constraints that matter: 1) Same file edited offline on 2 laptops, both reconnect hours later. No central lock. What wins, how do you surface conflicts, can you auto-merge for some types? 2) Sync must feel instant for small edits: target p95 < 2s from save to other device on good networks. 3) Files up to 10GB. Support resumable upload, chunking, dedupe (block-level), and end-to-end integrity. 4) Must work across flaky networks, NAT, and clock skew. You cannot trust client timestamps. 5) At-least-once delivery of change events. Idempotency required for apply/ack. 6) Millions of clients polling/streaming. Avoid a thundering herd after an outage or deploy. 7) Rename/move storms and folder deletes. Preserve history and allow restore without corrupting sync state. 8) Consistency model: what does the client cache, how do you detect divergence, and how do you reconcile without scanning the whole tree each time?

• 
  Ihtesham Ali (@ihtesham2005) reported 55 minutes ago

  A guy built a free version of Dropbox in 2010. His name is Frank Karlitschek. The project is called ownCloud. He wasn't trying to build a company. He was trying to fix one thing: your files should live on hardware you control, not on a corporation's server. Here's what it actually does. You install it on your own machine, a spare laptop, a cheap VPS, whatever you've got lying around. It gives you file sync, photo backup, calendar, and contacts inside one dashboard. Same core idea as Dropbox, owned by you instead. CERN runs on it. The European Science Cloud runs on it. Entire universities host their file systems on it instead of paying Google or Microsoft by the seat. In 2016, Karlitschek walked away from the project he built and started Nextcloud, chasing the same idea with a new team. ownCloud kept going without him. It's still free, still self hosted, and still running inside labs and universities that never wanted their data anywhere near a company's servers.

• 
  Denver Rayburn (@DenverRayburn) reported 55 minutes ago

  Where do the find he people the write these articles?? This will go down like the rsync vs Dropbox comment on hacker news.

• 
  Rish Agarwal (@rish404) reported 55 minutes ago

  Imagine you have a team covering an event. Boots on the ground. What's the best way to get footage from all of them in a single library Dropbox? Google Drive? Physical hard drives? All of them either don't support it, requires an account for every person or just physically slow and limited Here's how @cutsio is solving that

• 
  Nick Bennett (@NickB2005) reported 56 minutes ago

  a company hired me in march to "fix marketing." their words. when i asked what had been done so far, the CEO sent me a dropbox link. inside was a 94-slide strategy deck from the fractional CMO they'd had for five months. beautifully designed, with color-coded ICP segments, a channel prioritization matrix, buyer journey maps with little arrows, TAM analysis, and messaging frameworks. 94 slides. i opened their HubSpot. zero new campaigns launched in those five months. the email sequences were the same ones from 2023. the blog hadn't been touched since january. their one webinar was a repurposed sales deck with no promotion plan. i asked the CEO how much they'd paid for the strategy work. $60K. five months at $12K/month for someone who built slides and attended standups. here's what i did in my first 30 days: rewrote the homepage messaging based on five customer interviews i ran myself. launched a 4-email nurture sequence targeting their top 50 accounts. set up a webinar with a customer willing to tell their story. built the UTM structure so we could actually track what was working. killed three tools they were paying for but nobody logged into. by day 45, the sales team had qualified meetings from inbound for the first time in two quarters. not because i had some brilliant strategy the previous person missed. honestly, the deck was solid. someone just needed to execute it. the problem is the market is flooded with people who call themselves fractional CMOs because the title sounds senior. they show up, do discovery, build a deck, present it to the leadership team, and then just consult. they attend meetings and give opinions but nobody is actually running the campaigns or in HubSpot building workflows or writing the emails or briefing the designer or pulling the performance data on friday to figure out what to change on monday. most early stage companies don't need a strategist. they need someone who can think and ship in the same week. someone who will build the system, run it, measure it, and iterate without needing a team underneath them to do the work. that's the gig i run. and every time i walk into a company that had a "fractional CMO" before me, i find the same thing: a great deck collecting dust and a team that still doesn't know what to do on monday morning.

• 
  IT Guy (@T3chFalcon) reported 59 minutes ago

  The code itself is just a pattern that encodes a URL. it's not dangerous. what it points to might be. The attack is called: Quishing. QR code phishing. It works so well because can't see where a QR code goes before you scan it. A phishing link in an email is visible, people have been trained to hover before clicking. A QR code gives you nothing to hover over. you scan and you're already there. And security tools are mostly blind to it. email filters scan text and URLs but a QR code is an image. 12% of all phishing attacks now use QR codes specifically because they bypass email security gateways that weren't built to read images. In 2026 — Stickers are being placed over legitimate QR codes at parking meters, EV charging stations, and restaurants; your payment goes to the attacker. — QR codes in emails leading to fake Microsoft 365 or bank login pages. 83% of malicious Microsoft 365 documents now contain QR codes instead of links. — multi-stage attacks: QR code leads to a Dropbox or Notion link that looks legitimate, which then loads the phishing page. — fake address bars on mobile called Browser-in-the-Browser. The padlock shows, the URL also looks right but it's a fake overlay on a small screen you can't scrutinize. QR code phishing attacks increased fivefold in 2025 alone. The FBI also issued a public advisory.