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:

• 
  lonesome cowgirl lex (@besosprincessa) reported 6 seconds ago

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

• 
  Simple American News 🗞️ (@TSimpleAmerican) reported 12 minutes ago

  Dropbox CEO Drew Houston is stepping down after 19 years, with chief product officer Ashraf Alkarmi being promoted, per CNBC

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

  Interviewer: design Dropbox file sync. I paused and asked what they meant by sync. Whole product? Or just the client protocol? Single user? Team shares? Offline edits? Large files? Mobile on spotty networks? End to end encryption? What’s the SLO for conflict rate and time to converge? Once we scoped it to single-user sync across devices with offline support, I wrote requirements: detect changes, upload deltas, download updates, handle conflicts, resumable transfers, and don’t melt the battery. Non-goals: shared folders and fine-grained permissions. APIs and data model next. I used a file ID stable across renames, plus per-file version and per-device cursor. Client calls: /changes?cursor=..., /upload_session/start, /upload_session/append, /upload_session/commit, /download?file_id&version, /ack?cursor. Server tables: file_metadata(file_id, user_id, path, type, size, content_hash, current_version), file_versions(file_id, version, blob_ref, created_at), device_state(device_id, user_id, last_cursor), and an append-only changelog(user_id, seq, file_id, version, op). Architecture: client has a watcher, a local state DB, and a sync loop. It batches changes, computes chunk hashes, uploads missing chunks, then commits a new version. Server side: metadata service, blob store (chunked, content-addressed), and a per-user change log that devices long-poll or stream. Push notifications help, but the cursor-based pull is the truth. Scaling: shard by user_id for metadata + changelog, store blobs in object storage, cache hot metadata, and keep uploads on pre-signed URLs so the metadata tier doesn’t become the data plane. Chunking makes big files resumable and dedupe-friendly, but it adds CPU and more metadata reads. Tradeoffs I called out: last-writer-wins is simple but loses intent; per-file version vectors are heavier but reduce false conflicts. Chunk size is a fight: 4MB reduces round trips, 1MB retries faster on bad networks. Long-polling is cheaper than WebSockets at scale but slower to react. Failure cases: client crashes mid-upload, so upload sessions must be idempotent and garbage-collected. Network ***** cause retry storms, so exponential backoff + jitter and server-side rate limits. Two devices edit offline, so create conflicted copies and surface it in the client. Silent data corruption, so verify hashes on every download and run background repair. Rename vs edit races, so operations are applied against file_id, not path, and changelog ordering is per user, not global

• 
  SCRIBEMOON (@SCRIBEMOON) reported 15 minutes ago

  Ok great. What do we do. What can we do. I was told We were the problem, the people who vote on Election Day, we made things go slowly. VOTE EARLY THEY SAID. I voted on May 13 via dropbox. STILL NOT COUNTED. I doorknocked for Spencer. Only threatened once- by a Cedars Sinai young white female doctor. The CORRUPTION is too overwhelming. We need FEDERAL INTERVENTION!

• 
  Anuroop Kumar (@anuroopk4u) reported 19 minutes ago

  @jasonlk I remember as a teen, Dropbox set the standard. It was Dropbox, AirBnB, and Uber - as these “new economy” startups that were changing the world. Frankly speaking, Google Drive just started to do more for me and integrated easier sharing down the road. There was no value add I was getting from Dropbox once storage got commoditized.

• 
  ray🥤 (@rayontrack) reported 19 minutes ago

  bookmarked, downloaded, screen recorded, emailed, stored in hard drive, uploaded to cloud, archived, backed up, shared via bluetooth, forwarded, copied to usb, saved offline, synced across devices, added to favourites, printed, password protected, compressed into zip, renamed, organised into folders, duplicated, exported, imported, attached to message, sent to recycle bin, restored from backup, converted to pdf, edited, highlighted, annotated, watermarked, uploaded to google drive, uploaded to dropbox, shared through airdrop, linked to notes, tagged, encrypted, burned to cd/dvd, cached, mirrored to another device, uploaded to server, queued for transfer, dragged into archive, pinned, added to reading list, stored on ssd, embedded in document, linked in spreadsheet, previewed, sent to printer queue, recovered from trash, and indexed for search.

• 
  ṢƘĪÑlÖVẸ́R̃ṢX🇺🇲🌷 (@skinloversx) reported 20 minutes ago

  Hey Daddy I'm down for FaceTime 💧 Dropbox and all kind of nasty content message me for menu 💦💦 #md

• 
  J. (@munchivelo) reported 22 minutes ago

  track back to just over a year to now. i'd built an automated ecommerce flow that took a whole store end to end. seo would research trends, products, and map those into .js scripts which would launch prompts that read those research files. that would feed an image gen prompt which created designs, set to specific standard. i'd generate them, and then ANOTHER prompt, would check the images, score them with a criteria, and either move them to an accepted folder, or move them to an archive folder. the accepted folders, would automatically fire a script which would open photoshop, map the image to smart layers, in a 'product shot' template i'd made, and then export all of the final product shots to another folder, and then exported the flat designs which would be used for the products. another script took the product images, did visual lookups, generated all product descriptions, renamed the images and generated the seo text. it ran optimizations locally via a jpegoptim and oxipng script. it then uploaded them to dropbox, and via API, would generate a dropbox link map. i had one barebones csv template, which i'd run a ps1 script through to map json files into the csv rows, and insert the dropbox link map. all my images, links, followed the exact same slugs, so it turned 2 hours of manual work into a 5 second bulk rename and insert. it then converted that csv into json, which then itself converted that json into ld-json for product rich listings. ai would write the product description based on a dataseo keywords, and googletrends json file that would run on every product type. collecting keywords for that specific product. it also formed it around brand profiles, copy guides and other things. this was sonnet 3 days, GPT 4.0 days, and it STILL wrote great copy when it had the right guidance. in the .js file, i'd replace all em dashes with a hyphen if they ever appeared. i built a custom product uploader, built my own php plugin which synced to local .js files and connected via rest. it was (and still is) one of the best wc product uploaders that exist, as it completely resets filterlookups only for that product, and is lightning fast because i upload it directly into the sql from json. no importers or WC rest needed. the images would be uploaded via ftp, and then on detection, would sync those to the media library. it took what would be 3 hours of manual work, and congested it into a 2 minute image, to fully live product. after that, i'd export sales data, the ai was constantly learning, sales data feeding back to files, which would then teach the ai what products work, what doesn't. what copy worked, what copy didn't. all of it was local on my pc. i wasn't selling an saas. it was just something that worked for my very particular setup. i built that mostly with GPT 4.0 and a little bit of 3.5. copy and pasting the chats from chatGPT. all the plugins, the php, everything. then some of it got improved inside vscode back on the old original copilot plans. this was before n8n, before agents were even a thing. all of that was built for me, local, syncing folder to folder, json file to json file. python scripts watching files, and .ps1 files that would follow up with other .ps1 files, which launched .js files which contained prompts for AI, and hitting the openAI API's whenever I needed the AI layer. eventually i built a terminal tool, which would allow me to run the scripts from the terminal, and i'd manually type in the slugs for which products i wanted processed. all files would sit in specific folders, and scripts would do the rest. i was so excited about that, giving my terminal app a shortcut icon and putting it onto my taskbar. that was a year ago. fast forward to now. the game has changed so much. ANYTHING and i mean anything is possible now. i've had this ******* idea for so long, to build a fully automated, self learning ecom business, that launches products end to end based on it's own research, writing, and growth, but the complexity of it previously , and being busy with life, it never got finalized. and i've finally been building the replacement for it, but it'll be able to do many other things. i'll be able to run that exact same system, except this time through a full app, with a canvas, and agent systems instead of .ps1 scripts. not to say i won't run scripts; they're an integral part of any automated workflow, but now it has superpowers. not only that, but i moved away from woocommerce entirely. instead i just built my own website builder, which is fully automated end to end. my brand profiles, my artwork system? i'm still using those, just for more things. now i can launch 50 brands just like it, running the same system, all in about 5 minutes. except this time, a year later, we have GPT 2.0, and seedance. which offer MUCH better usage for ecommerce than it was back 1 year ago. i also built an ad builder. it takes my brands images, or generates images. i've got background removed, and full skills and agents which practically generate the ads for me. it mixes all that into seedance videos, and posts in logos etc. now i take those image/videos, and build instagram, tiktok, facebook vids, generate descriptions, and upload them automatically. that's why it's so great building for yourself. the amount of reusability you get with it, the fact it's free forever, can never be beaten. i'm not selling anything yet. but if you're interested in seeing how i think about automation, then stay a while and listen. the tool i'm building will absolutely help you too. but i'll be honest. i'm actually quite scared to release it, solely down to how powerful it is. not many people do it like i do, and i'm finally on here to tell the world.

• 
  Ashutosh Rana ⛓️ (@ashutoshrana_20) reported 23 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.

• 
  Ricker (@0xRicker) reported 24 minutes ago

  Senior engineer just dropped a GPT-5.6 stress test after burning around $200K on API usage: 00:00 - $180K–$240K spent testing GPT-5.6 in Fast Mode 02:43 - The model using browsers, dashboards and settings like a remote operator 05:32 - 67 projects and 20+ hour autonomous sessions 07:07 - Lakebed, T3 Code and native app rewrites in 2–4 hours 15:08 - Rust compiler experiments, 18x speedup and a $91K Dropbox-style build 17:46 - GPT-5.6 fixing a broken Linux GRUB boot through KVM 22:56 - 3D games, weird assets and the remaining frontend taste problem It is a field test for agent loops The future edge is not the prompt It is the loop that can keep working after the prompt stops being useful

• 
  TeX64 (@TeX64AI) reported 25 minutes ago

  that's a sync-direction race: your web edits haven't reached the local Dropbox copy yet, so Claude overwrites a stale file. nothing's lost though, Overleaf's History menu keeps every version to restore from. fix: let Dropbox finish pulling before Claude edits.

• 
  Raziel (@tryraziel) reported 26 minutes ago

  Drew Houston got rejected by 76 VCs before Dropbox became worth $12B. But the rejections weren't random — they revealed exactly what he needed to fix. 2007: Drew builds a file-syncing prototype. VCs say "there are already 20 companies doing this" and "users won't pay for storage." He realizes he's pitching the wrong thing. Storage isn't the product — seamless sync is. 2008: He creates a 4-minute demo video showing Dropbox "magically" syncing files across devices. No technical jargon. Just the experience. The video gets 75,000 signups overnight from a waiting list that didn't exist yet. Same product. Same founder. Completely different story. Key insight: Drew stopped explaining how Dropbox worked and started showing why people needed it. → Before: "We use block-level file synchronization across distributed systems" → After: "Your files, everywhere you need them" When he finally raised $1.2M from Sequoia, it wasn't because he built better technology. It was because he learned to sell the outcome, not the process. The rejections taught him something no accelerator could: how to position a technical product for mass adoption. What's the difference between how you explain your product internally versus how customers actually experience it?

• 
  Bunnie Maiiii (@imbunniemai) reported 27 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

• 
  Blackbox RMS (@blackboxrms) reported 30 minutes ago

  Running a record label in 2026 is pure chaos: spreadsheets, Dropbox, endless emails. We built Blackbox RMS to fix it. One desktop app for releases, artists, contracts, promo & royalties. Built by a label, for labels. Link in bio. What's your biggest headache? 👇

• 
  Natan Hackbarth (@Natan90850688) reported 31 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?