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 (67%)
• Sign in (33%)

Live Outage Map

The most recent Dropbox outage reports came from the following cities:

City	Problem Type	Report Time
Flumet	Errors	10 days ago
Irapuato	Errors	12 days ago
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	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:

• 
  Christopher Doyle (@djfunboy) reported 28 seconds ago

  @iamlukethedev CLI updates changed the signed binary and dropped macOS permissions Dropbox/TCC made jobs work interactively but failed headless (this took some time to figure out) Claud auth refresh broke and continue to break despite multiple attempts and setup tokens. Agent confusing to use API vs subscriptions. Article jobs failed on missing configs, QA turn limits, and clunky validataion Digest existed but failed to pick up silent failures Some jobs reporting done while producing nothing, without a final artifact verification I am an experienced builder but also self/agent taught so these are mostly setup and validation issues. My bigger point is that these take work and especially the more complex tasks. I am still early and I have put more work than value created but I can see the light at the end of the tunnel.

• 
  Nathan (@arcane_bloom) reported 58 seconds ago

  He was OpenAI's first business hire in 2018. This week, after eight years, he walked out the door. > Brad Lightcap > studies economics and history at Duke, starts as a JP Morgan investment banking analyst > moves into strategic finance at Dropbox, then joins Y Combinator's Continuity Fund > meets Sam Altman through YC, gets pulled into a tiny nonprofit called OpenAI in 2018 as its first business hire > becomes CFO, then rises to COO, helps run the company through the ChatGPT launch and its climb to the most valuable startup on earth > moved off the COO title in April 2026 into a vague "special projects" role > in August, posts on X that he's leaving after eight years to "start something new" > his exit lands one month after product chief Fidji Simo also stepped down > walks away right as OpenAI preps a monster IPO on an $852 billion valuation

• 
  Rish Agarwal (@rish404) reported 2 minutes ago

  Imagine you have a team covering an event. Boots on the ground. What's the best way to get footage from all of them in a single library Dropbox? Google Drive? Physical hard drives? All of them either don't support it, requires an account for every person or just physically slow and limited Here's how @cutsio is solving that

• 
  Mike Nolan - ⌬CatalyticComics⌬ (@CatalyticComics) reported 3 minutes ago

  As a developer I wanted to build something that addresses every issue I've run in to as a reader. These are my top ones: - Campaigner emails a Dropbox link and maybe you miss it - DRM/server requirements that amount to "you don't really own it" - No above-board way to share

• 
  Arthur Terrell Vaughn (@ArthurV36405381) reported 18 minutes ago

  @patmendoza6745 I know not of any of those specifications, but I still can’t figure out what the issue is with persistent memory, why can’t I just have a dropbox online that it can constantly access every single chat and conversation?

• 
  Hugo Bowne-Anderson (@hugobowne) reported 20 minutes ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)

• 
  Kieran 🥃🎶🐇 (@KGeorgee) reported 20 minutes ago

  @datarade NET? Probably region of 45% 5k+ companies now? Not all are exits or in cash yet will be propped up a lot on Stripe dropbox doordash coinbase if we go gross probably close to 70% by now? Some bad perfromers in there of course too that will bring it down. nuts figure ngl

• 
  🪬M🪬 (@_marokiya) reported 22 minutes ago

  Apple be bullshitting about this iCloud storage. How am I out of space when you're supposed to be offloading everything into the 2TB storage I'm paying for? Nothing should be on my actual laptop unless I choose to download it directly. DropBox somehow never has this issue.

• 
  numaan (@numaan27) reported 23 minutes ago

  they solved this problem in panda by splitting the key space into “ranges.” each range is roughly 100 GB, so when a range grows too large, it can be split and redistributed. (btw panda is an abstraction layer over sharded mysql that dropbox built)

• 
  WPBeginner (@wpbeginner) reported 24 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  Ed Giansante (@edugiansante) reported 26 minutes ago

  community is not a Slack channel. I've been building communities for 15 years across Zynga, Dropbox, Wix, Persona, and my own project Edublin. And the biggest misconception I still hear is: "we launched a Slack, so we have a community." You don't. Slack, Discord, forums, Circle... those are all tools. Community is what happens when people trust each other enough to be honest. I've seen companies spend six figures on community platforms and end up with a ghost town. I've also seen a group chat of 12 people generate more value than a 10,000 person Slack. The difference is the architecture: who's in the room, how they got there, what the norms are, and whether people feel safe enough to say what they actually think. At Dropbox, we had 400 million users. The "community" wasn't a platform, it was the trust between power users who helped each other solve problems the support docs couldn't. They needed to know they were talking to someone who understood their situation. At Wix, I built an 80K partner community. The platform was secondary. What mattered was that web designers felt seen by a company that historically marketed to DIY users. The community was the signal that Wix took professionals seriously. Edublin started as a blog answering questions for Brazilian expats moving to Ireland, with no dedicated platform or app. It became the largest community of its kind because the trust was real. People showed up because they knew they'd get an honest answer. Community is trust. Community is the reason someone comes back. Every time I evaluate whether a community is working, I ask one thing: would these people show up even if the tool disappeared? If yes, you have something real. If not, you have a group chat.

• 
  Lindsey Gaetani (@lindseygaetani) reported 27 minutes ago

  This piece of information is much more important than many realize. Cosgrove & Kate Peter got very lucky with my "countersuit" against Cosgrove, et al, in that they were able to use that as a convenient excuse to not continue with the wiretap & WI charge against @DoctorTurtleboy involving myself. But the truth of the matter is that Pam 'The Scam' Friedman (my "advocate" aka handler assigned by corrupt Brian Tully) informed me weeks before they had any knowledge of my countersuit that Cosgrove was having some "difficulties". She informed me that they could not locate the wiretap evidence that was shown to the grand jury when I testified. She even asked ME if I had a copy that I could provide to them. Evidence submitted before a grand jury is suppose to be saved and cataloged, so explain to me how exactly it goes "missing." Well, I can help you. See there were two videos. The original video in which I was recorded from a pocket. And the edited video that is spliced to make it appear as though I agreed to being recorded (the infamous "I know, I know" response). Kate Peter claimed that the original video was given to her by a woman who Aidan had sent it to. Big problem with this, the woman "didn't want to be involved", so her name was never mentioned during any police report or part of the grand jury, let alone did she testify to authenticate the videos. Instead, Tully had Kate save the original video to a Dropbox folder and email it directly to him, to make it appear as though it came from her and that this was the original chain of custody. Big no-no. As time went on, Kate's name began to take center stage, along with her shady involvement and criminal behavior. The secrets of her helping Mello were exposed so they had no choice but to see that these charges were squashed as to not contaminate the rest of the charges against Aidan. So what did they do? They had Kate delete the Dropbox file, and the evidence it contained. Kate Peter tampered with evidence in a felony trial. They must have took a big sigh of relief when I sued Cosgrove because it gave them a very easy out and they were able to wipe their hands clean as if none of this ever happened. Except it did. And Kate Peter still inserted herself into the other charges. For this reason alone, Aidan's charges should be dismissed.

• 
  FarhanX_AI (@FarhanBuildsAI) reported 28 minutes ago

  SETTING #1: Startup Apps Nobody Asked For What it does: Every time you install a new program, it quietly adds itself to a list of apps that launch the second Windows boots, whether you use it daily or once a year. Why it kills performance: Your laptop isn't just starting Windows when you power it on. It's simultaneously launching Spotify, Steam, Adobe updaters, Dropbox, Zoom, and a dozen other programs all fighting for the same limited CPU and RAM at once. How to fix it: Ctrl + Shift + Esc to open Task Manager → Startup apps tab. Disable everything except your antivirus and anything you genuinely open every single day. The technician found 19 apps launching automatically on her laptop. She recognized maybe 6 of them.

• 
  Palpy (@evgenij_rabij) reported 29 minutes ago

  A 32 YEAR OLD PRAGUE DEV BULK-BUYS $180 CHINESE NAS BOXES AND NOW PULLS $7,200 A MONTH SHIPPING PRIVATE DROPBOX-KILLERS TO EU FREELANCE DESIGNERS While massive brands scramble to lock teams into clunky, data-mining cloud databases, this creator built a private intelligence system that secures sensitive data and brings in a massive stream of passive revenue every single month. He makes a steady $7,200 every single month by building and configuring private cloud and AI indexing hardware for EU freelance designers who want to escape subscription traps. The entire micro server fits right on the corner of a desk and runs on an ORICO metabox HS200 pro unit. This tiny sliver of hardware packs an Intel N100 processor, 8GB DDR4 RAM, and pumps out local cloud performance on a machine the size of a coffee coaster. Instead of letting his clients burn cash on recurring cloud storage retainers, the engineer pairs the board with two refurbished 30TB hard drives in RAID 1, pre-installs the software, and sells the complete physical package at a premium. Pause at the 0:02 mark in the video where the drive slides in: that is a sleek metallic chassis hosting a $1,000 mini-NAS holding 30TB of encrypted client data. The core value proposition of this setup comes down to absolute data privacy, zero monthly fees, and strategic scalability. Mainstream cloud providers like Dropbox Business can never offer this level of value because they bill €2,400 a year for the same storage tier while uploading private user files to external cloud networks. Here, the ORICO metabox pulls off the entire magic trick locally inside the office. Running on Ubuntu Server 24.04 and MinIO S3-compatible storage, the system automatically triggers a local Qwen 2.5 VL 7B model to run localized RAG pipelines directly over the user's PDFs and Figma exports. Through this custom setup, designers get access to lightning-fast local cloud storage, zero third-party data tracking, and a smart visual search assistant built right into their private drive. This case study is a textbook example of how accessible hardware combined with a smart setup service can unlock unique niche products that solve real human problems, and you can catch the full assembly pipeline in the video below.

• 
  Shadow_Vortex_2025 (@Shad0wV0rtex) reported 29 minutes ago

  @FrancoisOlwage @bot I ran into a similar issue just trying to connect Dropbox, ClickUp, and Google Sheets, and all my tokens were already gone.

• 
  John B. Holbein (@JohnHolbein1) reported 31 minutes ago

  Replication has become much easier in the era of generative AI. I'm not the first person to say that. However, I've seen fewer people acknowledge a specific aspect of this lowered cost for replicating scientific work: Generative AI will very soon allow us to assess the robustness of individual scholars' full bodies of work. Soon, we will be to compute measures of which scholars do robust science, and which do not. What's wild is that we may be able to almost do that already. Let me show you what I mean. In June, I gave Claude a pretty basic prompt. It read: "I have a big task for you. I want you to start a folder. Call it Acemoglu Replications. Then, go find as many replication archives for Daron Acemoglu as you can. Keep a spreadsheet of the ones you can find and those you can't. Then, start a replication/reproduction effort on those articles. People have in the past criticized the research designs and general robustness of his individual papers. I want to know how strong his body of work is as a whole. Don't come in with any prior beliefs; be dispassionate." I let Claude run overnight while I slept. When I came back in the morning, 29 of Acemoglu's replication archives were fully loaded in my Dropbox. All the code reproducing the paper's results had run. And there was a first draft of a paper assessing the robustness of Acemoglu's full body of empirical work. I'll admit, the first draft of the paper wasn't great. But with 15 short follow up messages--which took me about an hour to write--I was able to prompt engineer a paper-length examination of Acemoglu's work. I've attached the screen shot of the abstract below. I think this reassessment of Acemoglu's work is certainly not done. I'm posting the abstract as a proof of concept, rather than a definitive answer. I'm not posting the full paper yet because I think it still needs more work. Ultimately, I paused this project for three reasons. 1.) Limited time/topical expertise: Most of Acemoglu's work is outside of my area of topical expertise. So, I have limited time to work on it. What this type of a project really needs is someone who has the time and the know-how to dig into each of the replication's individually to make sure they are doing the right things. I think the ideal approach combines the breadth that LLMs afford and the depth of attention/expertise that humans can give. 2.) Questions about the value of the "assess one scholar at a time" enterprise: I totally get that having a database of scholar-level robustness metrics would be very valuable in theory. But what I don't know is whether this approach is truly valuable. Moreover, doing so would come with distinct challenges. a.) Many journals have very restrictive space constraints. A body of work approach would, of necessity, be very long. b.) Collecting replication archives is harder for some types of scholars (those who post them all on their websites) than others (those who don't). c.) We'd have to think hard about questions like: what scholar-specific robustness metrics would be best? And: how would we deal with the fact that prolific authors' robustness metrics would be estimated much more precisely than less prolific scholars? Additionally, I'm just not sure that "taking on" one scholar at a time has enough scientific merit to pursue. If I measured how robust an individual scholars' work is, I'd ideally want to know where that metric stands vis-a-vis the rest of scholars in that field/area. To do that, we'd ideally want the population of these scholars or, at minimum, a random sample. Concretely, if Acemoglu has, say, 78% of published headline results reproducible under some standardized protocol, is that excellent, mediocre, or terrible? To answer that, you need a reference distribution. That makes a random or otherwise well-defined sample of scholars much more attractive than selecting prominent individuals one by one. (I'll acknowledge that I may just be wrong on #2. Arguing against myself, I do agree that human-driven reproduction/replication work rarely assesses full/representative slices of a field. Instead of assessing one scholar at a time, we assess one paper at a time. Field-wide detective work is becoming more common, but my sense is that it's still the exception rather than the rule.) 3.) Cost/benefit considerations and replication norms: we have very weakly formed norms around reproduction/replication generally speaking. We have basically no developed norms around replicating individual authors one at a time. What this means is that the people who would lead a scholar-by-scholar replication effort will, likely, bear a heavy cost and, potentially, reap limited benefits. On the costs side, focusing on scholars' total bodies of work risks making the replicators look petty, vindictive, and antisocial. Enough of the scientific field is hostile towards replications of individual papers. Imagine what will happen if/when a scholar submits a scholar-specific "take down" of a full body of work. My sense is that it's common enough for scholars having their work replicated to be asked to be a reviewer for those manuscripts. I've seen very hostile responses when one paper is at issue. Imagine what type of reviewer Acemoglu would be for a paper that took on his entire body of empirical work! Even if Acemoglu weren't a reviewer, prolific authors tend to have wide coauthor/friend networks. The rally-around-my-friend dynamic we often see would certainly work against this type of paper being published. Even a completely neutral analysis acquires an accusatory character simply because the sampling unit is a named person. And that creates an unfortunate problem of its own: readers may interpret the choice of scholar as evidence that the investigators expected to find something. On the benefits side, replicating individual scholars' total body of work may offer limited payoffs. What journals would accept this type of scholar-specific replication? I'm not sure the top ones would. Conclusion: Generative AI has enormous potential in assessing and, ultimately, enhancing the robustness of scientific research. Instead of asking questions like, “does this famous individual paper replicate?”, we can begin asking questions like: -“What proportion of published empirical findings in [field X] survive a common robustness protocol?” -“How much of the variation in replicability is attributable to papers, authors, journals, methods, or subfields?” -“Are scholars persistently more or less robust across their work?” -“Can we predict which findings will prove fragile?” I may just be wrong on what I think about a one-at-a-time full body examination of scientific research. If I am, please let me know! I am also happy to chat one-on-one with anyone who is curious to learn more about the early-stage Acemoglu-specific replication project.

• 
  ericleebristol (@iamericbristol) reported 39 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🚩.

• 
  Sasha Sage (@SSage38676) reported 40 minutes ago

  Most founders confuse awareness with demand. Awareness = people have seen you. Demand = people understand why they need you now. For innovative products, demand doesn’t already exist at scale. You have to create it. Here’s the step process to create demand: 1. Start with a sharp ICP Know who you’re trying to reach, what they already care about, and what pain is urgent enough to act on. 2. Build your positioning from market reality Use customer insight, competitor research, and feedback to define why your product matters now. 3. Reframe the problem Don’t just describe your feature. Teach people to see the problem differently. 4. Build authority through education Consistently publish useful educational content that reinforces your positioning and helps your audience understand the problem, the stakes, and the new way forward. 5. Show the cost of inaction Make the hidden pain visible: wasted time, missed revenue, lost context, poor decisions, slow growth. 6. Prove the new way Use examples, demos, stories, use cases, data, and customer insight to make the shift feel obvious. 7. Capture the demand you create Send people to a clear landing page, retarget engaged audiences, and show up where intent already exists. 8. Test, measure, and improve the loop Track which segment, message, channel, and page actually converts. Then double down. Example: Zapier Most people already knew Gmail, Dropbox, and Basecamp. Almost no one was looking for an "app automation platform." That's missing demand. Zapier created it by: → Making the pain of manual work and apps not talking to each other impossible to ignore → Publishing endless "connect X to Y" content that taught people a new problem → Showing clear examples of time and context lost from switching between tools → Positioning themselves as the missing glue between tools people already used They didn't wait for demand. They built it through education and problem reframing. Don't just get seen. Make the market understand why they need you now.

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

  System design question. How would you design Dropbox file sync with conflict handling? Constraints to make it real: 1) Clients are offline for days, then reconnect over flaky networks. Upload is resumable and idempotent. 2) Same file edited on 2 devices before either syncs. You need deterministic conflict detection (hash + version vector/etag?) and a UX for duplicates. 3) Renames/moves vs edits: preserve history and avoid treating rename as delete+upload. 4) Large files (2–10GB) need chunking, dedupe, and partial re-upload (content-defined chunking vs fixed). 5) Consistency: per-file ordering vs global ordering. What is the conflict scope and how do you prevent flip-flopping? 6) Server state: metadata store vs blob store, retention for old versions, and how you garbage collect orphaned chunks 7) Security: encryption at rest, per-user keys, and how sharing folders changes trust boundaries

• 
  Danny Grinberg (@DannyGrinberg) reported 49 minutes ago

  @DropboxSupport I DMd you guys but pandadoc is looking great right now ngl its an error when you have an existing dropbox sign trial and you try to upgrade to the api version it wont let you (insane)

• 
  meshgear (@_meshgear) reported 51 minutes ago

  @Dropbox It is not working.

• 
  Karus Daedlyn *Cat Dad Era* (@CDaedlyn) reported 51 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.

• 
  Greg Ceccarelli (@gregce10) reported 52 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.

• 
  wigsandtea (@wigsandtea_) reported 52 minutes ago

  Ariana Grande reveals hackers allegedly stole 45 unreleased songs in 2023 alone, including “Fantasize”, “White Tee” and “that b*tch is mine,” in new lawsuit. She also claims they allegedly stole a photographer's Dropbox login details and hacked the phone of one of her producers: “The hackers created a Gmail account and internet domain impersonating the photographer and tricked the technician into sending Grande’s materials to them.” (via @THR)

• 
  Gabriellathebadbadfrenchmaid (@Gabriella50726) reported 52 minutes ago

  @AngryBeaverABM @DarkShadow1948 It took me a while to upload it. It was slow. But my computer has so many pages and tabs for work, so that gets slowed down by that and Dropbox cuz the files are so big

• 
  Ryan Zygar (@zygar) reported 53 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.

• 
  Mayank Vora (@aiwithmayank) reported 58 minutes ago

  In 2010, a developer decided your files should live on your computer, not Dropbox’s servers. So he built ownCloud. It gives you your own private cloud using a spare laptop, home server, or cheap VPS. His name is Frank Karlitschek. Install ownCloud on hardware you control, and you get file syncing, sharing, photo backup, calendars, and contacts through one dashboard. Your laptop and phone can access the same files just like Dropbox. The difference is where those files live. They stay on your server, under your rules. The project grew far beyond one developer’s experiment. CERN, universities, research institutions, and large organizations started using it to keep control of sensitive data. Then something unexpected happened. In 2016, Frank left the project he created and started Nextcloud with a new team. But ownCloud did not disappear. The project kept going, its source code remained public, and people continued running it on their own hardware. ownCloud has since gone through forks, an acquisition, and major rebuilds. Yet the original idea survived: Dropbox rents you space on its servers. ownCloud gives you the cloud itself.

• 
  Craig O'Shea (@craig_os) reported 59 minutes ago

  @DropboxSupport major issue with your services right now.

• 
  abheet nigam (@MaginAbheet) reported 59 minutes ago

  Dropbox rejected billions of dollars of acquisition offers only to later realise down the line that they were building a feature not product. Which other companies show a similar pattern today?

• 
  Fougars (@fougars67) reported 60 minutes ago

  @GaleTRogersJr @vaNlabs Three replies and you still have not answered the actual question: how does Leadpoet revenue accrue to alpha holders? V440 is not a permanent top-32 cartel. There is no hard cutoff and the threshold is dynamic. Dropbox is piloting Leadpoet, not “signed as a customer.” The fact that everyone sold the announcement candle is precisely the point. The business may have value, but the token has not demonstrated durable value capture. Sorry your bags are down bad, but insulting me does not fix the alphanomics.