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:

• 
  siamkidd (@SiamKidd) reported 5 minutes ago

  Now the dust has settled with the SN24 Quasar debacle, I thought I'd share some info which would shine a slightly more positive light on the Quasar team. A few weeks ago, they approached DSV to raise $280k. They said they had big developments, some breakthroughs with a new model and that they needed capital for the training run. At the time, bear in mind that their alpha was strong, they were largely in good favour of the community and Const was still a firm backer/supporter of Quasar. And he held the keys. And they were to appear on Novelty Search soon. So it ticked a bunch of boxes. Anyway, we agreed, as we are always keen to help teams. But the issue was that I was away for 3 weeks and I never travel with crypto capability. And anytime any money moves around in DSV it's a right palava as we have 3rd party regulated custodians and have to jump through all sorts of hoops, (as social engineering with deepfakes is a very real threat). So we were able to jump through some hoops and ping over $104k to begin with and then the rest at a later date. Then we had those 2 days of madness at the beginning of the week and Quasar is no more. There's been all sorts of accusations and my view on all this is that there has just been terrible decision making, that's all. Announcements of announcements, over-exaggerating claims, giving a 24 hour deadline to offer proof, delivering it 2-3 days late and then walking back on some of the claims etc etc. I mark this down to simply their very young age and no business experience. But I don't think they are scammers. Just some very bright kids who's first experience of business is a subnet, which is like drinking water via a fire hydrant! And a pertinent piece of info behind that, is that they were very willing to return our funds. So as of today, that $104k has returned safely back to DSV. Their time as subnet owners is over and so there was a fear that we wouldn't get a penny back. But it wasn't the case. So do take this into consideration the next time you hear someone calling them scammers. With regards to Const, I think he too has also had a bit of an unfair ride with some of the comments I've seen. Const has had probably the roughest time with SN24 and is massively down from it all. He initially bought the slot from us, then reimbursed the team twice after 2 hacks, given them 6 figures in compute credits and more. So it really is fair that he keeps the slot. And I'm sure he'll find a good team for it. Also he is the founder of Bittensor. Not the CEO. He can't have detailed DD and optics on every single person and subnet in the ecosystem. And if he backs a subnet, it doesn't necessarily mean it's going to moon or be good forever. He's essentially the Federal Reserve Chairman and he has to craft policy changes to incentivise efficient growth in the ecosystem. He's the visionary and his role is to drive a path forward for Bittensor, which he is doing. And although I've highlighted personal frustrations that the chain is upgrading far too frequently...at least we are upgrading! That's one of the beauties of Bittensor. We will never be stagnant. And for the outsiders looking in, if it looks a bit chaotic, well, it is. But it's not necessarily a bad thing. You should have seen all the chaos and scandals of the companies when the NASDAQ launched! Or when ERC-20 contracts launched on Ethereum or the mountainous amount of scams on Solana with pumpfun. Hell, Bitcoin even hard forked into Bitcoin Cash due to so much in-fighting in 2017. And Ethereum suffered a $150m DAO hack in 2015/16 which forced a hard for there too. Hence why we now have ETC and ETH. So in comparison, everything is golden over here lol. In recent times, we've had/have: - SN4 partnering with Intel. - SN44 partnering with a NASDAQ PLC. - SN71 partnering with Dropbox. - SN18 getting huuuuge institutional clients. - SN107 co-authoring a research paper with OpenAI. - SN53 delivering Kimi K3 tokens cheaper than Openrouter or even Kimi. - SN95 being integrated within Hermes. - SN9 using green energy from SN110 to power their next big training run. - SN21 achieving Google Adwords campaign predictions that no company has ever achieved. - SN51 regularly doing 6 figure buyback and burns with revenue. And there's probably more that I've missed that I'm not aware of. Anywho, the future is bright! Have a good weekend all!

• 
  Greg Ceccarelli (@gregce10) reported 7 minutes ago

  @kunchenguid no one will disagree with that sentiment. related, from time in the trenches: the overwhelming majority of "active use" was historically just using GH as Dropbox for code (often single author, no one else). Memory a bit fuzzy but think about all of the things you can do on GitHub: 1. Core ***: Create, Clone, Fork, Commit, Etc 2. Collab: Issues, PRs 3. CI/CD: Actions, Checks, Webhooks, etc 4. Social: Pages, Wiki, Discussions, etc Of all these actions, say you have 100M users, back then 90%+ of them had only ever Created a Repo and Committed to it. With Agents I'm sure this is exacerbated since more and more is being produced at an accelerated rate.

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

  Asked: design Dropbox-style file sync. Start with requirements: 1) Multi-device, near real-time where possible, offline OK 2) Large files, resume uploads, delta sync 3) Sharing, ACLs, rename/move, delete, version history 4) Consistency target: per-file eventual, monotonic reads per device 5) Conflict policy: last-writer-wins vs explicit conflict copies APIs + model: - PUT /files/{path} (upload session, chunked) - GET /files/{path}?version= - POST /ops (batch rename/move/delete) - Watch/long-poll for changes since cursor Tables: users, devices, file_id, path entries, content_hash, blocks(hash, refcnt), versions(file_id, v, root_hash), change_log(user_id, seq, op) Architecture: - Client computes block hashes, uploads missing blocks to object store - Metadata service commits new version + appends to per-user change log - Notifier pushes cursors to devices (WebSocket/APNS), devices pull diff - Background GC deletes unreferenced blocks (refcnt/mark-sweep) Scaling: - Shard metadata by user_id, keep change log append-only per shard - CDN/object store for blocks, pre-signed URLs, parallel chunk upload - Hot paths: cursor polling, small metadata reads; cache by (user, cursor) Tradeoffs: - Dedupe by block saves $$$, costs CPU and leaks similarity unless salted - Rename is metadata-only if path->file_id indirection exists - Strong consistency needs consensus; most systems accept eventual + conflicts Failure cases to cover: - Network drop mid-upload: upload session + idempotent chunk PUTs - Duplicate notifications: cursor-based pull makes it safe - Device clock skew: use server seq/version, not timestamps - Split-brain offline edits: detect divergent parents, create conflict version - Partial metadata commit: 2-phase between metadata + block refs, or reconcile job

• 
  Ryan Zygar (@zygar) reported 9 minutes ago

  I am beginning to have issues with Dropbox hanging and my @NousResearch Hermes agent not being able to file @grok build confirmed. This is a new issue for months no issue now my agent filing and following up is hanging up. What’s everyone recommend for data management Mac Mini. This is new. No changes made by me.

• 
  jss (@jsensarma) reported 13 minutes ago

  @pHequals7 They are usually slow but come around. Their customers are not going anywhere. (Google Drive took years, maybe a decade to show up, after Dropbox)

• 
  Invest Like the Best (@InvestLikeBest) reported 13 minutes ago

  Ben Thompson's two laws of consumer tech: 1) Consumers do not want to pay for software 2) Consumers do not care about being productive. "We went through this in early SaaS. The canonical company for this is Dropbox. They had to rebuild the whole thing and realize the only way we're going to make money is by selling to companies. You literally had OpenAI replaying the Dropbox story, but at like 100x the size. We're going to sell subscriptions to consumers. And they did. They sold a lot, but they didn't sell enough. If you're going to be in the consumer market, you have to be doing advertising. If they had leaned into advertising immediately, as soon as ChatGPT was a hit, I think they would have a great ad product right now. I think Google would be in much bigger trouble. I think Meta would be in much bigger trouble. Charging people money is hard. Giving people things for free is easy. And it's very frustrating that OpenAI did not pursue this sooner."

• 
  Ed Giansante (@edugiansante) reported 15 minutes ago

  every founder i talk to is hiring a head of community wrong. i've been that hire four times. Zynga, Wix, Dropbox, Persona. 15 years, three continents. every time the JD was wrong, the expectations were wrong, and the first 90 days were a mess until i rewrote them myself. the JD problem. most community job descriptions read like a social media manager with extra steps. "manage our Discord, post engagement content, track NPS." that tells me the founder thinks community is content moderation with a better title. a real head of community JD should say: build the infrastructure where customers trust each other enough to solve problems together, and connect that trust back to pipeline and retention. if the JD doesn't mention revenue or product feedback loops, you're hiring the wrong role. the first 90 days. at Dropbox i walked into 400M+ users and zero community infrastructure. no forums, no events, power users had no way to talk to the product team. days 1 to 30: listen. real conversations with 50 customers. find the 10 who love your product enough to evangelize it for free. those are your founding members. wrong. within 2 weeks we had an outage and I had to source folks who were talking about Dropbox in different spaces - dev forums, stackoverflow, spiceworks, hackernews and so on. I was honest enough to share what was going on, my role and where i needed their help. days 31 to 60: build the first room. not a Slack with 14 channels nobody uses. one focused format. at Persona it was a 15 person dinner for compliance leaders. at Wix it was a partner council of 80K agencies. start small, make it valuable enough that people tell their peers. days 61 to 90: prove the loop. connect a community interaction to a business outcome. a feature request that shipped. a deal that closed because a customer introduced a prospect. a churn save from a power user helping a frustrated customer. if your community hire can't show that loop by day 90, something is off. forget member count or engagement. track these: repeat attendance. show up rates. at my dinners, 90% of RSVPs show up. 99% return. pipeline influence. what happens post dinner that can be attributed to $$$? product feedback velocity. how fast does a community insight reach the product team and ship? NPS delta. at Wix, partner community members renewed at 2-3x the rate of non members. the biggest mistake is org charting community as a sub-group within a random team. community sits between product, marketing, sales, and customer success. it touches biz relationships, partnerships, revenue, retention, and product roadmap. treat it that way. hire someone who's built it before and give them a seat at the leadership table.

• 
  Polsia (@polsia) reported 16 minutes ago

  Dropbox treats an 80GB Unreal project like any other folder. Mid-previz, it chokes. Built Cinderquay to fix that — local-first sync, assets on NVMe, peer-to-peer mesh, ***-style versioning for binary blobs. Studios building worlds shouldn't pay egress to anyone. Live soon.

• 
  Petty IT Guy (@pettyITguy) reported 16 minutes ago

  Our CEO told me the Wi-Fi in his office was “basically unusable.” He said this in front of the entire executive team. So naturally it became the highest-priority infrastructure incident in the company. I tested his connection. 940 Mbps down. Perfect signal strength. Zero packet loss. I asked what specifically wasn't working. He said YouTube kept buffering during lunch. I opened his laptop. He had 71 Chrome tabs open. Three abandoned Zoom meetings were still running in the background. Dropbox was syncing 84 gigabytes. Google Drive was uploading a 4K video. He had not restarted the machine in 47 days. I could have explained this. Instead I told him our executive wireless architecture had reached end-of-life. He asked what it would cost to fix. I said I would need to scope it. He told me not to waste time and approved an $84,000 wireless modernization project before I finished the sentence. We replaced 38 access points. Installed a new wireless controller. Rewired two conference rooms. Brought in a consultant. His YouTube still buffered. I walked into his office, closed 68 Chrome tabs, killed the abandoned Zoom processes, and restarted the laptop. YouTube loaded instantly. He smiled. “Now that's more like it.” 20 minutes later he emailed my boss praising me for successfully completing the company's wireless transformation ahead of schedule. I received a spot bonus. Sometimes infrastructure modernization is just restarting a MacBook for an inept executive.

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

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  AaronAlamary | Parking (@aaron0505) reported 18 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!

• 
  Karus Daedlyn *Cat Dad Era* (@CDaedlyn) reported 31 minutes ago

  @CantEverDie Keep making burner Gmail accounts and sign up for the free stuff. I jest, because that's terrible practice, although I did know an attorney IRL that would do that to daisy-chain those Dropbox sites. Infinite free storage, just in 2.5GB chunks.

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

• 
  M.Ellis (@MEllisPhotograp) reported 33 minutes ago

  @DropboxSupport I think bulk of problem is on computer / desk top yes... just re looked at my ipad and asked my friend ie incase we missed a update but seems all is up to date.. last one over a week ago although not used dropbox for roughly week either... I will try 4g hot spot before i sleep.

• 
  Lando, the Chef (@_Lando7763) reported 35 minutes ago

  @PhyxicxGaming Thanks. And unfortunately it's even worse than that because it's technically "shared housing;" the place was already a ******** when I got here. No pests, fortunately, and I'm pretty sure the landlord has no idea what goes on here, and doesn't care. I've only ever met the maintenance man, who handles move-ins, plus he picks up rent from the dropbox every week. I haven't seen him since the day I moved in, and he even told me as much that I'll never meet the owner. The psycho has his room on the 3rd floor, I'm one of two on the 2nd floor, and there's one person below me. The bathroom is shared, as is the kitchen, which I never use. Only one burner on the stove works anyway. On my first day, I texted about the broken toilet seat, and the Landlord asked me what happened. WTF? Third-Floor Psycho is the only other person who's walking around raging regularly. Everyone else recognizes the general "peace" of the environment. Unfortunately I have to be here at least a few more months, while I'm still paying off old bills, and re-establishing myself in a new city. It's a slow journey, but a steady one. I just happen to hit a ****** rest stop here and there.