Dropbox 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:

• 
  Dr Prosper The Philosopher (@ProsperThePhilo) reported 2 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.

• 
  Evan Logan (@evanlogan) reported 2 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.

• 
  StarHaze (@ST4RHaze) reported 2 minutes ago

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

• 
  glitterandspit (@Glitterandspit) reported 5 minutes ago

  Dropbox down. Computer updating. I have a free day I suppose.

• 
  AaronAlamary | Parking (@aaron0505) reported 10 minutes ago

  I saved my grandfather's voicemails for years. Birthday wishes. Questions about his computer. Who to call to fix his A/C. Upgraded my iPhone and they were gone. Devastated. Found them today sitting in my Dropbox. SO glad I get to hear him again!

• 
  Phillip Shoemaker (@pbsIdentity) reported 12 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  More Gravy (@lotsmoregravy) reported 14 minutes ago

  @FFT1776 Deputize our military and send them to literally every last damn polling station and dropbox in the United States of America. Every last damn one. Give them the authority to handle **** on the spot. Problem solved.

• 
  Abhi • AMZBoosted.com (@AbhiChauddhari) reported 15 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.

• 
  Duaa 🤲🇮🇳 (@Duaa_1206) reported 17 minutes ago

  @himasoraakane Doing digital forensics on Dropbox error screens to investigate a suspended account is a whole new level of investigative work.

• 
  ericleebristol (@iamericbristol) reported 17 minutes ago

  Email scams but they also use a press cloud server that can hold up to millions of emails and send out messages in a bulk but to hundreds of people complicated when it comes to taking down email scams cuz you have to find where they coming from answer in a cloud compressed server that can hold up to millions of emails frequently combine compressed attachments (like ZIP, RAR, 7Z, or TGZ files) with cloud storage or servers to deliver malware, phishing pages, or credential-stealing links while trying to bypass security filters. Common patterns 🚩Malware in compressed attachments: Attackers send emails with ZIP or similar archives containing executables, scripts (VBS/JS), or disguised files. Some use specially crafted or nested ZIPs, password-protected archives (password given in the email body), or less-common formats that email gateways may not fully unpack or scan. Opening/extracting the archive can install remote-access tools, stealers, or ransomware. Cloud storage phishing (“storage is full” or similar alerts): Emails impersonate Google Drive, OneDrive, iCloud, Dropbox, or generic “Cloud Storage” services. They claim storage is full, a payment failed, or files will be deleted, creating urgency. Links often point to real cloud infrastructure (e.g., Google Cloud Storage Azure Blob, or other legitimate buckets) that host redirect pages or fake login/upgrade forms. This makes the links look trustworthy and helps them pass filters🚩.

• 
  Y (@ys_tachikake) reported 19 minutes ago

  @DropboxSupport @LIBSCRUSHER Can't login..

• 
  The Open Web JP (@TheOpenWebJP1) reported 22 minutes ago

  @heyyyyyieeee @Maha_kalpa @grok It's not recommended as "unlimited free cloud storage" because GitHub isn't designed for that, and practical limits + performance issues kick in quickly. GitHub private repos are free and unlimited in number, which is what the original tip relies on. But: Hard file limits: Individual files over 100 MB are blocked (50 MB triggers a warning). Browser uploads are capped even lower (~25 MB). Larger files require *** LFS. Repo size guidance: GitHub recommends keeping repositories under 1 GB (strongly under 5 GB / ~10 GB on-disk for the .*** folder). Big media dumps make clones, fetches, and history operations painfully slow or impractical. *** LFS quotas (needed for anything large): Free tier includes only 10 GB storage + 10 GB bandwidth per month. Exceed that and you hit blocks or billing (depending on settings). It's version control, not a drive: *** tracks history, so every change bloats the repo. Binaries (photos, videos, etc.) are inefficient in ***. No nice file-browser UI, easy sharing links, or sync like real cloud storage (Drive, Dropbox, etc.). Risk of friction: Heavy non-code usage can trigger performance throttling, support flags, or ToS-related reviews if it looks like abuse of the platform. GitHub actively monitors repo health signals. It's fine for small code-adjacent backups or a few files. Terrible as a general-purpose unlimited media dump. Use actual cloud storage (or object storage) for that.

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

• 
  VC Intern (@the_vc_intern) reported 23 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.

• 
  Dinnu daniel (@daniel_adinnu) reported 26 minutes ago

  Ariana Grande said “I’ll see you in jail, literally” to whoever was leaking her music. On Monday, she filed the lawsuit that starts making good on it. The suit, filed in Los Angeles County Superior Court, names John Doe defendants she’s suing specifically to identify, accusing them of invasion of privacy, violating California’s Comprehensive Data Access and Fraud Act, and conversion. It describes not a single breach but a pattern stretching back years: in 2019, hackers stole a photographer’s Dropbox login and downloaded unreleased photos. In 2020, a producer’s phone was compromised, surfacing unreleased masters, demos, and recording session footage. In 2023 alone, 45 unreleased songs were stolen and leaked. In 2024, hackers built a fake email domain impersonating a photographer to trick a digital technician into handing over unreleased images. The complaint states that hundreds of similar leaks have occurred since her 2011 debut, with stolen material allegedly resold on the dark web for what it calls significant sums. The 2023 wave is what made the pattern impossible to keep quiet about. One of the leaked tracks, “Fantasize,” a collaboration with longtime producer Max Martin, spread across TikTok well before any release date. Grande addressed it publicly on the Zach Sang Show in early 2024, laughing through her own anger as she called the leakers “thieves, pirates, crooks” and joked she’d pay them more just to make the leak disappear. The lawsuit’s real target isn’t a single hacker. It’s the access itself, the accounts of the photographers, producers, and technicians who work closest to her, treated as the weak point in a system built to protect the artist directly. Grande isn’t suing to recover songs that are already out. She’s suing to find out who keeps getting in.