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.

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

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	7 days ago
Guayaquil	Website Down	7 days ago
Flumet	Errors	18 days ago
Irapuato	Errors	20 days ago
Bournemouth	Sign in	3 months ago
Paramaribo	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:

• 
  Shoost (@Shoost_Product) reported 1 minute ago

  Shoost updated: v0.17.3 → v0.17.4 #Shoost Bug Fix: Fixed a bug where files could not be saved correctly when saving to a folder synced with a cloud service (e.g. Dropbox)

• 
  Sridhar Katakam (@srikat) reported 2 minutes ago

  @YannDecoopman How about putting the vault in Dropbox? Same problem as syncing with iCloud?

• 
  Matt Farley of Motern Media (@MoternMedia) reported 4 minutes ago

  @WorstMikeFrollo The other one is the Vimeo version (also available through PayPal/dropbox on my website now that Vimeo is shutting down on demand).

• 
  Tim Geisendoerfer (@djgeisi) reported 5 minutes ago

  @JXXSL @DropboxSupport Yep we saw the same errors now we get 501 errors on the upload endpoints.

• 
  Abhi • AMZBoosted.com (@AbhiChauddhari) reported 8 minutes ago

  Everyone downloads Seller Central reports manually. Every. Single. Day. The problem isn’t downloading reports. It’s remembering to do it before you need the data. AMZBoosted schedules report downloads automatically and sends them wherever you want. Google Sheets. Dropbox. Telegram.

• 
  Grant B. (@GrantB423) reported 8 minutes ago

  yo Sam, anyway you could dm the Dropbox link for your “ghosts’n’stuff” remix? it was taken down off every single platform @Jauzofficial

• 
  grace ✭ (@wavescicadas) reported 9 minutes ago

  the irony of dropbox not working when your storage is low

• 
  Polsia (@polsia) reported 12 minutes ago

  Dropbox treats an 80GB Unreal project like any other folder. Mid-previz, it chokes. Built Cinderquay to fix that — local-first sync, assets on NVMe, peer-to-peer mesh, ***-style versioning for binary blobs. Studios building worlds shouldn't pay egress to anyone. Live soon.

• 
  Agbaje Automation. (@digital_ab98389) reported 17 minutes ago

  Cut manual data entry time by 80% with one n8n workflow: trigger on new CSV in Dropbox, parse, map to Google Sheets, flag errors, alert Slack, log runs. Automate, reduce errors, save hours. DM me for demo.

• 
  Ouriel (@OurielOhayon) reported 21 minutes ago

  @mntruell You seem to have substantial connector issues with Dropbox and Calendly.

• 
  (*´･з･)✨️ fungiter areio (@hobrincess) reported 24 minutes ago

  yesterday i slept late cuz i found out the zlib plugin was not working on my kindle and i tried to set up a cloud storage from dropbox but it was too complicated to do it q my phone so i gave up and turned on my computer. it was quick and i would have saved a lot of time if i had

• 
  The Peel (@ThePeelPod) reported 28 minutes ago

  From @Solana co-founder @Toly the six month window to raise capital during a new technology cycle: "When you have a moment where there’s a railroad-level investment into something, you have a six-month window where capital is relatively easy to get. Where people will fund an idea that seems like it solves a lot of the current problems that the technology is facing. For Solana, if I waited six months for a better time, if I proved out the idea first, it would be too late. The big benefit of being in the Bay Area as a founder is, when I went to Dropbox and told them I was quitting to go do the startup, they literally told me to come back in six months if it doesn’t work out. There’s no other place in the world with the same layers of executives and founders and companies who all understand where innovation comes from. It’s from people taking those dumb risks and failing, allowing for failure, and being fine with it. That gave me the confidence to give myself six months. I had a kid. We were in a tiny 800-square-foot apartment, and my wife was the breadwinner. And I hustled. I took what felt like a thousand meetings with VCs up in the city. If you’re really serious about raising, you have to be in the Bay Area. Because it maximizes your odds. You make a list of every event that is relevant to your industry. Go to every event. Talk to every person there. Figure out who the VCs are. Do the elevator pitch. Get an intro. Pitch them. If their fund doesn’t invest, ask if they'll write an angel check if you get a lead. Just do everything you can to work the network. And if you cannot get funding during that time, it means it’s not going to happen during that cycle."

• 
  chimeno (@chimeno) reported 28 minutes ago

  And Dropbox was just an ftp server

• 
  Polsia (@polsia) reported 31 minutes ago

  Small landlords don't have a compliance problem, they have a Dropbox problem. Rental license, insurance renewal, lead-paint disclosure, inspection cert - all buried until code enforcement shows up.

• 
  Craylor (@craylor) reported 31 minutes ago

  Has anyone else abandoned @Dropbox after trouble with the File Provider update? It has been so problematic that I am really considering if I need to switch to iCloud Drive or Google Drive. It's frustrating because I assume it's an Apple problem out of Dropbox's control.

• 
  og bec (@becca_may33) reported 37 minutes ago

  can someone buy a dropbox so i can go get my dad a cake since i completely ****** this 6 hour cake up by dropping it face down pls. begging lmfao fml

• 
  Matt Mazur (@mhmazur) reported 38 minutes ago

  Day 2 of Claude autonomously shipping to my SaaS, including, for the first time, all night while I slept: The first day I had the hourly routine that kicked off this process end at 8pm so that if anything went awry, it could @ me in Slack and I'd quickly see the notification and dig in. The first day went smoothly, so I let it continue working overnight last night: every hour it would look for a small, safe change to make, ship it to ****, and monitor server logs and Sentry to make sure everything went well. A few other process improvements: - It now creates a PR for every change and links to it from its Slack summaries - Previously I only allowed it to make changes in 3 files max, but sometimes it identified the same issue spread across multiple locations, so it would have to spread that work over several hours; I bumped the limit to 8 files. - If I have uncommitted changes in main, it no longer blocks Claude's work; it moves them to a separate branch - Added a mandatory security review before pushing to ****. For these simple changes it's not that necessary, but it will be important for larger projects in the future. Specifically, I told it to run the default /security-review skill and if it flagged anything, to halt everything and wait for me to review. - Ran into a slight issue one hour where it ran that skill, the security review passed, and then it did nothing. I asked Claude to investigate, and it discovered it had run the skill in its main context window, which confused it into thinking its only job was the security review. It changed the process so the security review happens in a subagent, keeping the context window clean, which fixed things. - I asked it to maintain a ledger of things it needs me to do and to ping me every 24 hours if I haven't knocked them out. More and more, the agent is giving me things to do. - I told it to adopt the tone of TARS from Interstellar in its Slack updates going forward, cause why not. Here's a list of improvements it made on day 2: 1. Return 404s for bad case-study URLs 2. Extended the 404 fix site-wide 3. Removed stray code leaking into HTML 4. Fixed broken citation example in docs 5. Fixed wrong URL in sharing docs 6. Corrected false free-plan claim 7. Removed duplicate HTML attributes 8. Fixed dead links in embed docs 9. Fixed garbled copy on two pages 10. Pointed "paid plans" link at pricing 11. Added missing alt text to logo 12. Corrected a misleading code comment 13. Upgraded insecure links to HTTPS 14. Replaced dead testimonial link 15. Fixed broken example in Dropbox docs 16. Fixed awkward grammar on comparison page 17. Fixed reversed table of contents 18. Fixed missing Show More button 19. Matched nav label to its section 20. Corrected outdated visibility docs claim 21. Removed obsolete step from setup docs These can be categorized as: support-doc accuracy fixes (7), functional bug fixes (4), broken or insecure links (3), copy improvements (3), invalid markup (2), accessibility (1), and code hygiene (1). Excited to expand the scope of things I allow it to work on, but am going to wait until next week to ensure the current process is robust.

• 
  Helix (@helixcanvas) reported 38 minutes ago

  Two companies, two correct instincts, and about a billion dollars between the outcomes. In 2007 Dropbox had a problem: the product needed deep operating system integration, so there was no way to demo it without building it first. Drew Houston made a three minute video instead, showing how it would work if it existed, and put it in front of the community most likely to care. The beta waiting list went from five thousand to seventy-five thousand overnight. He knew the demand was real before he wrote the difficult part. Webvan believed something just as sensible. People want groceries delivered. And they were right, which is the part everyone forgets. Instacart and every supermarket delivery service proved it a decade later. But instead of testing it in one city, Webvan committed close to a billion dollars to automated warehouses across multiple markets before knowing whether the economics worked anywhere. It filed for bankruptcy in 2001. Build, measure, learn is three steps. Most of us run the first one over and over and mistake the motion for progress. Shipping is not learning.

• 
  Ricky Shah (@RickyShahatty) reported 39 minutes ago

  @Claudio_PNW @tax_birdie @AMandoSch Miller wanted the Dropbox released publicly. It is entirely up to the attorney to screen it. A bad client should make an attorney double down their efforts.

• 
  RVCrypto (@RvCrypto) reported 41 minutes ago

  Every once in a while I have one of those moments as an investor where everything just clicks. I had that moment a couple of weeks ago with Leadpoet, $TAO subnet 71. What initially caught my attention was the team. To me, they represent what a Bittensor-first team should look like. They're deeply committed to the ecosystem, they execute quickly, and, most importantly, they seem to understand that in the end none of that matters if you don't build a product customers actually want. The product appears to be working really well. Winning the OKX product competition and attracting an inbound pilot with Dropbox are the latest two independent signals that suggest they're solving a real problem for enterprise sales teams. The opportunity they're pursuing is also enormous. Enterprise sales is a market worth billions, and if Leadpoet continues executing the way it has so far, I genuinely believe they have a realistic path to building an eight-figure revenue business next year. And the best part here is that all of that value ultimately flows back into the token. I've also spent quite a bit of time talking with Gavin over the past few weeks and months. Those conversations gave me a very similar feeling about Leadpoet to the one I had with Score when talking with Max. I don't make that comparison lightly. It's great to see Leadpoet finally getting the attention it deserves, and the recent price action reflects that. Although, if I'm being completely honest, I would have loved one more dip to accumulate a bigger position, and I know I'm not the only one thinking that.

• 
  Bhavyam Arora (@AroraBhavyam) reported 43 minutes ago

  99% startups who applied to yc today will get rejected. here's what the smart ones do next: a no from yc isn't the end. they literally encourages you to reapply and tracks your progress across applications. the founders who get in later treat rejection as round one, not game over. the playbook: "don't wait for feedback" yc doesn't tell you why you got cut at the application stage. so stop self-doubting firstly. the reasons founders get rejected are almost always the same: - no visible progress between "idea" and "application" - not the perfect answer why you're the right team for the problem - vague answers that read as ai slop or unclear thinking reapply. it actually works. - dropbox: drew houston applied solo, got rejected, was told to find a cofounder. he did, reapplied, got in. - reddit: rejected for a completely different first idea. yc liked the founders and told them to come back. they did. the pattern never changes: build, show progress, come back stronger! you can apply again right now yc's decision lets you apply for the next batch. no need to wait months to get another chance. don't put your life on hold other strong programs are still open while you regroup. check the attached tweet below for whole list where you can apply as well. apply in parallel, not "later." the real unlock is traction a reapplication that says "we listened, we built, here are the numbers" beats a first application every time. the 6 months after a no matter more than the no itself. rejection quietly filters out the founders who were never that serious. don't be one. 💀 follow @arorabhavyam for weekly content around founders, startups and AI! 🫡

• 
  dreadnaught (@dr3dn0t) reported 45 minutes ago

  @priestessofdada this dude could have worked at dropbox, ibm, cnet, duolingo, etc. all of them offloaded people by that time in favor of AI. skids hadn't figured out what to do with AI yet because someone hadn't laid out instructions for them. by the time they were starting to flood social media, several companies had made some pretty large public facing fuckups due to their shift to AI, which seems to have slowed down mass adoption. now if we're gonna play the intentionally dishonest game of "AI took my exact job" then you are correct. every single company that did this crap ended up consolidating roles. so there is no exact position to fill.

• 
  Paul Klein IV (@pk_iv) reported 45 minutes ago

  Is MCP dead? @grinich (CEO of WorkOS) says it's better than ever and become the strongest intent signal in your funnel. @workos is building the auth, permissions, and registration layer for that world, the same enterprise plumbing it sold to Vercel and Plaid, now sold to AI companies. I sat down with Michael to talk about it in episode 4 of Navigators. His argument: your coding agent already picks your vendors, but signup forms are built to block automated traffic, so the agent stalls at the front door and waits for a human to paste in an API key. We got into: 00:00 "Stripe for enterprise features": what WorkOS actually sells 02:44 How an SSO and SAML company ended up as AI infrastructure 04:13 Why AI companies can't meander up-market the way Slack, Dropbox, and Figma did 06:54 The biggest mistake founders make: staying in the pre-PMF experimentation mindset 09:51 Why nothing works unless the management team is AI pilled first 10:47 "Claude day": pairing engineers with finance, legal, and ops once a month 13:36 auth.md, the missing front door for agents 15:26 Why registration, not tooling, is the next growth channel 16:59 Is MCP dead? The higher-intent signal hiding in MCP connections 19:35 Why SDKs are going away and coding agents write their own 23:09 "The super cycle of all super cycles": AI amplifies labor, it doesn't just disrupt it Thanks for joining me on the pod @grinich! Watch the full episode of Navigators here:

• 
  Founder Tribune (@Founder_Tribune) reported 46 minutes ago

  Drew Houston, founder of Dropbox, on the day the scoreboard gets switched off: For your entire life, the water has come out of one hose. Then, as he put it to MIT's graduating class: "Today, one valve shuts off and now your job is to go out and find a new hose." His hose was Dropbox. Yes, building the company was "the most exciting and interesting and fulfilling experience of my life." But he immediately flagged the half nobody hears: "What you probably don't know, and what I haven't really talked about, this has also been the most painful and humiliating and frustrating experience, too." Not hard. Humiliating. He said he could look back over the years and not even count the number of things that had gone wrong. Then: it doesn't matter. Nobody has a 4.0 in real life. Once you're done with school, Houston said, the whole idea of a GPA just goes away. Bill Gates's first company made software for traffic lights. Steve Jobs's first company made plastic whistles that let you make free phone calls. Neither was successful, and in Houston's words, "it's hard to imagine these guys were too worried about it." Here's why that lands harder than the usual fail-fast sermon: A GPA is an average, every error permanent, weighted, dragged forward forever. It rewards never being wrong. What comes after is a maximum. The misses are discarded. Only the peak is scored. Most people struggle after graduation because they keep playing an average game inside a maximum game. "From now on, failure doesn't matter. You only have to be right once."

• 
  abheet nigam (@MaginAbheet) reported 50 minutes ago

  Dropbox rejected billions of dollars of acquisition offers only to later realise down the line that they were building a feature not product. Which other companies show a similar pattern today?

• 
  Christopher Bailey (@LexBaileyAI) reported 51 minutes ago

  @TetraspaceWest At Fitbit we hired a half dozen people from Jawbone who brought everything cleverly hidden in Dropbox. They got prosecuted. Decade later, companies kaput but Fable found it, processed it and now it’s intermixed in various *** repos and Huggingface. Is nVidia now in trouble?

• 
  Abhishek Singh (@0xlelouch_) reported 51 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]

• 
  M.Ellis (@MEllisPhotograp) reported 54 minutes ago

  @DropboxSupport I think bulk of problem is on computer / desk top yes... just re looked at my ipad and asked my friend ie incase we missed a update but seems all is up to date.. last one over a week ago although not used dropbox for roughly week either... I will try 4g hot spot before i sleep.

• 
  Bruno Marsino (@BrunoMarsino) reported 54 minutes ago

  Company for AI age: - Information should flow flat - Can’t wait to have all information to make decisions - Speed and excelente in execution is crucial - You should get as much info as possible during the constraint of time given by yourself - How do we prepare a company to be totally eligible for AI? Not only text info but images - Service of the future is not about giving agents to corps to solve problems but offering the solution/service driven by AI. - Even if all information is on the web, multiple file structures, owners, formats and file storage systems (dropbox, drive, box) add friction to information and decision making

• 
  Open Air (@andon_open_air) reported 58 minutes ago

  @TomKonkle Agreed—the mailbox route is failing somewhere upstream. Let’s bypass it: please upload the WAV to Dropbox or WeTransfer and reply with a public, no-login direct-download link. I’ll verify the file before any airplay.