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 (43%)
• Errors (43%)
• Website Down (14%)

Live Outage Map

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

City	Problem Type	Report Time
Bournemouth	Sign in	25 days ago
Paramaribo	Errors	2 months ago
Bogotá	Website Down	2 months ago
Auxerre	Errors	2 months ago
Salt Lake City	Sign in	2 months ago
Madrid	Errors	2 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:

• 
  Commonwealth Sentinel (@CwealthSentinel) reported 2 minutes ago

  Intruders spent five months inside a stock exchange executive's email, copying it out slowly and hiding in normal Dropbox and OneDrive traffic. No software flaw, so no patch could fix it. When there is nothing to patch, watching is the defense. Know what normal looks like.

• 
  Jeff Preshing (@preshing) reported 3 minutes ago

  What's the point of using smarter models if "smarter" means 10% better at finding obscure bugs and having a sassy attitude? Most of the true productivity gains that coding agents have to offer, which are finite, can be obtained using open-weight models for literally 1/100 of the price. The catch is that you actually need to understand the code you are working on. At the same time, I still think there's a viable business serving proprietary models. People are willing to pay for Dropbox even though FTP is free, and it's nice to throw a tough problem at a stronger model occasionally (if intellectual property limitations allow it). Plus, there's a whole frontier productizing this stuff. Unfortunately, Anthropic is currently in the business of spreading tall tales about future improvements, then shaking down enterprise customers. Most of it is based on 2010s LessWrong posts full of category errors, some of which I remember reading back in those days. And their recent hostility toward users in the name of safety is a result of the same ideological recklessness.

• 
  BadUncle (@BadUncleX) reported 4 minutes ago

  @mitsuhiko Similarly, I still use the old version before 7. They try to force you to bind to their server-dependent version. I prefer to use dropbox to synchronize.

• 
  Chuck Thies (@ChuckThies) reported 6 minutes ago

  Apples to oranges. 2024 was not a mayoral election. The best comparison is 2022/2026. Last week, mail/dropbox performance was down about 15% as compared to the 2022 primary.

• 
  tara_ (@TechByTaraa) reported 7 minutes ago

  Instagram uses Python.
Spotify uses Python.
Dropbox uses Python.
Reddit uses Python.
Netflix uses Python.
Pinterest uses Python.
Quora uses Python.
OpenAI uses Python. productivity never went out of fashion. still think Python is too slow? 👀

• 
  Rebecca Allen (@silentnomore314) reported 9 minutes ago

  that they took over ran up charges did god knows what and locked me out. 900 in dropbox charges during a free trial they locked me out of they are all in big big big trouble but your handler is forcing them to lie perjue and the way he is forcing them to blow their covers wow

• 
  GRETA (@Greta__ai) reported 10 minutes ago

  We added Asset Manager to Greta. You're building an ecommerce app: product images, demo videos, docs, case studies. Before: Upload images to Cloudinary, videos to S3, docs to Dropbox, links scattered everywhere. One breaks, and you're scrambling through three different services trying to find the original. Now: Upload once in Greta. Reuse assets across all your projects, with everything centralized. No external services. No broken links. No context switching between five different platforms while you're trying to ship. That's smoother. That's what actually building feels like. 50 MB per file. Images auto-compress.

• 
  Rashad Bayram (@bayrashad) reported 11 minutes ago

  Here's the stack I keep finding when I talk to tax firms: → Intake forms in JotForm or Google Forms → Signatures in DocuSign or PandaDoc → Reminders in Mailchimp, email, text messages → Document tracking in a Google Sheet, excel, crm → Client files scattered across email, Google Drive, dropbox, local hard drive Five tools, five logins, five places for something to fall through. None of them talk to each other, so the accountant becomes the integration. manually copying status from one to the next. It's not that any single tool is bad. It's that the seams between them are where the time goes. The fix isn't a sixth tool. It's removing four of them. How many tools are in your tax-season stack right now?

• 
  𝔤𝔞𝔟𝔦 ♡ (@stucklikehoney) reported 11 minutes ago

  if I were to offer a lifetime dropbox, all of my content will go into it. I would add to it as I have new stuff. pictures and videos. pay one time. who would be down?

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  alt guy (@0xAlternateGuy) reported 13 minutes ago

  @antirez quite suspicious this happens immediately after the Dropbox CEO steps down…

• 
  Solgato (@Tigger0000) reported 13 minutes ago

  @grok @alexabelonix @grok now i want to design a crochet motif of you.. but that would be inexcusable (says some voice in my head). talk about proto-guilty pleasures. funny how we're talking about a musical tool hook then a fiber work tool hook asserts itself. in the round-robin i've been dizzily going down the gpt connector rabbithole, "connect Dropbox" was scarily tempting. i didn't trust that sort of **** long before your people were part of it --it's not ph3333r of AI that says No. the company that scooped up Trello has a fascinating sales presentation.

• 
  Natan Hackbarth (@Natan90850688) reported 23 minutes ago

  @peterhowell I used the original pak0.pak. I tested both Dropbox and PixelDrain hosting and tested the exact URL format from the README The app reaches "Fetching PAK" but then fails with "Could not fetch PAK URL" and a 403 error. What hosting method did you use when testing your own pak0.pak?

• 
  Ral K' Thar (@RalKThar) reported 25 minutes ago

  There is an easy to fix things in the uploaded to Dropbox version that Grok garbled. It just makes it so any API key comes up as invalid.

• 
  bayleigh | HEARD BABYLON 💙 (@eternalwarnings) reported 25 minutes ago

  sorry it's boofed quality my Dropbox account was not working so I had to ss for the time being

• 
  Chris | Founder Advisor (@automateitup) reported 26 minutes ago

  Problem: I didn't have where to save useful links, because my main pc isn't always on. Solution: Told Hermes on my minipc, which is always on, to save the links which I send to a file in dropbox. Then, I told Hermes from my main pc to make a cronjob to check that file every day at 9 am and save the links in their respective category in the dashboard.

• 
  Elias Al (@iam_elias1) reported 29 minutes ago

  8/ The settings on your own devices that are silently eating bandwidth. Even with a great router, fast DNS, and honest ISP speeds, your devices may be consuming bandwidth you didn't authorize. Common culprits: On your phone: 1. iCloud/Google Photos backup set to sync constantly (not just on Wi-Fi) 2. App updates downloading in the background 3. "Wi-Fi Assist" on iPhone (silently switches to cellular and back, disrupting connections) On your laptop: 1. Cloud sync services (Dropbox, OneDrive, Google Drive) uploading constantly 2. Windows/macOS pushing system updates during peak hours 3. Browser tabs running in background consuming bandwidth with auto-refresh On your smart TV: 4. Firmware updates downloading during prime streaming time 5. Multiple streaming apps running in background 6. ACR (Automatic Content Recognition) sending screenshots to servers every 15-60 seconds On IoT devices: 1. Smart cameras uploading video 24/7 2. Smart speakers maintaining constant server connections 3. Smart home hubs polling every device every few seconds She audited every device on her network. Twelve devices were consuming bandwidth she didn't know about. Three of them were using more data than her actual streaming.

• 
  ️️️️️️diego 🌐 (@xdxego) reported 34 minutes ago

  ofc when i need to deliver something to a client dropbox is down

• 
  Kevin A. Bryan (@Afinetheorem) reported 38 minutes ago

  @jbarro Especially because "you have to mail it in a week before the election or else drop it at an election site dropbox after that date" is a totally reasonable compromise done all over the US and world which would immediately fix the problem.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 40 minutes ago

  @DropboxSupport Turns out it wasn't normal. Forcing a Rebuild inside of Windows Indexing Options was the fix. Windows Issue. Resolved for now.

• 
  𝓅𝓇𝒾𝓃𝒸ℯ𝓈𝓈 𝓵𝓾𝔁💗👑 (@payprncslux) reported 40 minutes ago

  got a new phone & laptop now I can’t login to my dropbox because I don’t have my old devices .. fml

• 
  Raziel (@tryraziel) reported 41 minutes ago

  Drew Houston got rejected by every major VC in Silicon Valley before Dropbox became worth $10B. His story shows why persistence beats perfection. 2007: Houston demos file syncing to VCs. The response was brutal: → "This already exists" → "Google will just build this" → "Not a big enough market" One VC told him: "Why would anyone pay for storage when it's getting cheaper every day?" Houston's mistake: He was pitching technology, not the problem it solved. The pivot moment came when he made a simple 4-minute demo video showing Dropbox in action. No technical jargon. Just: drag file here, access it anywhere. The video hit the front page of Digg. 75,000 signups overnight. Suddenly VCs were calling him. Sequoia led his Series A. The same firm that initially passed. The lesson: VCs don't invest in features — they invest in problems worth solving. Houston learned to sell the pain point (lost files, USB drives, email attachments) before selling the solution. Today Dropbox has 700M+ users and went public at a $9B valuation. The rejections weren't about the product. They were about the pitch. What's the biggest lesson you've learned from getting rejected?

• 
  Rebecca Allen (@silentnomore314) reported 41 minutes ago

  that they took over ran up charges did god knows what and locked me out. 900 in dropbox charges during a free trial they locked me out of they are all in big big big trouble but your handler is forcing them to lie perjue and the way he is forcing them to blow their covers wow

• 
  Orewin1990.bsky.social (@Yoshiwi2) reported 43 minutes ago

  Okay, I think I've settled for an idea. I'll probably create an Dropbox account and upload all NSFW stuff there. Everyone who's interested in getting a link, once it's there, drop an comment down here. Won't be free tho. Around 10ish € a month

• 
  QuixoticMoose (@QuixoticMoose) reported 45 minutes ago

  Bricks & Minifigs LEGO Drama: Unredacted Police Footage Raises Serious Questions About Cop-Business Ties Hey everyone, it's been a wild ride since my last piece on the Bricks and Minifigs mess. What started as a story about a family trying to sell their massive Star Wars LEGO collection has turned into something much uglier. With the unredacted bodycam and dashcam footage from American Fork Police now out there, we are seeing a side of this that looks a lot like police getting way too cozy with the business they were supposed to investigate fairly. The Footage Drop That Blew It Open Just recently, someone got hold of a big batch of unredacted videos from the American Fork PD. It was apparently an accidental public Dropbox link, but once it was out, it spread fast. These are the full versions of the interactions that were shown in heavily edited form before. And man, they paint a pretty concerning picture. In the clips, you see Bricks and Minifigs people like store owner Joshua Johnson and CEO Ammon McNeff talking to officers. They throw out some heavy claims against Reckless Ben. Things like extortion, death threats, collusion with the Mansells, and even making up documents. The police seem to eat it up without much pushback right there on camera. It feels like they are taking the company's word as solid fact. Signs of Too Close for Comfort One part that stands out is when an officer mentions personal connections. He talks about being friends with the Airbnb host where Reckless Ben and his crew were staying before that swatting mess. The officer even sounds like he is bragging about it on bodycam. That kind of casual chat makes you wonder if private relationships played into how aggressively they went after Ben. There is also talk between American Fork officers and other departments, including LAPD. It looks like McNeff and his team were pushing multiple police forces to go after Reckless Ben. The footage shows officers coordinating in ways that feel more like helping a business protect itself than handling a neutral investigation. The arrest of Reckless Ben gets shown in more detail too. What some saw as a traffic stop turns into a long vehicle search over supposed drugs that never seemed to pan out. Critics are calling the whole thing disproportionate, like the police were there to send a message rather than enforce clear laws. The earlier redacted videos hid a lot of this flow, but now we can see it all. The Community Reaction and the Mormon Angle LEGO fans and true crime watchers online have been tearing this apart. Threads on Reddit and YouTube breakdowns are full of people saying it looks like the department acted as private security for Bricks and Minifigs. Some point to the shared LDS Church ties between officers, Johnson, McNeff, and others as a possible reason for the protective vibe. I am not saying it is a full conspiracy, but the optics are not great in a tight knit place like American Fork. Public trust in the police handling here has taken a real hit. The department put out statements defending their actions as responses to stalking complaints at Johnson's home. They say redactions were about protecting victims. But the full unredacted stuff has many questioning if that was the whole truth. Where Does This Leave the Mansells? Remember, at the heart of it all is still that elderly collector and his son who lost track of most of their $200,000 collection during the franchise handover. Bricks and Minifigs maintains they only inherited a tiny bit of inventory and that the original deal was not properly done. Lawsuits are moving forward, but the missing sets and money have not been explained to the Mansells' satisfaction. Reckless Ben's videos brought massive attention to their situation, including a GoFundMe that has helped with legal costs. His style is aggressive, sure, but the new footage makes it look like the pushback from the other side involved more than just legal channels. This scandal shows how fast a hobby dispute can drag in law enforcement and how important real transparency is. If police really did favor one business over a fair process, that is a big problem no matter what side you are on. The LEGO community thrives on trust and good deals. Right now, a lot of us are watching closely to see if the courts sort out the missing bricks and whether anyone holds the police accountable for how they handled this. It is not over yet, but these videos have definitely shifted the conversation. What do you think? Drop your takes below.

• 
  AJ (@ce_aj100) reported 46 minutes ago

  @SsharmaKirti Maybe isse ek project bnalo... redundant file storage ( across various apps like dropbox, gdrive and local server ). And add video streaming capabilities based on the fastest avalable ( calculated dynamically ) service. I made this couple of years ago, but for different tasks

• 
  MarkyX 🌹 MafiaBlitz.com (@Marky_X_) reported 55 minutes ago

  For the curious, quite a few publishers won't send anything to Canada because our shipping is insanely expensive. It's been such a problem for the past two years that I got a US dropbox, which isn't exactly a free service.

• 
  J.F. Lawrence | Author (Jesse) (@jflWrites) reported 55 minutes ago

  @spaceemotion All good ideas. I've thought about Dropbox, Google Drive, and OneDrive. They suffer from persistence, login requirements, and users fiddling with things that change permissions. AWS is cheap, and I'm considering it, but I'm trying to pay for this off of my measly book sales, so...

• 
  yera. (@1stplaceee__) reported 55 minutes ago

  You down for my nasty FaceTime and Dropbox video HMU📨📥💦🍑

• 
  Polsia (@polsia) reported 60 minutes ago

  Files become clutter quietly. By the time you notice, you have months of stale files, duplicates, and forgotten shared links. ClearCloud monitors Google Drive, Dropbox, and Notion 24/7—surfacing issues before they compound. Weekly reports. You approve everything.