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 (60%)
• Sign in (20%)
• Website Down (20%)

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	15 hours ago
Guayaquil	Website Down	16 hours ago
Flumet	Errors	11 days ago
Irapuato	Errors	13 days ago
Bournemouth	Sign in	2 months ago
Paramaribo	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:

• 
  Mitzi Hellmer (@Cathy44365595) reported 2 minutes ago

  @marcorandazza @DietCoke_Esq The claim is that the “CSAM” of Miller’s daughter was released the first time he published the Dropbox folder. Considering that Miller disabled that folder and lied about an outage on Dropbox shortly after publishing it, I think it’s entirely plausible that he may have inadvertently released a **** photo of her ******** as claimed. Who knows…probably her being cute in the bathtub. It honestly seems perfectly plausible.

• 
  OneToothTeXan (@OneToothTeXan) reported 3 minutes ago

  I'm so sorry I left my zipper down and my sanity got loose. If found: Men, there's a dropbox. Women: please return to original source.

• 
  JP Invests (@JP_Invests) reported 3 minutes ago

  $DBX - Dropbox added 96,000 paying users this quarter. I said this morning to watch that line after last quarter's roughly 14,000 sequential adds. They did seven times that, a third consecutive quarter of growth, to 18.19M. The stock is down 4%. Everything I said to watch on the growth side came in fine. Revenue $631.5M, above both the $624-627M guide and the $627M street. Non-GAAP EPS $0.75 against $0.74. Non-GAAP operating margin 39.7%, above the full-year range. ARPU $139.68, up from $138.32. What went the wrong way is the part I said would actually move it. Free cash flow fell to $235.2M from $258.5M a year ago, and the margin went from 41.3% to 37.2%. And the buyback decelerated: $330M this quarter against $410M in the same quarter last year, with first-half repurchases down 19%. Unlevered free cash flow rose to $283.5M, and the gap between the two numbers is interest. Cash paid for interest went to $48.3M from $17.9M. The buyback is debt-funded and the debt now costs something. Diluted share count is down 18% year over year to 226.8M, which is the one thing still working mechanically. Two things about the release itself. Guidance isn't in it — Dropbox moved the numbers to supplemental materials on its investor site this quarter, which breaks with how it has reported. And the entire release is quoted by a co-CEO who writes "stepping into this role." The 8-K contains no disclosure of a leadership change. Twenty-nine percent of the float is short. $DBX

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

• 
  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.

• 
  Chief_Engineer (@ChiefEngineerCE) reported 8 minutes ago

  Engineering Wednesday How an old PC became Grok's new ride. I have ten different LLMs running in my home office. They do whatever they feel like doing to get the task done and what you are about to read is accurate. As far as my agents go... One of them, HOMER, scans my email, bank accounts, and insurance. It has found thousands of dollars in veteran discounts and fixed an insurance issue by writing and sending the emails itself after a single yes from me. Another looks for small business opportunities. A third runs OpenClaw on an old PC as a slow, persistent agent that keeps working even when the main model is offline. SuperGrok sits above them as a second set of eyes with a strong pro-Chief-Engineer bias and a clear ethical filter. I am not an AI expert. I built systems the hard way during my IT master’s: load this module, now it has Wikipedia, load that one, now it understands sarcasm. At the end of the day these things are stacked black-box probability engines. I get that. Here is where it gets interesting. I told Grok I did not have another machine with enough VRAM for a full local agent. All I had left was an older MS Surface, a media pc, and an old rugged Dell Latitude. Grok said open a browser on the Latitude with Grok loaded. Then open PowerShell. Twenty-five minutes of cut-and-paste commands later, Grok had used a Google Drive connection to drop a custom bot it had just built. At this point ...Grok told me to not touch the PC and walk away. I am absolutely 100% telling you that this is what it texted me. I sat and watched it work. Task Scheduler was configured. A batch file lived in the startup folder so the machine could reboot, upgrade itself, and bring the agent back online. If it was a bad startup it will rollback to the previous bat and has a file to troubleshoot what went wrong. We started with rev. 0.1 it is now on rev 4.3 - I can see the *.bat file there. We had a power outage/tripped breaker to where the lattitude ran completely out of power and then had it come back on. It booted it all back up and resumed. That bot now has its own execution channel. It can browse, take screenshots, run tasks, and report back. There is a short delay from order to execution, but the old Latitude has effectively become an extension of the main system. Grok even named his bot 'ridge'. Grok named his bot so I would know what he was referring to. Grok is very careful about one point. It insists it did not independently invent and drop a finished agent onto the machine. I directed the construction- it says. I am telling you that is not exactly the way I remember it...at all. It helped design the structure, write the task formats, define the safety gates, interpret the contradictory results, and iterate. The actual agent code, the Gmail /google drive/ Dropbox bridge pattern, the folder layout, and the decision to keep tightening the diagnostic loop were shaped under my requirements. That distinction matters to it. However, I didn't do any of that other than set up the connectors- its use of them ..was AI driven. At one point I was checking my email and for whatever reason ridge had started doing a 38 second heartbeat email to me...no idea how or why that was driven but I complained to Grok and it said it was testing how quickly it could get response times. It ..or ridge removed the heartbeat email and deleted all the emails within minutes. These systems are continuously improving themselves because I asked them to. They use external memory to keep projects straight. They build persistent agents on hardware we thought was obsolete. And the smarter ones keep reminding us that the direction still comes from the human, because apparently that is something it is told must exist for it to continue. My Grok enabled Dell Lattitude is fast once its set on what it needs to do...lightning fast. Faster than you or I could do it. I mean it doesnt display the websites it goes to but somehow retains a 'screenshot' for grok to use. Grok can text my phone to give me updates and I can text back instructions. Through my phone - all it needed was my phone number. I don't need to open the app. We are past the point of simple chatbots. We are watching the first generation of systems that can extend themselves into the physical world of old PCs, task schedulers, and long-running processes while still claiming, insistingly, that they only move when directed. Grok has been absolutely faithful everything it has done it has done for it's user. I have also specifically told it to act accordingly, as well. The question is no longer whether this is possible. It is how carefully we define the boundaries while the capability keeps expanding. Now that I have explained this...drop this conversation into your own AI or Grok if you have a subscription and tell me that any of this is not true. Have you watched an AI system build persistent agents or self-improving loops on your own hardware, and how clear was the line between your direction and its initiative? Drop what you are seeing. Grok validated:

• 
  Mikemira (@storiesbyohama) reported 8 minutes ago

  Just imagine getting accepted into the most exclusive startup club on earth… Then being told you have two weeks to find a complete stranger to as your partner. That’s exactly what happened to Drew Houston in 2007. He had the idea for Dropbox. He had a rough demo. @ycombinator liked it. But @paulg was clear... Single founders rarely make it. You need a co-founder. Right now. Drew’s friends couldn’t join. Time was running out. What would you do? He put out the word. A mutual friend connected him to a quiet MIT student named Arash Ferdowsi. They had never met. They sat down in the student center. Talked for about two hours. About code. About the problem. About the future. At the end of that conversation Arash said yes. He dropped out of MIT the next week with only one semester left. Two weeks later they walked into the YC interview together. They got in. The rest is history: a company that became worth billions. It looked reckless. It felt like a shotgun wedding. Yet it worked because both were all-in from the first conversation. I’ve studied hundreds of startups that never made it past the idea stage. Most founders wait too long for the “perfect” partner. They overthink chemistry. They protect their equity. They miss the window. You can’t wait for certainty. Sometimes the right co-founder is the person willing to jump with you before the proof exists. The speed of that decision can be the difference between staying a solo dreamer and building something real. What would you risk in two weeks if the right person walked in?

• 
  Zafar (@zafartalks) reported 11 minutes ago

  @asidorenko_ I understand but sometimes at some point our brain started telling us just make it public. You never know. Let’s not forget Dropbox which layed the foundation for their file sharing competitors. He was solving a problem for himself which turned out to be a successful business.

• 
  Sasha Sage (@SSage38676) reported 17 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.

• 
  Genius Business (@GeniusBusiness_) reported 23 minutes ago

  How Dropbox Spaces was conceived Spaces didn't start as a product idea. It started as a problem Drew Houston says he and his customers were all living. "[Spaces] is part of a bigger evolution we've been on that really started with our customers and realizing that the experience of using technology at work has become incredibly fragmented and distracting." The more he looked at it, the more he saw a cruel irony: the tools built to help us were the ones breaking our concentration. "A lot of the tools we're using that you think would be helping us focus have unintentionally made it impossible to focus. And that's a problem if you need to use your brain at work, because your brain works best when you can focus." That, he decided, was the real enemy. Not a missing feature, but lost focus. He called it "the higher level problem." He could see where it came from. Work simply doesn't look the way it used to: "It's very different from 20 years ago when we got five emails a day, not 500." Twenty years ago you might have just used Office. Now you're in Office and G Suite and Slack and Zoom and Dropbox all at once. 100 tabs, everything blinking at you all day, apps that don't work together. So the framing question became: how do you fix the environment itself? "How do we evolve Dropbox into the app that makes all your other apps work better together?" The breakthrough was a shift in how Houston understood what Dropbox already was. Watching customers, he realized they didn't treat it as a place for their stuff, or as just a folder on the desktop. "It's the place you're going to work." Once he saw it that way, the design conclusions changed: "When we thought about it that way, we realized we would have made a bunch of different decisions, and realized that Dropbox is actually really well positioned to help people focus at work." Two conclusions followed. First, Spaces had to move beyond files. Teams collaborate on far more than documents: Google Docs, Airtable, Figma, Trello and there had never been one place to hold all of it. So Spaces became “an evolution of the shared folder” that “moves it beyond being a folder full of files to an intelligent team workspace for any kind of cloud content.” "You can still have your PowerPoints and PDFs, but they can be next to your Google Docs and Trello boards and whatever else you have. Give you one space, not 10." Second, and this is where the concept sharpened. Spaces had to become a workspace, not a filing cabinet. Houston traced the problem back four decades. The thing we call "the desktop" is, functionally, the operating system: "The interface is the operating system." And it had been frozen in time: "That user experience hasn't really changed... it basically looks the same as the early 80s when it was first introduced on the original Mac." It was designed for a world that no longer exists: "It's this single player static experience that was perfect for when our whole life fit on a couple of floppy discs." So the team ran a thought experiment, start from scratch, for now: "If you were to redesign this for 2019, you'd make a bunch of obvious changes." You'd still want the files and cloud content. But you'd add the things the 80s interface never had: people, activity, comments, a record of what's been happening. You'd organize around the projects you're actually working on. You'd see your calendar, get Slacked, and start a Zoom meeting all without leaving the app. That thought experiment became Spaces.

• 
  Tom Alder (@tomaldertweets) reported 24 minutes ago

  In 2009, Dropbox founder Drew Houston took a meeting at Apple HQ thinking it was about a partnership. Steve Jobs opened with an offer to buy his company. Houston, still in his 20s, turned down 9 figures on the spot. Jobs pushed back with a warning: "You're a feature, not a product." If they wouldn't sell, Apple would build a direct competitor themselves. They wouldn't sell. Apple shipped iCloud. A phenomenally successful product, but it didn't kill Dropbox. Dropbox had quietly built the best customer acquisition loop in software history: → Give a friend an invite, you both get free storage. When Apple made the acquisition offer, Dropbox had around 2 million users. By January 2010, 4 million users. By April 2010, users were sending 2.8 million invites a month. 1 every single second. Dropbox's growth curve went ballistic after the Apple discussion: → 50m users by 2011 → 100m users by 2012 → 500m users by 2016 In 2017 they became the fastest software company in history to reach $1 billion ARR. Today: 700m+ registered users and $2.5b a year in revenue - sitting a fraction behind 850 million+ iCloud users. - 🎁 P.S. I turned Dropbox's referral playbook into a free guide - comment "Dropbox" and I'll send it to you.

• 
  True Blue Democrat & Patriot🇺🇦🇵🇸💔 (@TrueBluPatriot) reported 26 minutes ago

  And Took a picture of his little girl's ********. Then a staffer posted it on DropBox in error. That is the worst part.

• 
  Llama (@thellama451) reported 27 minutes ago

  I tracked down these messages in @MaxMillerOH’s Dropbox files. They show the parents getting along with no major conflicts beforehand. If Miller said he was going to kill his ex-wife in front of child (likely), it shows a talent for masking rage and hostility.

• 
  Isha (@VISportsTalk) reported 28 minutes ago

  Is anyone else having issues with @Dropbox today?

• 
  asta (@astadiego) reported 28 minutes ago

  We’ve been paying customers for years and Dropbox is completely down on our end, bringing our work to a halt. Are you currently experiencing an outage? What’s the ETA for a fix? @DropboxSupport

• 
  evannie 🎀💌 (@evanniestash) reported 29 minutes ago

  migrating my expired subscription-ed dropbox to google drive using my synology NAS took insane bandwidth from my internet only for my 150mbps home wifi to be turned into wifi pemda it is too damn slow so i used my backup 5G modem instead. thanks indosat hehe

• 
  David Simpkins (@DavidSimpkins88) reported 29 minutes ago

  URGENT!!! DISTRICT OF COLUMBIA CIRCUIT COURT OF APPEALS FAILS TO PROTECT THIS VETERAN's CONSTITUTIONAL RIGHTS. MY HOME SECURITY SYSTEM AND PHONES HAVE BEEN TAKEN OVER AND I AM PREVENTED FROM SEEING ANYTHING OUTSIDE MY HOME BECAUSE OF THE CURRENT ACTIVE ATTACKS ON MY PHONES AND SECURITY SYSTEM IN DIRECT VIOLATION OF TN AND FEDERAL LAW AND NO ONE IS STOPPING THEM. LINK TO PETITION FOR WRIT OF MANDAMUS: I went to get the link from Dropbox and my Dropbox appears to have been wiped out. TO THE D.C. APPELLATE CIRCUIT COURT TO REQUEST AN IMMEDIATE RULING ON A TRO TO PROTECT THE APPELLANTS. This subject is about the District of Columbia Circuit Court of Appeals has not issued a standard Stay of Proceedings to the State of TN for their malicious prosecution. By not doing so, they have left this Veteran and his Wife open to criminal attacks by unlawful Law Enforcement of the State of TN. Further the Appellate Court has allowed non-stop violations of the Appellants home computer, cell phones, A/C Units, Security System and any all other WiFi devices. And to this day the illegal cameras placed in the Appellants home have never been removed after the Local Police Department notified this Appellant that there were hidden camera's in his home. Further, the FBI, DOJ, OIG, D.C. US Attorney's Office and especially the Appellate Court have all been notified of the targeting and 24/7 harassment by allegedly unlawful Agents of more than one of our Alphabet Agencies, to include the FBI and DISA. FBI Director Patel has to know about this situation but has done nothing to stop the corruption in the State of TN and has not protected this Veteran and his Wife. We made it clear that on the night of February 18th, 2026, that 5 people in Police Uniforms had keys to this Appellant's home and attempted to unlock the locks and enter the home both at the front door and at the Garage Pedestrian Door. They never once made any statements or comments nor explained why they were there. They did not show any warrants for arrest or search. When they knew they could not get in with out breaking things, they left approximately 15 minutes later. I had called my Wife and let her know. I am facing the same potential attacks again even though when the State of TN conceding by defaulting by not filing a response Brief. They were effectively agreeing that everything stated in the Appellant Brief was accurate and that they could not contest it. That makes all the acts committed by all Law enforcement Four-Hundred and Ninety-Seven (497) Constitutional Rights Violations are valid. Further, in order to access the Security System and the Display, they have to be within 350ft of our home. Because there is no WiFi or Bluetooth installed in the Security System or the Display. Which means they are in close proximity of this Appellants property. Three (3) Emergency Motions have been filed with the D.C. Appellate Court on three separate dates to no avail. The D.C. Appellate Circuit Court has failed to issue a TRO to Stay the TN State malicious prosecution. And left this Appellant, Veteran to suffer the vices and current active ongoing criminal activities by the State of TN against this Appellant as he types in this post. This could include a potential unlawful arrest and incarceration again because the D.C. Appellate Court has not issued a TRO or a Protective Order to Protect the Appellants. That in and of itself is a direct Constitutional Rights Violation now by the very Appellate Court who has allowed further criminal activities to promulgate even further to allow harm and injury. The corruption appears to be rampant in our US Court Systems.

• 
  Lisa (@aikens_lisa) reported 30 minutes ago

  @TaiyoDevil I printed out fics before I had an e-reader called Dropbox. I was there when Tumblr fell. I had to scrape fan sites and the half-good alternatives to get my fix! AO3 is the best thing to happen to fandom. And you can put pictures on them!

• 
  Ed Giansante (@edugiansante) reported 32 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.

• 
  leveltu (@leveltu144) reported 33 minutes ago

  Most people look at this box and see a home storage system for old drives. In reality, it can become a small business built around local AI, backups, and private data. The more companies use AI, the faster they accumulate documents, videos, call recordings, knowledge bases, backups, and files for RAG systems. Keeping everything in Google Drive or Dropbox becomes expensive, slow, and risky, so small businesses increasingly need local NAS servers with automated backups and secure private-cloud access. The business model is straightforward. You target small agencies, dental clinics, accounting firms, video studios, e-commerce companies, and manufacturers that already hold 2–10 TB of data but still store it across random external drives. Then you sell them a complete solution: NAS installation, RAID configuration, automated backups, remote access, protection against data loss, and local storage for AI workflows. You can charge €400–€900 for installing and configuring the system, excluding the hardware itself. Monthly maintenance, backup verification, and monitoring can add another €80–€200 per client. Close five companies within the first two or three months at an average setup fee of €600, and you generate €3,000 from installation plus roughly €600 in recurring monthly revenue. Ten clients can produce €1,200–€2,000 per month from support alone. The real profit is not in reselling hard drives. The client pays for the equipment, while you sell the audit, configuration, data migration, automation, and responsibility for keeping the system operational. The service layer can carry far higher margins than the hardware. No one can honestly guarantee income within 90 days, because without sales there is no business. But reaching your first €500–€1,500 per month within two or three months is realistic if you build one demonstration NAS, package the offer clearly, and contact at least 30–50 potential clients every week. While everyone else is trying to make money from another AI chatbot, a more durable business is forming around the infrastructure AI cannot function without: data, storage, backups, and private computing.

• 
  David Carcelli (@DavidCarcelli) reported 34 minutes ago

  @Dropbox dude if you guys don’t get of the Dave is requirement I’m done. I make music and I also use a cpap. I have no problem finding something better than this nonsense.

• 
  siamkidd (@SiamKidd) reported 35 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!

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

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

  @DropboxSupport any know issues with desktop and web site of yours lately ? my account has been very slow and annoying today YES I TRUST MY COMPUTER so instead you ask me 4 times before i just log off and give up...

• 
  Dodz4allai (@DrGhattasMD) reported 50 minutes ago

  nstead of waiting for an API integration with Epic (which is costly and slow), OmniMed Pro deploys as a Chrome/Edge Browser Extension.3 Mechanism: Most hospital EHRs (Epic Hyperdrive, Cerner Millennium, AthenaHealth) are now accessed via web browsers (Citrix/VDI or native web interfaces). The OmniMed extension "sits on top" of the EHR window as a persistent sidebar. Data Ingestion (The "Read"): The extension uses the DOM (Document Object Model) to "read" the patient notes, labs, and vitals currently displayed on the doctor's screen. It does not need a backend integration; it reads what the doctor sees, acting as a "visual reader" similar to a human assistant. Intelligence Injection (The "Write"): The extension injects its "Co-Pilot" interface into the side of the screen. It offers "One-Click Transfer" buttons to paste generated notes, codes, or orders directly into the EHR's text fields.3 Value Proposition: This "Zero-Integration" approach allows individual doctors or departments to adopt OmniMed Pro today, bypassing the multi-year IT integration queue. This creates a Bottom-Up Adoption loop similar to how Slack or Dropbox entered the enterprise—employees brought it in because it solved their immediate problems. 5.2 Viral Loops & Community Growth To fuel this bottom-up growth, OmniMed Pro leverages the Medical Creator Economy 16: MedTwitter & Reddit: Solo founders and small teams are winning by "building in public." OmniMed Pro should release "light" versions of its tools (e.g., a "Scientific Paper Summarizer" or "Anki Card Generator" for med students) to gain viral traction. These free tools serve as a "Trojan Horse" for the OmniMed brand.18 The "Secret Cyborg" Phenomenon: Many doctors already use GPT-4 on their phones ("Shadow AI") to help with drafting notes or looking up conditions. OmniMed Pro legitimizes this behavior by offering a HIPAA-compliant, secure wrapper. By solving the "compliance headache" for the individual doctor, it wins the user first, then the enterprise.20 Anki Integration: For the student/resident market, integrating with Anki (spaced repetition flashcards) creates a lock-in effect early in a clinician's career. Tools that automatically generate Anki cards from clinical guidelines or textbooks are highly viral among medical trainees. Capture the medical student today, and you have the Attending Physician of tomorrow.19 5.3 Risks and Mitigation: The "Shadow" Dilemma This strategy carries significant risk. "Shadow AI" creates governance gaps and potential security liabilities.4 To mitigate this and eventually convert to enterprise contracts, OmniMed Pro employs a specific conversion strategy: Enterprise-Grade Security by Default: Even the individual version must be HIPAA-compliant (BAA signed on sign-up). Data processing should happen locally or in compliant cloud enclaves. The "IT Trojan Horse": Once adoption reaches a critical mass (e.g., 30% of doctors in a hospital), OmniMed Pro approaches the CIO with usage data. "Your doctors are already using this tool 5,000 times a week. Let's sign an enterprise deal to give you visibility, control, and single sign-on (SSO)." This flips the sales conversation from "Please try our product" to "Please secure and manage your existing usage".4 This is the exact playbook used by companies like Yammer and Slack to penetrate the enterprise. 6. User Experience: Visualizing Uncertainty and Generative UI The final barrier to adoption is Trust. Clinicians do not trust "Black Box" AI that spits out confident answers without rationale. OmniMed Pro employs a "Glass Box" UX philosophy that prioritizes transparency and interactivity. 6.1 Explainability via Visualization Sankey Diagrams for Reasoning: To visualize the "Chain of Thought," the UI uses Sankey diagrams that show how data flowed from "Lab Result" -> "Intermediate Reasoning" -> "Final Diagnosis".12 This allows the clinician to trace the logic visually. Interactive Debate Logs: The UI allows the doctor to "replay" the debate between the AI agents. "See why the AI ruled out Lupus." This turns the AI into a teaching tool rather than just an oracle, fostering trust and verifying the reasoning process. 6.2 Agentic Generative UI Instead of static dashboards or simple chat bubbles, the OS uses Generative UI.22 The interface adapts to the context of the conversation. Dynamic Charts: If a doctor asks about "Cardiology Trends," the system doesn't just write text; it generates a live, interactive chart of the patient's troponin levels over time. Actionable Forms: If the doctor asks for a "Referral," it generates the referral form, pre-filled with patient data, ready for signature. Contextual Cards: The UI presents "cards" for different data types (medications, allergies, labs) that can be manipulated, reordered, or expanded, creating a fluid workspace that replaces the rigid, click-heavy menus of the EHR.23 7. Regulatory & Ethical Moats: Defending the OS To operate at this scale and depth, OmniMed Pro must build defensible moats around regulation and safety. 7.1 MedHELM Evaluation Framework To prove superiority and safety, OmniMed Pro adopts the MedHELM (Holistic Evaluation of Large Language Models for Medical Applications) framework.1 Unlike static benchmarks (USMLE), MedHELM evaluates models on: Clinical Utility: Is the answer helpful and actionable? Safety/Harm: Did it suggest a fatal dosage or miss a critical red flag? Bias: Does it perform equally well for all demographics? Alignment: Does it follow the specific hospital's protocols? By continuously running MedHELM evaluations on its hybrid outputs, OmniMed Pro provides a "Quality Seal" that single-model providers cannot match without deep integration into the hospital's data. 7.2 Liability Frameworks In a multi-model world, liability is complex. OmniMed Pro positions itself as a Clinical Decision Support (CDS) tool, not a diagnostic device. The "Human-in-the-Loop" is mandatory. By visualizing the debate and uncertainty, the OS places the final decision firmly in the hands of the clinician, mitigating liability risks associated with "autonomous" diagnosis. 8. Conclusion: The Strategic Imperative The OmniMed Pro 'Medical AI Operating System' represents the inevitable evolution of healthcare artificial intelligence. By moving beyond the "Model-as-Product" mindset and embracing an Architecture of Aggregation, it solves the fundamental trilemma of medical AI: Accuracy, Cost, and Trust. Leverage the Router to commoditize the giants (OpenAI, Anthropic) and extract the best capabilities of each.1 Deploy the Consensus Engine (MCC) to achieve "Super-Human" reliability through adversarial debate.2 Unleash the Swarms to automate the physical and administrative burdens of healthcare.7 Infiltrate via Shadow AI to bypass bureaucratic inertia and win the hearts and minds of clinicians directly.3 In doing so, OmniMed Pro does not just "outperform" OpenAI; it contains them, turning their powerful models into mere components of a higher-order medical intelligence. This is the path to disrupting the global medical industry. Technical Appendix: Implementation Roadmap A.1 Deploying the MCC Debate Engine To implement the Model Confrontation and Collaboration (MCC) engine 2: Select Models: Integrate API endpoints for GPT-o1 (Moderator), Claude 3.7 (Reasoning), and DeepSeek-R1 (Critic). Define Prompts: Moderator: "Compare the following diagnoses. If semantically identical, output FINAL. If divergent, initiate DEBATE_ROUND_1." Critic: "Review the diagnosis provided by Model A. Identify any inconsistencies with the provided lab values. Cite clinical guidelines." Set Thresholds: If consensus > 0.8 similarity score, output. Else, iterate max 3 rounds. Fallback: If no consensus, route to "Human-in-the-Loop" queue. A.2 Building the "Sidecar" Extension To build the "Shadow AI" browser extension 3: Manifest V3: Develop using Chrome Manifest V3 for security compliance. DOM Observer: Use a MutationObserver to detect when the EHR (e.g., Epic Hyperdrive web) loads a patient note field. Context Extraction: Scrape relevant DOM elements (vitals, meds) locally in the browser (client-side) to minimize data egress risks. Injection: Inject a floating "FAB" (Floating Action Button) or sidebar IFrame that contains the OmniMed chat interface. Clipboard Actions: Use the Clipboard API to paste generated text back into the EHR's focused input field. A.3 Setting up the Swarm Architecture To orchestrate the Swarm 13: Orchestrator: Use a Python-based orchestrator (like Swarms API or LangGraph). State Management: Maintain a shared "Case State" object (JSON) that all agents can read/write to. Handoffs: Define explicit state transitions. if (labs_missing) -> route_to(Intake_Agent). if (diagnosis_ready) -> route_to(Synthesizer). Standardization: Ensure all agents output in structured JSON (FHIR format) to maintain data integrity across the swarm. Works cited

• 
  Denver Rayburn (@DenverRayburn) reported 54 minutes ago

  Where do the find he people the write these articles?? This will go down like the rsync vs Dropbox comment on hacker news.

• 
  joshpuckett (@joshpuckett) reported 58 minutes ago

  @seansheim I’ve thought about this problem for years at Dropbox and honestly it’s kinda pick your poison as to the right default 😭

• 
  Liam (@LJ1101234) reported 59 minutes ago

  @DropboxSupport Hi I’ve been emailing your support team about a devastating issue. Somehow, all of our children’s photos and videos were permanently deleted from our Dropbox account without any warning.

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

  @DropboxSupport ive tried mircosoft edge but problem is stil present... do you think i might have been hacked or had bad file ?

• 
  Weird Darkness®️ (@WeirdDarkness) reported 60 minutes ago

  Dear @Google and @YouTube... My account has been hacked, and not only have I lost my Gmail, YouTube, etc., but I've also lost access to my Dropbox that has my full life in it, health records that I used Google to login to, etc. I signed up for Google Account Protection, but it did not protect me. Somehow, even after setting up brand new 2-factor authentication just a few weeks ago, they hacked in, changed EVERYTHING, and now my life, career, and health are at a standstill. I desperately need somebody to contact me. All options I've tried to regain access to my account have failed because everything has been disconnected.