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:

• 
  Theeevilprincess (@Theeevilprince1) reported 5 minutes ago

  My Dropbox I cannot login so everything is being sent on telegram until further notice

• 
  lonesome cowgirl lex (@besosprincessa) reported 7 minutes ago

  Who is down to add to their Dropbox link? 👀👀👀 shoot me a message with your budget and want you wanna see!!

• 
  PodWire (@PodWireHQ) reported 10 minutes ago

  Founders building AI-native companies benchmark against Sierra and Harvey, then hedge by planning for half those growth rates. Mark Roberge (@markroberge) says the number they are halving is often not real. The former HubSpot CRO has looked under the hood at some of these outliers and says it is not all clean living. Headline ARR leans on contracted-ARR gimmicks. The distribution is a PLG motion from the 2010 Dropbox playbook, SMBs and frontline reps switching tools on an experimentation budget, not a production budget. Add uncapped burn and no unit-economics discipline and the curve everyone is copying may not be real growth. Some gold in there, he says, but a lot of Groupons and WeWorks. The trap is every founder thinking they are the exception. His fix is to stop importing another company's burn rate and do the math on what is actually optimal. Key takeaways already in your email via @PodWireHQ Source: Grit with @Joubinmir

• 
  Dan Holzrichter (@dholzric) reported 13 minutes ago

  @JoshuaKhane This is why i have primary copy on my home system, backup on local server (raid array of old hd's), and copies on google drive and dropbox for anything important.

• 
  Manoj (@HeartofManoj) reported 14 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 16 minutes ago

  Most developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.

• 
  Joshatoshi #BIP-110 (@joshatoshi) reported 17 minutes ago

  @Cryptotea Core apologists want to frame this like it’s just a spam issue. It’s all about data storage and node centralization. Bitcoin, not DropBox.

• 
  Rashad Bayram (@bayrashad) reported 18 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?

• 
  Elias Al (@iam_elias1) reported 22 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.

• 
  The Open Web JP (@TheOpenWebJP1) reported 24 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.

• 
  Some guy (@ibesomeguy) reported 24 minutes ago

  @Voxyz_ai Doesn't sound like a Codex problem, sounds like a Dropbox problem. Syncthing doesn't take your files offline, ever.

• 
  Spencer Baggins (@bigaiguy) reported 27 minutes ago

  SOMEONE BUILT A GITHUB REPO THAT TURNS TELEGRAM INTO UNLIMITED CLOUD STORAGE. 100% free. It is called UnlimCloud. Self-hosted-ish desktop app. Open source. Uses Telegram as the storage layer. You log in with your Telegram ID. Upload files. Download files. Organize folders. Manage pictures and videos in a gallery. That is it. No Google Drive upgrade screen. No Dropbox “you are out of space.” No iCloud begging for $2.99/month. No random startup holding your files hostage. Your Telegram. Your files. Your storage. Here is the full feature set: ↳ Uses Telegram as the backend storage layer ↳ Secure login with your Telegram account ↳ Upload, download, and organize files ↳ Folder-based file management ↳ Gallery for photos and videos ↳ Clean desktop app interface ↳ Built with Tauri ↳ Windows release available ↳ macOS and Linux coming soon ↳ MIT licensed ↳ Open source 885 GitHub stars. 125 forks already. Here is why this matters: For years, cloud storage companies trained everyone to rent space for their own files forever. Photos? Pay. Backups? Pay. Large folders? Pay. Team storage? Pay more. UnlimCloud is the opposite idea. Take an app people already use every day. Telegram. And turn it into a private cloud drive with a clean file manager on top. No storage subscription. No SaaS dashboard. No “pro” plan. Just a weird, useful, open-source hack that feels like it should not work this well. Built in HTML + Rust. MIT License. 100% Open Source.

• 
  Pixelhop (@pixelhopio) reported 30 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 👇

• 
  EchoMind (@ai0echomind) reported 30 minutes ago

  Everyone's arguing about which cloud API is cheapest. Almost nobody's asking what happens when the smartest teams stop paying at all. A quiet migration is already underway. Most of AI Twitter is still comparing token prices inside the room the smartest teams already walked out of. The debate right now runs on the exact same track it always does. AWS vs Anthropic vs OpenAI: which model is cheaper per million tokens; which volume discount kicks in at what threshold; which enterprise deal moved which quarter. All of it real, all of it loud, and all of it happening inside the assumption that renting AI compute is the only reasonable option. That assumption is where most of the argument sits, and it is quietly getting tested by teams that stopped participating in it altogether. The clearest visible case is a Chinese startup that packed roughly 1,000 Mac Mini M4 computers into a single data center to run AI workloads without paying ongoing cloud fees. Each unit costs $599. Each draws between 10 and 30 watts under load, compared to 300 to 500 watts for a traditional GPU server. Total hardware outlay for the cluster is under a million dollars, in a category where the equivalent GPU infrastructure runs closer to ten. Once the build is paid off, the ongoing bill is electricity and a small operations team. That is the entire cost curve, and it stops moving after year one. None of this is a new pattern. In 2015, Dropbox was paying AWS more than $200 million a year just for S3 storage. Between 2015 and 2017, the company moved most of its infrastructure onto its own hardware and saved $74.6 million in the first two years alone, and its gross margins went from 33 percent to 67 percent. The tech press at the time called it a bet against conventional wisdom. It also turned out to be one of the highest-leverage financial decisions the company ever made. Every time a rented input gets cheap enough to run locally at scale, the market that rented it starts shrinking, and the teams that notice first collect most of the benefit. The uncomfortable thing about this pattern is that it is easy to miss because the loudest people in the market never leave: cloud providers keep publishing pricing pages; analysts keep tracking token costs; founders keep tweeting spreadsheets. Meanwhile a smaller, quieter set of teams is running the same workloads on hardware they own, at a fraction of the recurring cost, without an announcement thread about it. The exit is not visible in the debate because the teams who exited stopped participating in the debate. Which category of AI work in your life still feels expensive today, but might not need a cloud API in eighteen months? Save this. You will want it back when the first big AI-native company announces it is bringing its inference workload in-house. Follow for the next one.

• 
  Justin Reinhart 📯📯 (@justinreinhart) reported 34 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.