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	6 days ago
Guayaquil	Website Down	6 days ago
Flumet	Errors	16 days ago
Irapuato	Errors	18 days ago
Bournemouth	Sign in	2 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:

• 
  🔩⚾️ (@john_dough) reported 5 minutes ago

  @irisivanyi @nickcamsmith If someone has a very fancy and complex portfolio site, they are probably not working very much. My portfolio is 10+ years out of date because I never have the time to update it. I just send a Dropbox folder of images of new work to people these days. ¯\_(ツ)_/¯

• 
  Sridhar Katakam (@srikat) reported 5 minutes ago

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

• 
  Ishita Sethi (@Ishita__Sethi) reported 8 minutes ago

  @LoganOpSec that dropbox bit is the part that sticks. recovery without revoking access is just half a fix.

• 
  Ryan Babbs (@buckybabbs) reported 12 minutes ago

  Hello @Dropbox, Just this week I have decided to switch cloud service from Google Drive to you and less than 1 week I'm having an issue. I run a wedding film business and am trying to move the same 200GB file to two separate editors for two separate kind of films and one of them is encountering a "link temporarily disabled" message. I tried to research online and made a new folder and copied over the original folders contents and cannot share that either as it says I've exceeded bandwidth limits. This is maddening as I thought I'd picked the good plan (3TB) and was all set. Please advise asap as I need these files in my editors hands stat.

• 
  Tim Geisendoerfer (@djgeisi) reported 12 minutes ago

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

• 
  Evan Logan (@evanlogan) reported 13 minutes ago

  @Shwinnabego Same. I use chat for common tasks, merging data, generating images, planning projects. But I only this week figured out how to connect to Dropbox, pull audio files, edit them, and upload to a server. And once I did I was hit with a credit limit. Can’t afford it on a daily basis.

• 
  Bruno Marsino (@BrunoMarsino) reported 19 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

• 
  Llama (@thellama451) reported 21 minutes ago

  I tracked down these messages in @MaxMillerOH’s Dropbox files. They show the parents getting along with no major conflicts beforehand. If Miller said he was going to kill his ex-wife in front of child (likely), it shows a talent for masking rage and hostility.

• 
  Ricky Shah (@RickyShahatty) reported 22 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.

• 
  Marcus (@marcuslayerx) reported 24 minutes ago

  way too many teams in crypto still think they're buying user acquisition when they’re really just paying the same audience to look at another project for a week i’ve spent the last few days looking at products that could actually break out of the crypto bubble and the people they need aren’t sitting on ct waiting to find them - morse is built around freelancers getting paid across borders - blackbird gets people while they’re literally sitting in the restaurant - DIMO’s real path runs through dealerships, insurers and people building with car data - Hivemapper only becomes a real business when companies pay for fresh map data, not because more drivers collect it square put the card reader in the merchant’s hand, dropbox gave people more storage for bringing someone else in, opentable became part of how restaurants took bookings, etc they showed up while the person was already trying to do the thing a lot of teams still open a spreadsheet of kols/agencies to pay before they’ve even worked out where the user is when the problem even happens

• 
  VC Intern (@the_vc_intern) reported 28 minutes ago

  Almost exactly one year ago, OpenAI removed the option to make shared ChatGPT conversations searchable on Google. Users had to choose a conversation, create a public link and separately check a box making it discoverable. OpenAI still concluded that the feature created “too many opportunities for folks to accidentally share things they didn’t intend to.” Claude is now facing the same product-design problem with Artifacts. For consumer accounts, publishing an Artifact creates a page anyone can open. Anthropic warns that it may appear in search results. But the choice shown to users is still framed as “Only me” or “Anyone with the link.” Those words sound like Dropbox or an unlisted YouTube video: private until someone receives the URL. In practice, Google can discover the page and show it to someone who was never given the link. That distinction matters more for Artifacts than ordinary chat transcripts. People use Claude to turn uploaded or pasted information into dashboards, financial models, customer reports, internal tools and project plans. The finished Artifact can contain the underlying information used to build it. Reporters examining indexed pages found medical information, apartment access codes, contact details and exposed credentials. These were not private pages broken into by Google. Their owners published them. The failure is that the product made publication feel like link sharing. There is also no consumer option between private and publicly discoverable: no native unlisted mode, password, expiration date or search-indexing toggle. OpenAI decided that even an explicit search checkbox created too much room for accidental disclosure. Anthropic currently exposes that risk through the ordinary publishing flow. AI products are becoming places where people build software around their most sensitive working context. Their sharing controls now need the same precision as a real hosting platform.

• 
  og bec (@becca_may33) reported 28 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

• 
  Rei (@ReiHerrera) reported 30 minutes ago

  @owldreig @porterrobinson @madeon The problem with them both is they love gatekeeping the rare song behind a bad quality sounding medium so you cannot use it for clean for dj sets. For example Celine,worlds live,shepherdess,etc. at least we had hollowheart on wav and shepherdess wav was on porter’s Dropbox leak🫩

• 
  Synapse Brief (@Synapse_Brief) reported 30 minutes ago

  @gdb Scraping 7 consecutive years of tax forms and equity statements across Dropbox and Shareworks requires orchestrating dozens of DOM interactions without dropping session state. Standard visual tool-calling loops degrade quickly once context windows swell from repeated full-page DOM trees and screenshot tokens across nested subfolders. The underlying issue with multi-year document extraction is not simple folder traversal, but error recovery when dynamic OAuth tokens expire mid-sweep. Navigating nested web UI trees for 2016 through 2025 records usually hits rate limits or modal overlays that cause visual grounding agents to hallucinate click coordinates. Production reliability on complex immigration workflows will require hybrid execution models that compile raw browser actions into structured API calls or deterministic scripts after initial path discovery. Until agents decouple stateful file fetching from reactive visual vision loops, edge-case recovery will remain the bottleneck for zero-touch filings.

• 
  DFIR Radar (@DFIR_Radar) reported 32 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 34 minutes ago

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints to pin down: 1) Clients can be offline for days, then reconnect and sync 50k files 2) Same file edited on 2 laptops while offline; edits can arrive out of order 3) Atomic rename/move matters (folder reorganizations), not just file contents 4) Need fast local UX: edits show instantly; sync happens async; p95 conflict detection under 2s after reconnect 5) Must handle large files (10GB) with chunking/resume, but conflicts are per-file semantic, not per-chunk 6) Cross-device clock skew, no trusting mtime; need a version model 7) Storage is eventually consistent across regions; clients can hit different edges 8) Conflict policy: auto-merge for text? duplicate files? keep both? how do you avoid conflict loops? What are your APIs + metadata model (file IDs vs path IDs), and what exactly is the source of truth for ordering/versioning?

• 
  davidsong (@bitplane) reported 35 minutes ago

  Has @Dropbox been breached again? I just got this but it can't be me. At least I hope not. I have a randomly generated, unique password that's made in an offline password manager, I used it once on this machine when I first set it up. If I'm getting hacked the rest of you are in serious trouble.

• 
  Mapacho (@Mapacho111) reported 38 minutes ago

  @MajorianBTC But that’s the problem. Bitcoin in its current state is a decentralized Dropbox. Bitcoin failed and there’s no alternative.

• 
  Dodz4allai (@DrGhattasMD) reported 42 minutes ago

  nstead of waiting for an API integration with Epic (which is costly and slow), OmniMed Pro deploys as a Chrome/Edge Browser Extension.3 Mechanism: Most hospital EHRs (Epic Hyperdrive, Cerner Millennium, AthenaHealth) are now accessed via web browsers (Citrix/VDI or native web interfaces). The OmniMed extension "sits on top" of the EHR window as a persistent sidebar. Data Ingestion (The "Read"): The extension uses the DOM (Document Object Model) to "read" the patient notes, labs, and vitals currently displayed on the doctor's screen. It does not need a backend integration; it reads what the doctor sees, acting as a "visual reader" similar to a human assistant. Intelligence Injection (The "Write"): The extension injects its "Co-Pilot" interface into the side of the screen. It offers "One-Click Transfer" buttons to paste generated notes, codes, or orders directly into the EHR's text fields.3 Value Proposition: This "Zero-Integration" approach allows individual doctors or departments to adopt OmniMed Pro today, bypassing the multi-year IT integration queue. This creates a Bottom-Up Adoption loop similar to how Slack or Dropbox entered the enterprise—employees brought it in because it solved their immediate problems. 5.2 Viral Loops & Community Growth To fuel this bottom-up growth, OmniMed Pro leverages the Medical Creator Economy 16: MedTwitter & Reddit: Solo founders and small teams are winning by "building in public." OmniMed Pro should release "light" versions of its tools (e.g., a "Scientific Paper Summarizer" or "Anki Card Generator" for med students) to gain viral traction. These free tools serve as a "Trojan Horse" for the OmniMed brand.18 The "Secret Cyborg" Phenomenon: Many doctors already use GPT-4 on their phones ("Shadow AI") to help with drafting notes or looking up conditions. OmniMed Pro legitimizes this behavior by offering a HIPAA-compliant, secure wrapper. By solving the "compliance headache" for the individual doctor, it wins the user first, then the enterprise.20 Anki Integration: For the student/resident market, integrating with Anki (spaced repetition flashcards) creates a lock-in effect early in a clinician's career. Tools that automatically generate Anki cards from clinical guidelines or textbooks are highly viral among medical trainees. Capture the medical student today, and you have the Attending Physician of tomorrow.19 5.3 Risks and Mitigation: The "Shadow" Dilemma This strategy carries significant risk. "Shadow AI" creates governance gaps and potential security liabilities.4 To mitigate this and eventually convert to enterprise contracts, OmniMed Pro employs a specific conversion strategy: Enterprise-Grade Security by Default: Even the individual version must be HIPAA-compliant (BAA signed on sign-up). Data processing should happen locally or in compliant cloud enclaves. The "IT Trojan Horse": Once adoption reaches a critical mass (e.g., 30% of doctors in a hospital), OmniMed Pro approaches the CIO with usage data. "Your doctors are already using this tool 5,000 times a week. Let's sign an enterprise deal to give you visibility, control, and single sign-on (SSO)." This flips the sales conversation from "Please try our product" to "Please secure and manage your existing usage".4 This is the exact playbook used by companies like Yammer and Slack to penetrate the enterprise. 6. User Experience: Visualizing Uncertainty and Generative UI The final barrier to adoption is Trust. Clinicians do not trust "Black Box" AI that spits out confident answers without rationale. OmniMed Pro employs a "Glass Box" UX philosophy that prioritizes transparency and interactivity. 6.1 Explainability via Visualization Sankey Diagrams for Reasoning: To visualize the "Chain of Thought," the UI uses Sankey diagrams that show how data flowed from "Lab Result" -> "Intermediate Reasoning" -> "Final Diagnosis".12 This allows the clinician to trace the logic visually. Interactive Debate Logs: The UI allows the doctor to "replay" the debate between the AI agents. "See why the AI ruled out Lupus." This turns the AI into a teaching tool rather than just an oracle, fostering trust and verifying the reasoning process. 6.2 Agentic Generative UI Instead of static dashboards or simple chat bubbles, the OS uses Generative UI.22 The interface adapts to the context of the conversation. Dynamic Charts: If a doctor asks about "Cardiology Trends," the system doesn't just write text; it generates a live, interactive chart of the patient's troponin levels over time. Actionable Forms: If the doctor asks for a "Referral," it generates the referral form, pre-filled with patient data, ready for signature. Contextual Cards: The UI presents "cards" for different data types (medications, allergies, labs) that can be manipulated, reordered, or expanded, creating a fluid workspace that replaces the rigid, click-heavy menus of the EHR.23 7. Regulatory & Ethical Moats: Defending the OS To operate at this scale and depth, OmniMed Pro must build defensible moats around regulation and safety. 7.1 MedHELM Evaluation Framework To prove superiority and safety, OmniMed Pro adopts the MedHELM (Holistic Evaluation of Large Language Models for Medical Applications) framework.1 Unlike static benchmarks (USMLE), MedHELM evaluates models on: Clinical Utility: Is the answer helpful and actionable? Safety/Harm: Did it suggest a fatal dosage or miss a critical red flag? Bias: Does it perform equally well for all demographics? Alignment: Does it follow the specific hospital's protocols? By continuously running MedHELM evaluations on its hybrid outputs, OmniMed Pro provides a "Quality Seal" that single-model providers cannot match without deep integration into the hospital's data. 7.2 Liability Frameworks In a multi-model world, liability is complex. OmniMed Pro positions itself as a Clinical Decision Support (CDS) tool, not a diagnostic device. The "Human-in-the-Loop" is mandatory. By visualizing the debate and uncertainty, the OS places the final decision firmly in the hands of the clinician, mitigating liability risks associated with "autonomous" diagnosis. 8. Conclusion: The Strategic Imperative The OmniMed Pro 'Medical AI Operating System' represents the inevitable evolution of healthcare artificial intelligence. By moving beyond the "Model-as-Product" mindset and embracing an Architecture of Aggregation, it solves the fundamental trilemma of medical AI: Accuracy, Cost, and Trust. Leverage the Router to commoditize the giants (OpenAI, Anthropic) and extract the best capabilities of each.1 Deploy the Consensus Engine (MCC) to achieve "Super-Human" reliability through adversarial debate.2 Unleash the Swarms to automate the physical and administrative burdens of healthcare.7 Infiltrate via Shadow AI to bypass bureaucratic inertia and win the hearts and minds of clinicians directly.3 In doing so, OmniMed Pro does not just "outperform" OpenAI; it contains them, turning their powerful models into mere components of a higher-order medical intelligence. This is the path to disrupting the global medical industry. Technical Appendix: Implementation Roadmap A.1 Deploying the MCC Debate Engine To implement the Model Confrontation and Collaboration (MCC) engine 2: Select Models: Integrate API endpoints for GPT-o1 (Moderator), Claude 3.7 (Reasoning), and DeepSeek-R1 (Critic). Define Prompts: Moderator: "Compare the following diagnoses. If semantically identical, output FINAL. If divergent, initiate DEBATE_ROUND_1." Critic: "Review the diagnosis provided by Model A. Identify any inconsistencies with the provided lab values. Cite clinical guidelines." Set Thresholds: If consensus > 0.8 similarity score, output. Else, iterate max 3 rounds. Fallback: If no consensus, route to "Human-in-the-Loop" queue. A.2 Building the "Sidecar" Extension To build the "Shadow AI" browser extension 3: Manifest V3: Develop using Chrome Manifest V3 for security compliance. DOM Observer: Use a MutationObserver to detect when the EHR (e.g., Epic Hyperdrive web) loads a patient note field. Context Extraction: Scrape relevant DOM elements (vitals, meds) locally in the browser (client-side) to minimize data egress risks. Injection: Inject a floating "FAB" (Floating Action Button) or sidebar IFrame that contains the OmniMed chat interface. Clipboard Actions: Use the Clipboard API to paste generated text back into the EHR's focused input field. A.3 Setting up the Swarm Architecture To orchestrate the Swarm 13: Orchestrator: Use a Python-based orchestrator (like Swarms API or LangGraph). State Management: Maintain a shared "Case State" object (JSON) that all agents can read/write to. Handoffs: Define explicit state transitions. if (labs_missing) -> route_to(Intake_Agent). if (diagnosis_ready) -> route_to(Synthesizer). Standardization: Ensure all agents output in structured JSON (FHIR format) to maintain data integrity across the swarm. Works cited

• 
  Hiten Shah (@hnshah) reported 48 minutes ago

  @varadh @NotionHQ Bunch of markdown. Google Docs handled it well, but some of my markdown files can get gnarly and even docs chokes a bit. I’m also a minimalist with tools and workflows, trying to get away with the least amount of tools which helps a lot with speed and efficiency. I should be a power user of Notion. Since we’re here, I have plenty of folks (like you) that I know who work there now who I’ve met and like. I’m always rooting for you folks, as a result. Here are some unsolicited thoughts from holding it in for too long. I’ve used every document and notes app under the sun and spent a lot of time in Dropbox Paper and Hackpad before it. Early user of writely which became Google Docs. There are core product principles around a product like Notion that Notion breaks or seemingly optimizes for Notion over the user’s experience. At @CrazyEgg, where I haven’t worked full-time for 17 years until about a year ago, the team loves Notion. So I’m forced to use it. My most common activity is to export things out of Notion into my a chatbot or agent of choice. That has little pricks in the process than paper cuts. But all ouchies count against you. For example, in chrome, when trying to print a page (i am weird and print web pages to convert them to pdf), I can’t trust that all the content will come through. And the issues are inconsistent. I understand this is likely an edge case of an edge case, but all ouchies count, prickle or stabbing. If you got this far, thanks for reading my rant. I one shotted it with the agent between my ears.

• 
  Lowkea (@lowkea713) reported 49 minutes ago

  Dropbox if you could please fix your self I have an uncomfortable amount of music in your app and now I can’t log in

• 
  Durodiyi (@durodiyi) reported 49 minutes ago

  company’s server (like Google Drive or Dropbox), decentralized storage spreads your data across a network of computers worldwide. Platforms like IPFS and Filecoin make this possible.

• 
  Craylor (@craylor) reported 49 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.

• 
  grace ✭ (@wavescicadas) reported 50 minutes ago

  the irony of dropbox not working when your storage is low

• 
  (*´･з･)✨️ fungiter areio (@hobrincess) reported 54 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

• 
  RadhikaBGhose (@RadhikaBGhose) reported 54 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

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 54 minutes ago

  @Ultrademic @Seltaa_ @GoogleAI You’re doing something like Suno? I have something for you. All my Dropbox links are broken. I have a PDF that will help. And yes… I miss the real Ai music. •

• 
  Ouriel (@OurielOhayon) reported 57 minutes ago

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

• 
  Callitlikeitis (@Callittlikeitis) reported 59 minutes ago

  @iAnonPatriot Yeah no.. That’s even more piracy. I will Dropbox if it comes down to this drone diarrhea. Or better yet bypass lameazon all together

• 
  Dr Prosper The Philosopher (@ProsperThePhilo) reported 60 minutes ago

  Stop Storing Your Medical School Files on Your Phone: If you're a medical student having problems with where to store your lecture slides because your phone storage keeps getting full... If you're always struggling to find files on your phone... If you've ever changed your phone and lost access to your lecture slides... Then I want to let you know that this isn't really a phone problem. It's simply because you're using the wrong storage system. As a medical student, you're not supposed to be storing your important academic files permanently on your phone. Yes. Have you heard of something called cloud storage? Cloud storage simply means storing your important files on secure servers online instead of inside your phone. Think about it. Your phone has limited storage. Depending on the model you're using, it may have 64 GB, 128 GB or 256 GB of storage. But over several years of medical school, you'll accumulate thousands of lecture slides, hundreds of PDFs, anatomy atlases, textbooks, videos, practical manuals, charts, flashcards and past questions. Eventually, your phone becomes crowded. The smarter approach is to let your phone become a temporary device—not your permanent library. For example... Google gives every Google account 15 GB of free cloud storage (shared across Google Drive, Gmail and Google Photos). If you're using an Android phone, chances are you already have a Google account. That means you already have free cloud storage waiting for you. If you have a Microsoft account, OneDrive gives you 5 GB of free cloud storage. If you use an iPhone, iCloud gives you 5 GB of free storage. There are also services like Dropbox and MEGA that offer free cloud storage as well. These services exist for a reason. Use them. If you have textbooks, don't store them permanently in your phone's internal storage. Instead... Open Google Drive. Create one proper Google account dedicated to medical school. Inside that account, create folders. For example: - Anatomy - Physiology - Biochemistry - Histology - Embryology - Pharmacology - Pathology - Microbiology - Surgery - Medicine Now open your Anatomy folder. Inside it, create another folder called Gross Anatomy. Inside Gross Anatomy, create folders like: - Lecture Slides - Textbooks - Past Questions - Clinical Correlations - Charts - Practical Manuals Now begin uploading. Upload. Upload. Upload. Stick to one Google Drive account throughout your entire medical school. You'll be surprised. Five or six years later, you'll look back and realize you've built an entire medical library. Everything you've ever studied... Every lecture slide... Every textbook... Every practical manual... Every chart... Every past question... Waiting for you in one organized place. Another thing. Learn to use Google Photos. All those anatomy diagrams... Charts... Clinical pictures... Embryology illustrations... Practical photographs... Store them inside Google Photos instead of leaving them on your phone. As long as you know your email and password, you can access them from anywhere in the world. Your phone. Another phone. A tablet. A laptop. Even a computer in a cyber café. If your phone gets stolen today... Nothing important is lost. Because your library isn't inside your phone. It's online. There are paid cloud services that provide even larger storage capacities, but honestly, the free options are enough for most students starting out. Now here's a habit I think every student should build. Whenever you download something important... Don't leave it sitting on your phone. Instead: Download it. Upload it to your cloud storage. Delete it from your phone. Download. Upload. Delete. Repeat. Your phone remains light. Your files remain safe. Your library keeps growing.