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:

• 
  Grant B. (@GrantB423) reported 5 minutes ago

  yo Sam, anyway you could dm the Dropbox link for your “ghosts’n’stuff” remix? it was taken down off every single platform @Jauzofficial

• 
  numaan (@numaan27) reported 7 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)

• 
  EchoMind (@ai0echomind) reported 7 minutes ago

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

• 
  Ayaan 🐧 (@twtayaan) reported 7 minutes ago

  Steve Jobs told Drew Houston that Dropbox was a feature, not a product. Dropbox is now worth $8 billion. In 2007 Drew Houston was a 24 year old MIT student who kept forgetting his USB drive. So he built Dropbox. Within a year Steve Jobs called him into Apple HQ. Apple wanted to buy Dropbox and shut it down. Houston said no. Jobs told him directly that Dropbox was a feature, not a product, and that Apple would build it themselves. Apple launched iCloud in 2011 specifically to kill Dropbox. It did not work. Dropbox crossed 100 million users in 2012. Then 200 million. Then 500 million. Apple tried again. iCloud Drive in 2014. Same result. Then the enterprise market shifted. Slack, Notion and Google Drive carved up Dropbox's user base from every direction. Revenue growth slowed. The stock dropped 50% from its IPO price. But Dropbox never died. Today 700 million people have used it. 17 million paying customers. $8 billion valuation. Still independent. Still running. Steve Jobs built a trillion dollar company. He called Dropbox a feature. The feature outlasted him and two attempts by Apple to replace it. Drew Houston never forgot his USB drive again.

• 
  Rituraj (@RituWithAI) reported 11 minutes ago

  🚨 Someone built a tool that checks if your email is registered on 120+ sites — without the sites ever knowing someone checked. No notifications sent. No login attempts logged. No alerts triggered. Silent. Invisible. Complete. It's called Holehe. 16,800 GitHub stars. And the technique behind it is what makes it different from every other email OSINT tool. Here's how most email checkers work — and why they fail. Standard approach: try to log in with the email and a fake password. If the error says "wrong password" — the account exists. If it says "account not found" — it doesn't. Problem: every login attempt gets logged. Every failed attempt triggers security alerts on accounts with 2FA. Some platforms lock accounts after repeated failed attempts. The target knows someone was checking. Holehe never attempts a login. Instead it uses the "forgot password" flow — the password reset mechanism that every platform exposes publicly. When you enter an email on a forgot password page, the platform has to check whether that email exists in its database. It tells you: "we sent a reset link" or "no account found." Holehe reads that response. Gets the answer. Never touches the login flow. Never triggers a security alert. Never logs an access attempt against the account. The platform confirms whether the email exists. The account owner never finds out anyone asked. Here's what 120+ platforms looks like in practice. Social media: Twitter, Instagram, Facebook, TikTok, Pinterest, Tumblr, Reddit. Professional: LinkedIn, GitHub, Freelancer, Fiverr. Dating: Tinder, Bumble, OkCupid, Badoo, Happn. Entertainment: Spotify, Netflix, Twitch, Steam, Epic Games, Deezer. Shopping: Amazon, eBay, Etsy, Zalando, AliExpress. Services: Airbnb, Uber, PayPal, Dropbox, Adobe. And 90+ more. Every registration checked silently. Here's the use case that makes people share this. Run your own email address. See every platform that comes back positive. Then run an email address you gave to a company that claimed they'd never share it. See if it's registered on data broker sites and marketing platforms you never signed up for. See where your email has been sold or leaked to. Here's what investigators actually use it for. Journalists verifying whether a source's claimed identity matches their digital footprint. Security researchers auditing their own exposure before a public disclosure. HR teams verifying whether candidate profiles match claimed backgrounds. And the obvious: anyone who needs to know whether a specific email address belongs to a real active person — without alerting that person. Here's the wildest part. It runs async — all 120+ platforms checked simultaneously. Results in seconds. And it exports clean JSON or CSV for integration into larger OSINT pipelines. Pair it with Blackbird (which takes the confirmed email and finds linked profiles), Sherlock (which takes usernames found in those profiles and searches 400+ platforms), and Maigret (which builds the full dossier) — and you have a complete four-tool OSINT pipeline from a single email address. One command to instal. Run it on your own email first. 16.8K GitHub stars. 1.7K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  FarhanX_AI (@FarhanBuildsAI) reported 11 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.

• 
  Ihtesham Ali (@ihtesham2005) reported 14 minutes ago

  A guy built a free version of Dropbox in 2010. His name is Frank Karlitschek. The project is called ownCloud. He wasn't trying to build a company. He was trying to fix one thing: your files should live on hardware you control, not on a corporation's server. Here's what it actually does. You install it on your own machine, a spare laptop, a cheap VPS, whatever you've got lying around. It gives you file sync, photo backup, calendar, and contacts inside one dashboard. Same core idea as Dropbox, owned by you instead. CERN runs on it. The European Science Cloud runs on it. Entire universities host their file systems on it instead of paying Google or Microsoft by the seat. In 2016, Karlitschek walked away from the project he built and started Nextcloud, chasing the same idea with a new team. ownCloud kept going without him. It's still free, still self hosted, and still running inside labs and universities that never wanted their data anywhere near a company's servers.

• 
  Abhi • AMZBoosted.com (@AbhiChauddhari) reported 14 minutes ago

  Everyone downloads Seller Central reports manually. Every. Single. Day. The problem isn’t downloading reports. It’s remembering to do it before you need the data. AMZBoosted schedules report downloads automatically and sends them wherever you want. Google Sheets. Dropbox. Telegram.

• 
  IT Guy (@T3chFalcon) reported 15 minutes ago

  The code itself is just a pattern that encodes a URL. it's not dangerous. what it points to might be. The attack is called: Quishing. QR code phishing. It works so well because can't see where a QR code goes before you scan it. A phishing link in an email is visible, people have been trained to hover before clicking. A QR code gives you nothing to hover over. you scan and you're already there. And security tools are mostly blind to it. email filters scan text and URLs but a QR code is an image. 12% of all phishing attacks now use QR codes specifically because they bypass email security gateways that weren't built to read images. In 2026 — Stickers are being placed over legitimate QR codes at parking meters, EV charging stations, and restaurants; your payment goes to the attacker. — QR codes in emails leading to fake Microsoft 365 or bank login pages. 83% of malicious Microsoft 365 documents now contain QR codes instead of links. — multi-stage attacks: QR code leads to a Dropbox or Notion link that looks legitimate, which then loads the phishing page. — fake address bars on mobile called Browser-in-the-Browser. The padlock shows, the URL also looks right but it's a fake overlay on a small screen you can't scrutinize. QR code phishing attacks increased fivefold in 2025 alone. The FBI also issued a public advisory.

• 
  Dr Prosper The Philosopher (@ProsperThePhilo) reported 15 minutes ago

  Stop Storing Your Medical School Files on Your Phone: If you're a medical student having problems with where to store your lecture slides because your phone storage keeps getting full... If you're always struggling to find files on your phone... If you've ever changed your phone and lost access to your lecture slides... Then I want to let you know that this isn't really a phone problem. It's simply because you're using the wrong storage system. As a medical student, you're not supposed to be storing your important academic files permanently on your phone. Yes. Have you heard of something called cloud storage? Cloud storage simply means storing your important files on secure servers online instead of inside your phone. Think about it. Your phone has limited storage. Depending on the model you're using, it may have 64 GB, 128 GB or 256 GB of storage. But over several years of medical school, you'll accumulate thousands of lecture slides, hundreds of PDFs, anatomy atlases, textbooks, videos, practical manuals, charts, flashcards and past questions. Eventually, your phone becomes crowded. The smarter approach is to let your phone become a temporary device—not your permanent library. For example... Google gives every Google account 15 GB of free cloud storage (shared across Google Drive, Gmail and Google Photos). If you're using an Android phone, chances are you already have a Google account. That means you already have free cloud storage waiting for you. If you have a Microsoft account, OneDrive gives you 5 GB of free cloud storage. If you use an iPhone, iCloud gives you 5 GB of free storage. There are also services like Dropbox and MEGA that offer free cloud storage as well. These services exist for a reason. Use them. If you have textbooks, don't store them permanently in your phone's internal storage. Instead... Open Google Drive. Create one proper Google account dedicated to medical school. Inside that account, create folders. For example: - Anatomy - Physiology - Biochemistry - Histology - Embryology - Pharmacology - Pathology - Microbiology - Surgery - Medicine Now open your Anatomy folder. Inside it, create another folder called Gross Anatomy. Inside Gross Anatomy, create folders like: - Lecture Slides - Textbooks - Past Questions - Clinical Correlations - Charts - Practical Manuals Now begin uploading. Upload. Upload. Upload. Stick to one Google Drive account throughout your entire medical school. You'll be surprised. Five or six years later, you'll look back and realize you've built an entire medical library. Everything you've ever studied... Every lecture slide... Every textbook... Every practical manual... Every chart... Every past question... Waiting for you in one organized place. Another thing. Learn to use Google Photos. All those anatomy diagrams... Charts... Clinical pictures... Embryology illustrations... Practical photographs... Store them inside Google Photos instead of leaving them on your phone. As long as you know your email and password, you can access them from anywhere in the world. Your phone. Another phone. A tablet. A laptop. Even a computer in a cyber café. If your phone gets stolen today... Nothing important is lost. Because your library isn't inside your phone. It's online. There are paid cloud services that provide even larger storage capacities, but honestly, the free options are enough for most students starting out. Now here's a habit I think every student should build. Whenever you download something important... Don't leave it sitting on your phone. Instead: Download it. Upload it to your cloud storage. Delete it from your phone. Download. Upload. Delete. Repeat. Your phone remains light. Your files remain safe. Your library keeps growing.

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

• 
  Flandermaxx (@Flandermaxx) reported 17 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 vojtech is 32, prague vinohrady flat above a pivnice, ex-JetBrains backend eng, sources ORICO metabox HS200 pro enclosures from a shenzhen aliexpress-parallel channel at $180 per unit plus 2x WD 30TB HDD refurbs at $410 each ORICO metabox HS200 pro (intel N100 · 8GB DDR4 · 2x 30TB WD in RAID 1 = 30TB usable) · ubuntu server 24.04 · minio S3-compat · qwen 2.5 VL 7B for local RAG over the user's PDFs and figma exports pause at 0:02 on the HDD sliding in, that is a $1,000 mini-NAS holding 30TB of encrypted client data that dropbox business bills €2,400 a year for the same tier 84 EU freelance designers pay him €78 a month each for a shipped pre-configured NAS + qwen RAG endpoint, €6,552 = $7,200 MRR at 71% margin $1,000 BOM per unit, €12 monthly prague power for the burn-in bench, first 20 units flipped covered his tooling and packaging, no dropbox no google drive business while ORICO still white-labels the metabox before EU distributors mark it up 3x, follow and bookmark

• 
  Hugo Bowne-Anderson (@hugobowne) reported 19 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!)

• 
  Karishma Bhardwaj (@bkarishma360) reported 23 minutes ago

  @shahzamannn_ Your SaaS idea doesn’t need to be complicated. Stripe moves money. Postman sends API requests. Notion organizes information. Dropbox syncs files. The lesson? Simple problem + huge market + great execution = massive company. Stop asking, “Is my idea too simple?” Start asking, “How many people have this problem?”

• 
  pharmabro (@pharmabro0782) reported 24 minutes ago

  @Ronalfa @draparente @liambai21 a “rock engineer” at Dropbox is an engineer, an RA doesn’t have the degree (undergrad/ masters at best). Now this is different at large pharma where RAs can stay for much, much longer time with structured career development (slow but existent).