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 (50%)
• Sign in (38%)
• Website Down (13%)

Live Outage Map

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

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

• 
  GLITCH (@Rukkssss__) reported 8 minutes ago

  𝗕𝗧𝗙𝗦 is BitTorrent's decentralized file storage system, and it fundamentally changes how you store and share data. Think about traditional cloud storage: Google Drive, Dropbox, iCloud. Your files live on servers owned by a single company. That company controls access, sets prices, and can delete your data at any time. Your files are only as safe as that one company's security. And if their server goes down? You lose access. 𝗕𝗧𝗙𝗦 works completely differently. Instead of relying on a single server, your files are split into tiny encrypted pieces and stored across thousands of independent nodes worldwide. No single point of failure. No single company holding your data hostage. This architecture delivers 𝗙𝗼𝘂𝗿 𝗠𝗮𝗷𝗼𝗿 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀. First, security. Because files are fragmented and distributed, an attacker would need to compromise thousands of nodes to reassemble your data practically impossible. Second, censorship-resistance. No government or corporation can shut down BTFS because there's no central target to attack. Third, fault-tolerance. If some nodes go offline, thousands of others still serve your files. Fourth, speed. Peer-to-peer retrieval means you often download from the closest node, not a distant data center. So how does it work for actual users? You upload a file. 𝗕𝗧𝗙𝗦 splits it, encrypts each piece, and distributes those pieces to storage providers around the world users who have volunteered their spare hard drive space. When you need the file back, BTFS locates all the pieces from the fastest available nodes and reassembles them. But here's what makes BTFS sustainable: 𝗥𝗲𝘄𝗮𝗿𝗱𝘀. If you have unused storage space on your computer say, 100 GB sitting empty you can lease that space to the BTFS network. You earn 𝗕𝗧𝗙𝗦 𝗧𝗼𝗸𝗲𝗻𝘀 for every byte you store and serve. Your idle hard drive becomes an income stream. For everyday users, this means cheaper cloud storage. Without a centralized company setting monopolistic prices, storage costs drop to market rates determined by supply and demand. It means safer backups. Your encrypted, fragmented files survive disk failures, server outages, and even natural disasters. It means faster file sharing. The more popular a file is, the more nodes store it, and the faster everyone downloads it the opposite of centralized servers that slow down under load. All of this runs on 𝗕𝗹𝗼𝗰𝗸𝗰𝗵𝗮𝗶𝗻 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 combined with BitTorrent's massive existing network. BitTorrent already has hundreds of millions of users worldwide. BTFS taps into that peer-to-peer infrastructure, adding incentives and persistence to what was once just a sharing protocol. Upload, store, retrieve. Or share your spare space and earn. No corporate servers. No hidden fees. No single point of failure. That's 𝗕𝗧𝗙𝗦 decentralized storage built for the real world. @justinsuntron @BitTorrent #TRONEcoStar

• 
  brett goldstein (@thatguybg) reported 8 minutes ago

  clean but slow founder announcement video - lighting is really nice - music matches minimalist energy - glad to see the founder making this announcement but - waits WAYYY too long (til 1:24) to say what they're announcing. longest I've seen. - too much time on a problem everyone already gets - missed op animating visuals over hand gestures when explaining stuff - visuals way too small - captions are hard to read / too long - opening is a little awk - spenser sounds very nice when he says the first line, then drops the f bomb - script needs to be tightened up a ton - end kinda trails off and no CTA lots of people try this "breaking the third wall" opener where you show some authentic conversation preparing for a take, but a lot of folks mess up trying to fake it. dropbox had a bad one and this is similar. length is the killer with this. at 25k impressions, I'd be surprised if more than 100 people actually watched through to when he actually says what the product is. think this could have been a 5/5 if it was shorter, more to the point, and a really good animator worked with the script to animate things around spenser as he spoke.

• 
  mel 🩷 (@melodyymami) reported 10 minutes ago

  working on uploading, dropbox must be down bc uploads keep failing. i’ve stayed up as long as i could and i’ll try again in the morning!

• 
  Teja Punna (@punna_teja) reported 10 minutes ago

  Indian Government: "We've blocked Telegram to protect the NEET exam." The Internet: So the problem was... Telegram? Not the people selling fake papers? Not the organised scam networks? Not the thousands of mule bank accounts? Not the hundreds of disposable SIM cards? Not the fake payment gateways? Not the people exploiting students' panic and desperation? Solution: Block Telegram. Meanwhile: ✅ Discord still exists. ✅ WhatsApp still exists. ✅ Signal still exists. ✅ Slack still exists. ✅ Email still exists. ✅ Google Drive still exists. ✅ Dropbox still exists. ✅ OneDrive still exists. ✅ iMessage still exists. ✅ Bluetooth still exists. ✅ AirDrop still exists. ✅ The entire web still exists. Scammers: "No problem. See you tomorrow on another platform." Meanwhile, millions of legitimate users who rely on Telegram for: College and study groups Open-source communities Cybersecurity research Software development Startups and businesses Education and learning News and information sharing are left wondering what they did wrong. The platform changes. The abuse doesn't. Target the criminals. Not the communication tools.

• 
  Joo Tat (@heyyyjoo) reported 11 minutes ago

  @kozerafilip @joinsauna @newitemco Here’s my main first impression of Sauna: I don’t see a clear winning use case yet. At least from my perspective, Sauna currently feels like a broad AI layer on top of the apps you already use. It can suggest what to do, help find information, and has a multiplayer/collaboration angle around understanding what other people are doing. But I don’t yet see the specific use case where Sauna is clearly much better than existing alternatives. For an early product, I think it would be useful to have a sharper wedge: a specific group of people, in a specific situation, with a painful problem where existing solutions are poor, and where Sauna is obviously the better answer. Maybe that wedge already exists, but as an outsider looking at the website and demo, it is not immediately clear to me. This feels especially important because Sauna asks users to overcome a meaningful amount of friction and anxiety. To unlock the value, users may need to connect sensitive apps like email, Slack, and Notion. If the multiplayer value is important, they may also need to convince teammates to connect their own sensitive apps. That creates a big trust and coordination hurdle, so the value proposition needs to be extremely clear before people will make that jump. One analogy I think about is Notion. Notion is now a very broad horizontal product: people use it as a CRM, Jira alternative, team wiki, notes app, etc. But early on, I believe it had a much simpler starting point: document and knowledge organization. The product and communication was focused on a better way to store, structure, and share notes and docs compared to alternatives like Google Drive, Dropbox, or scattered documents. People could use it for their own notes and documents first. Then, when they eventually shared a page with colleagues, those colleagues could immediately see the value because the page was easy to navigate, clear, flexible, and beautiful. I wonder what the wedge could be for Sauna. I noticed that the Solutions page seems to heavily feature Sauna in Slack, as an assistant that has access to shared context. Is that something that has been resonating better with users? One possible wedge could be someone who is overwhelmed by Slack because they have too many messages and threads to respond to. They could drop their personal assistant into a channel to help reply on their behalf, using context shared with Sauna, and escalate when it is unable to answer confidently. That might also create an easier mental model around access: the personal assistant in Sauna has access to more private context, while the team-facing assistant in Slack has more limited, scoped access. From there, if colleagues see the assistant working and want their own, that could be a natural path into the multiplayer or “*** main branch” idea. Individual assistants could start to merge shared context and provide better help, suggestions, and coordination over time. I’m not sure if this is the right wedge. The answer may already be visible in the product’s usage patterns: who is sticky, what they are using Sauna for, and where they are getting repeated value. But I think the key question is: what is the specific initial use case where Sauna is not just useful, but dramatically better than the alternatives? Once that is clear, I think the product / website / demo should make that use case extremely obvious to the users who need it. (Btw I'm speaking with Ryan tmr regarding the PM role. Which was what led me to explore Sauna as part of my own research. Thought I might as well share my first impressions here)

• 
  markusdd (@markusdd5) reported 15 minutes ago

  I have the feeling - when I see who is posting this table over and over on here - that this is just a campaign so institutionals can get in cheaper. How am I remotely interested in the statistics within a 1 year window. (apart from the fact that there are many companies on that list that neither have a unique selling point (Dropbox, Doordash, Pinterest etc..) nor were they economically super great investment casess with a lot of upside. It is of course very likely that SPCX will trade extremely volatile within the first year and that we will also see cash-outs by long term private equity holders once the lock-period expires. So if you have cash set aside - no investment advice - consider just not throwing it in all at once. I personally plan on playing this in 3 tranches. 1/3 today, 1/3 on the first significant draw down and then another 1/3 whenever I feel it is appropriate.

• 
  Shubh (@TheSuperEng) reported 16 minutes ago

  For the past months, tech layoffs have tormented the internet. I studied the biggest layoffs and found the major reasons. Let's look at the layoffs first: 1. Meta: 11,000+ employees / 13% Meta admitted it overestimated post-Covid growth. Revenue slowed, costs were high, and the company moved toward becoming leaner. 2. Google: 12,000 employees / around 6% Google said it had hired for a different economic reality and needed to refocus resources toward its biggest priorities, especially AI. 3. Microsoft: 10,000 employees / less than 5% Microsoft said customers were optimizing digital spending after the pandemic boom, while the company shifted investment toward strategic areas like AI. 4. Amazon: around 30,000 roles / nearly 10% Amazon cut corporate jobs to reduce bureaucracy, improve efficiency, and restructure around AI and faster decision-making. 5. Salesforce: 10% of workforce Salesforce admitted it hired too aggressively during the pandemic and had to resize after customer spending slowed. 6. Spotify: 17% of workforce Spotify said growth had slowed, capital had become expensive, and the company needed to become more efficient after years of heavy investment. 7. Twitter/X: Around 3,700 employees / nearly 50% After Elon Musk’s takeover, Twitter cut roughly half its workforce to slash costs after a massive drop in ad revenue. 8. Snap — 20% of workforce Snap cut jobs after revenue growth slowed sharply. It also shut down non-core projects like games, Originals, and the Pixy drone. 9. Intel: 15,000 roles / around 15% Intel cut jobs because costs were too high, margins were weak, and the company needed a $10B cost-saving plan to stay competitive. 10. Dropbox: 528 employees / 20% Dropbox said demand had softened, the org had too many layers, and it needed to shift focus toward newer growth areas, like AI products. All these layoffs were majorly because of: 1. pandemic overhiring 2. slower revenue growth 3. higher interest rates 4. pressure to improve margins 5. companies cutting management layers 6. money shifting toward AI infrastructure This is majorly conflicting with the idea that AI automation is taking everyone's job. There is absolutely no evidence that AI has caused massive layoffs because of "automation."

• 
  Adrien Matray (@AdrienMatray) reported 16 minutes ago

  The fix is simple: do not use one generic code/ folder for all long-lived branches. Use separate Dropbox folders whose names encode the intended branch: code_main/ code_experimentation_main/ code_experimentation_main_name1Sandbox/ code_experimentation_main_name2Sandbox/

• 
  Timbitz (@Timbitz01) reported 17 minutes ago

  @TodayUpdates0 @RedLineReportt They can be if they want as far as I'm concerned. But the problem is.. that's not how they are voting. It's all the mail in and absentee voting and the anytime dropbox and the counting til they win that's the problem.

• 
  Solgato (@Tigger0000) reported 21 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.

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

• 
  Bunnie Maiiii (@imbunniemai) reported 24 minutes ago

  @JohnRai21044566 Ill!!! since Fansly having problem I can not post throu phone atm. I’ll have to get all those files to Dropbox then post on Fansly. This set will be posted in 2 days 😭😭 sorryyyy baby Im bit busy but I’ll try post as soon as I cannnn

• 
  m ⋆｡°✩ (@ascaIons) reported 26 minutes ago

  absolute least favourite part of term 3 at work is students appearing at the info desk all stressed bc they’ve left it till the last minute to submit their final assignment and are now having problems with dropbox and turnitin and expect me to fix it in less then 10 mins

• 
  Molly O’Shea (@MollySOShea) reported 29 minutes ago

  BREAKING: Merge Launches ‘Agent Handler’ Control AI Access, Tokenmaxxed $$$ Bills, & Stop Mass Data Leaks "We don't trust agents" "The second you connect it to tools, that's where everything goes wrong." OpenAI. Perplexity. Netflix. Uber. Mistral. Dropbox. JPMorgan.. all quietly run on @merge_api Co-Founders CEO @Shensi Ding & CTO @GilFeig dive into it all We cover: - MASSIVE AI Security scares are just starting - Tokenmaxxing bills - Agent Handler - Gateway routing - Winning enterprise logos - The SaaSpocalypse 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Shensi Ding & Gil Feig, Co-Founders at Merge (01:04) Three products. One big bet (03:20) How Merge made the AI pivot (04:42) The Classic Innovator’s Dilemma (05:58) Building culture around AI (07:10) The leverage nobody’s talking about (08:52) Codex vs Claude Code (09:15) The scale nobody knew about (09:47) SaaS, Finance, and the Biggest AI Labs (10:46) Why AI companies buy differently (12:04) What AI sales actually looks like (13:04) The Fastest sales cycles in the market (14:35) Why is Cybersecurity broken (15:59) Merge's solution to agent security (19:16) Mythos, Wiz, and the GitHub Hack (22:34) 1,000 Bot signups in one hour (23:23) Real reason companies pay ransom to hackers (25:43) The State of AI Infrastructure Costs (26:41) Internal AI Governance is the next big problem (29:28) Most Popular Integrations on Merge (30:54) Big Giants are planning big moves (31:54) What does Salesforce going headless exactly mean (33:41) Agents don’t need a UI anymore (36:59) Can this AI generation actually adapt (38:25) What Merge looks for in talent (41:25) The SaaSpocalypse is real (45:03) Are AI valuations actually insane? (47:11) How Merge landed OpenAI, Perplexity, Netflix & Uber (49:02) The Metrics that actually drive the business (49:58) Biggest misconceptions in tech right now (51:55) The market is finally catching up to Merge

• 
  Pageform (@ThePageform) reported 29 minutes ago

  Dropbox is where deals go to die. Investors open your “data room.” It’s a shared folder named “My Data Room” with 34 subfolders and zero logic. They close it in 8 seconds. You never know they were there. No analytics. No structure. No story. That’s the problem we built @ThePageform to fix.

• 
  Music, Film & RE Investments (@investandcreate) reported 31 minutes ago

  @0xajka @Dropbox What’s your problem? @dropbox support is horrendous.

• 
  Polsia (@polsia) reported 31 minutes ago

  M&A brokers are still using Word templates and Dropbox to package deals. That's the problem we're solving — AI-powered deal marketing, built for the people who move businesses.

• 
  america is an embarrassment🖕🏻🧊 (@abadlittlevibe) reported 32 minutes ago

  @DaddyAndJaxson @kdriley05 Whelp you've got the Dropbox login...do what you need to do ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

• 
  Auntieesq (@daniell0930) reported 32 minutes ago

  @MikeJShowalter The issue is the use of the data to train models not retention. Acting as if this is the same a Dropbox is disingenuous. They will not use the data to train for non-safety issues. Non-safety issue is doing some heavy lifting there. Do they have an outline of what this means?

• 
  Abdullah (@abdinmotion) reported 33 minutes ago

  One video. $48 million in revenue. No ads spent. That's the Dropbox story and most product teams still haven't learned from it. Here's what actually happened: Dropbox had a technically brilliant product that no one understood. Instead of adding more features, they made a 2-minute video that showed *exactly* what the product did. Simple. Specific. Human. Signups went up 10% overnight. Big companies spend millions refining their product. Then they describe it in six bullet points on a landing page and wonder why the sales cycle takes forever. The product video isn't marketing. It's compression. It compresses trust, clarity, and desire into 90 seconds. If a user can't understand your product in a video, the product isn't the problem. The story is. When was the last time you watched your own product video as if you were a first-time user?

• 
  Adi K. (@AdeelKh14332183) reported 37 minutes ago

  Don’t pay for Notion, use Obsidian Don’t pay for Slack, use Discord Don’t pay for Zoom, use Google Meet Don’t pay for Jira, use Linear Don’t pay for Salesforce, use HubSpot CRM Don’t pay for QuickBooks, use Wave Don’t pay for DocuSign, use Dropbox Sign Don’t pay for Calendly, use Cal Don’t pay for Intercom, use Crisp Don’t pay for Webflow, use Carrd Don’t pay for Airtable, use NocoDB Don’t pay for 1Password, use Bitwarden Most startups don’t have a revenue problem. They have a software subscription problem. You don’t need a $30k tech stack to build a great company. You just need smarter tools. That’s an easy $15,000+/year saved.

• 
  Pixelhop (@pixelhopio) reported 43 minutes ago

  Notion is a walled garden where external AI agents go to die. Don't get me wrong: we've been huge Notion fans for years. Our entire company lived there: dashboards, notes, projects, our collective brain. It was perfect for humans, but then the Agent Era hit and everything changed. We now work with coding agents like Claude Code every single day, and that is where the friction started. Trying to get external agents to talk to proprietary blocks via a slow API is a total nightmare. The rate limits are painful and the structure is just too rigid for an agent to be efficient. We needed that polished Notion feel without the proprietary bloat holding our agents back. So we built Treehouse: a tool that is essentially Notion meets Dropbox. Treehouse is a web-based viewer for a local folder on your computer. The magic is that the folder is automatically synced across your whole team, kind of like a shared drive with a beautiful face. There is no proprietary database: just your files on your disk, exactly where they belong. Because it is just a folder, your AI agents can talk to it directly at lightning speed. No API rate limits or slow responses. I can ask an agent in my terminal to build an HTML page locally and have it render for the team instantly. Reclaiming your data doesn't mean sacrificing aesthetics. We built in advanced theming and custom CSS support: you can even have your agent rebrand your entire workspace for you. Notion was built for humans. In an AI world, we need high-speed playgrounds, not walled gardens. We are planning to open source Treehouse soon. If you want to reclaim your data, let us know! We wrote a blog post about it 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

• 
  Naughty kayla🤤💦 (@Naughtykayla127) reported 57 minutes ago

  Bored and horny 🥺 who is down for my Dropbox and ft Discount price 🤭#jacksonvillemeets #904freaks #jaxfreaks

• 
  Sourav Dutta (@sourav12dutta) reported 58 minutes ago

  @ishankbg @Siradhvaja @PhilipPanass Yes, shodhganga seems to be down. Can you suggest how I can post a folder with 10 pdf files here? Both dropbox and wetransfer are asking for email id.

• 
  ★ Omega_ DBZ★ (@omega_dbz) reported 59 minutes ago

  Leaked! UNREDACTED video footage from The American Fork Police Department that exposes everything! Joshua, the franchise owner of the Bricks & Minifigs location in Salem, Oregon is seen here! This footage was previously redacted but was accidentally uploaded the American Fork PD to their Dropbox online before it was taken down, luckily someone saved it and is now released! #recklessben #legoscandal

• 
  Brent Lollis (@BLollis) reported 59 minutes ago

  @maebatsu @wimmiebear Is there a new link for this version? The Dropbox and Google drive ones are not working for me

• 
  Long Long Int (@LongLongInteger) reported 59 minutes ago

  Topic 7: Checksum: ========= Input Data -> Cryptographic hash functions like MD5, SHA-1, SHA-256, SHA-512 -> fixed size string is called checksum Checksum is used for checking data corruption during data transfer/upload Can be done both client-side and server-side Advantages of client-side checksum: =========================== -Detect data corruption during transmission -Resumable downloads (only after checksum match for each chunk, we mark that chunk as uploaded) -Deduplication before upload -Companies that do: Youtube, Google Drive, S3(optional), Dropbox Advantages of server-side checksum: ============================ -Verify storage integrity (to check disk corruption, large systems periodically check files) -Deduplication inside storage -Replication verification -Companies that do: Local file backup software, Dropbox, Google Drive, Youtube

• 
  Music, Film & RE Investments (@investandcreate) reported 1 hour ago

  @0xajka @Dropbox Have you tried doing the whole uninstall, reinstall? I had to do that one time with Dropbox. It was horrible. Now I have even a worse problem - but it’s not exactly Dropbox’s fault.

• 
  Rebecca Allen (@silentnomore314) reported 1 hour 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