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 (75%)
• Website Down (25%)

Live Outage Map

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

City	Problem Type	Report Time
Nottingham	Errors	23 days ago
Guayaquil	Website Down	23 days ago
Flumet	Errors	1 month ago
Irapuato	Errors	1 month ago
Bournemouth	Sign in	3 months ago
Paramaribo	Errors	4 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:

• 
  Farmer henkenson (@FarmerJenkenson) reported 2 minutes ago

  @colemickens @Dropbox So if you had a lenovo account with a soecific emial, and a dropbox account had the same email, you could just login with lenovo and it would assume you own the dropbox account?? Insane

• 
  Jameson Lopp (@lopp) reported 5 minutes ago

  One reason I suspect the Dropbox breach may be massive is because I didn't get a login email notification when my account was accessed. Turns out, unlike every other login notification I've received from them, it went to spam. Likely due to a large uptick in their send volume...

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

  System design question. How would you design Dropbox-style file sync with conflict handling? Constraints that make it interesting: 1) Multi-device edits while offline, then reconnect hours later 2) Large files (GBs), but common case is small diffs; do you chunk + hash + resumable upload? 3) At-least-once events from clients; duplicates and retries are normal 4) Need per-file causality: version vectors? server-assigned sequence? something else? 5) Conflicts: rename vs edit, delete vs edit, concurrent edits on same bytes; what gets auto-merged vs forked as conflicted copy? 6) Metadata vs content planes: directory tree ops must be atomic-ish, blobs can lag 7) End-to-end integrity: how do you detect corruption and avoid re-upload storms? 8) Fast convergence: target <5s to see changes on another device, but mobile battery + bandwidth are limited

• 
  Rei (@ReiHerrera) reported 19 minutes ago

  @owldreig @porterrobinson @madeon The problem with them both is they love gatekeeping the rare song behind a bad quality sounding medium so you cannot use it for clean for dj sets. For example Celine,worlds live,shepherdess,etc. at least we had hollowheart on wav and shepherdess wav was on porter’s Dropbox leak🫩

• 
  Luke Elin (@LukeElin) reported 21 minutes ago

  👤Shadow Adoption The pattern: Staff route around the sanctioned tool, and the organisation finds out afterwards. I watched this with unauthorised modems. Then with USB drives. Then with Dropbox. Then with entire SaaS platforms procured on a personal credit card and expensed as “software.” Now it is AI the same movie, new cast, better production values. The reason is always identical and always reasonable: the sanctioned tool is slower than the job requires. Shadow adoption is not an indiscipline problem. 👊 It is a feedback signal about the official tooling, arriving through the wrong channel. The tell: Compare the usage figures for your officially sanctioned tool against what your helpdesk volume implies people are actually doing. The gap is your shadow estate. FR FR

• 
  CHItrader (@CHItrader) reported 22 minutes ago

  DBX LEAKS 5,000 ACCOUNTS ON A SIDE DOOR $DBX just told about 5,000 users their boxes got hit Aug 4-21 through a leftover $LNVGY login. Email was enough. No 2FA on the wrecked accounts. 🔹 Files touched on fewer than a third of them, call it ~1,500 🔹 Dropbox cut the Lenovo link and now wants a real password 🔹 After-hours ate the stock when Bloomberg printed it Cloud storage with a guest list and no bouncer. Cool product.

• 
  David Carcelli (@DavidCarcelli) reported 23 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.

• 
  Christopher Bailey (@LexBaileyAI) reported 24 minutes ago

  @TetraspaceWest At Fitbit we hired a half dozen people from Jawbone who brought everything cleverly hidden in Dropbox. They got prosecuted. Decade later, companies kaput but Fable found it, processed it and now it’s intermixed in various *** repos and Huggingface. Is nVidia now in trouble?

• 
  David Simpkins (@DavidSimpkins88) reported 26 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.

• 
  Mansi 👩‍💻 (@MansiCodez) reported 28 minutes ago

  Solution of yesterday’s question: Design Google Photos: the part after the boxes “Hash it and put it in S3” fails the interview. Two phones compress the same sunset differently. Same photo. Two hashes. Two rows. You just built a worse Dropbox. The system needs three IDs, not one. client_upload_id — generated on the device before the first byte moves content_hash — hash of the exact bytes you received asset_id — the thing the user sees in the library Uploads are sessions. Library entries are assets. Blobs are renditions. If you collapse those into one key, retries, edits, and shared albums all collide. 1. Retries must be idempotent on the client, not on the filename Phone goes offline mid-flight with 612 shots, 40 already half-uploaded. Each photo gets a client_upload_id the moment it enters the queue. Chunks are uploaded against that ID. Commit is PUT /uploads/{id}/complete. Same ID + same bytes → same session. Server returns the existing asset. Late packet after commit is a no-op. Filename + timestamp is not an ID. Camera roll and AirDrop will mint two. 2. Exact dupes are content-addressed. Near-dupes are reconciled. After commit: look up sha256(bytes) if it already exists for that user (or the shared album’s owner set), attach the new upload to the existing asset_id do not create a second photo The 28 shared “Goa 2026” shots that are almost-but-not-quite the library copies will miss on sha256. That is expected. Run a cheap perceptual hash (pHash / dHash) + capture time + camera model from EXIF. If distance is tiny and captured within a few seconds, mark as near_duplicate_of and do not show two tiles. Keep both blobs if you must; hide one in the UI. Two devices, two compressions, one photo in the grid. 3. The library is a set of assets + tombstones. Not last-write-wins. Delete in Delhi must beat a pending upload in Mumbai. Every mutation carries: asset_id op: upsert | delete | restore actor_id (device or user) logical_ts (per-actor Lamport or hybrid logical clock) A deleted asset gets a tombstone that outlives the pending queue. When the flight-mode phone finally flushes those 40 half-uploads, the server sees: upload commit for an asset that already has a newer delete → commit the blob if you want, do not resurrect the tile. Refresh in Mumbai cannot show a photo Delhi just deleted, because the change feed is “tombstone wins over delayed create,” not “whoever wrote last.” 4. Shared albums are references, not copies Partner adds 28 photos to Goa 2026. The album stores {asset_id, added_by, added_ts} — not a second blob, not a second library row. Adds and removes are a small CRDT: add(asset, actor, ts) remove(asset, actor, ts) Two devices adding the same asset = one membership row. Phone sync finishing a second later cannot wipe the partner’s 28 photos, because there is no “replace the whole album document.” Last-write-wins on the album JSON is how photos vanish. 5. An edit is a new rendition, not a new photo and not an overwrite User crops + filters while the original is still processing. Rules: original blob is immutable edit creates rendition_id with parent_asset_id library still shows one asset “current view” pointer moves to the latest rendition history is a list of renditions / edit ops, not 12 full-resolution copies by default If you overwrite the original, face clustering and search lose their source. If you mint a new asset, the user now has original + edit as two photos. Both are wrong. Storage stays sane because you store: original (once) derived thumbs / display sizes lazily, keyed by asset_id + transform not every intermediate crop as a first-class photo 6. Upload path and ML path must not share a lock “Beach sunset with Priya” in minutes, not overnight, also not on the upload critical path. Commit path only: durable bytes asset row appear in library + album enqueue jobs Workers (thumbs, embeddings, face cluster, labels) are async. Search index is eventually consistent. The UI can show the photo immediately with “processing” on faces. If clustering blocks upload, you built a spinner, not Photos. Face identity hangs off asset_id, so an edit does not orphan Priya. The new rendition inherits the parent’s cluster and gets re-checked, not reset. 7. Sync is a checkpoint + change feed, not “download the library” Each device stores last_applied_ts. Server gives a stream: new assets, new renditions, album membership, tombstones. That is how 62,000 existing photos plus 612 offline shots plus 28 shared adds converge without a full rescan, and why a deleted photo does not climb out of another device’s queue. The one-line design Client-generated upload IDs stop retries from cloning. Content hashes stop exact clones. Perceptual reconcile stops “same sunset, different JPEG.” Tombstones stop resurrection. Album CRDTs stop last-write-wins from deleting the partner’s night. Edits are renditions under one asset. ML is a consumer of commit, never part of it. Boxes for S3, CDN, Kafka, Redis are table stakes. This is the part that decides whether you designed Google Photos or a photo-shaped file dump.

• 
  True Become False (@trubecomefalse) reported 30 minutes ago

  @imbabybrooklyn HN had a terrible track record. They were anyi bitcoin 1 month after it launched. Same with Dropbox, discord and a few others off the top of my head.

• 
  OneToothTeXan (@OneToothTeXan) reported 32 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.

• 
  Bruno Marsino (@BrunoMarsino) reported 33 minutes ago

  Company for AI age: - Information should flow flat - Can’t wait to have all information to make decisions - Speed and excelente in execution is crucial - You should get as much info as possible during the constraint of time given by yourself - How do we prepare a company to be totally eligible for AI? Not only text info but images - Service of the future is not about giving agents to corps to solve problems but offering the solution/service driven by AI. - Even if all information is on the web, multiple file structures, owners, formats and file storage systems (dropbox, drive, box) add friction to information and decision making

• 
  Eyal Benishti (@eyalbd1) reported 33 minutes ago

  @BleepinComputer Password and 2FA were both fine here. Neither was in the path, because Dropbox trusted Lenovo's word that the attacker owned the email address. Every federated login is a bet that somebody else's email verification is not broken.

• 
  Phillip Shoemaker (@pbsIdentity) reported 34 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  Tomorrow’s James (@james__art) reported 36 minutes ago

  @wholemars A designated Amazon Dropbox could solve this problem. The drone could detect a Dropbox.

• 
  Alvin (@Alvin1492840) reported 37 minutes ago

  Kill the startup apps that have been draining your battery since day one. She opened System Settings → General → Login Items & Extensions. 14 apps were set to launch automatically every time he turned on his Mac. Spotify. Zoom. Adobe Creative Cloud. Google Drive. Microsoft Teams. OneDrive. Dropbox. A VPN he used once. A screenshot tool he forgot about. A calendar widget. And 4 more he didn't recognize. Every one of them was running in the background 24/7 consuming RAM, CPU cycles, and battery life whether he was using them or not. She said: "You turn on your Mac and within 30 seconds, 14 apps are fighting for resources before you've even opened your first document. Your fan spins up because your CPU is processing a traffic jam of apps you're not using. Your battery dies by 2pm because half your power is going to background processes you don't see." She removed 11 of the 14. Kept only the ones he actually needed at startup. The Mac booted in half the time. The fan stayed quiet. The battery lasted 3 extra hours. She said: "Check this list right now. If you see apps you don't use daily, remove them. They've been silently eating your Mac alive since the day you installed them."

• 
  Vladislav Zharkov 👾 (@_vladislavzh) reported 37 minutes ago

  I have zero industry experience. None. I don't know how to use issue trackers, I need a GUI for version control, I deliver my files through Dropbox. I don't have templates, I restart or reuse every time. I don't use industry standard tools, I don't know workflows and pipelines.

• 
  Ishita Sethi (@Ishita__Sethi) reported 38 minutes ago

  @LoganOpSec that dropbox bit is the part that sticks. recovery without revoking access is just half a fix.

• 
  Lisa (@aikens_lisa) reported 38 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 42 minutes ago

  86% of small businesses still haven't fully integrated ai into their operations. which is funny, because the tools are already here. they're everywhere. there's probably one open in another browser tab right now, quietly waiting to change your life. Goldman Sachs surveyed small businesses and found that only 14% have fully integrated ai into their operations. i don't think the other 86% are anti-ai. they're busy. they're cautious. and they probably don't want to add “company-wide ai transformation” to the list of things they need to worry about before lunch. honestly, fair. @paulg said something recently that I keep coming back to: "If the world is going to get turned upside down, the safest place to be is in a small, fast-moving company that can easily change direction." small companies should be the ones moving fastest. but most are still waiting for someone else to go first. someone else to test the tool. someone else to write the playbook. someone else to promise that nothing will get weird. @clairevo nailed the real blocker: "the blocker is never tools or intelligence. human systems, human problems." i've spent 15 years watching this happen. At Dropbox. At Wix. At Zynga. Now at Persona. different tools. different eras. same pattern. a team finds a new tool. everyone gets excited. someone schedules a kickoff. three weeks later, everyone is back in the old spreadsheet. not because people are stupid. because changing how people work is uncomfortable. and buying software is much easier than changing behavior. i've seen the same thing with community-led growth. i used to pitch community to executives who had every tool and dashboard money could buy. they'd nod. they'd agree it worked. then they'd return to the comfortable world of automation, sequences, and dashboards that made everyone feel productive. last year, i ran 86 events as a team of one and built $3M in pipeline. the secret was not a magical growth hack. it was showing up. knowing the 15 people in the room by name. listening carefully. creating a space where people could actually trust each other. not exactly the kind of thing you can solve with a 47-step workflow. ai adoption and community adoption have the same problem. the tools work. the ideas work. the uncomfortable human part is where things usually slow down. sitting with your team and figuring out what should change. trying one workflow instead of redesigning the entire company overnight. leading people through something new instead of sending a Loom video and hoping everyone feels inspired. the 86% aren't waiting for better ai. they're waiting for change to feel a little less scary. so start small. pick one annoying workflow. try one new thing. make it 10% better. then do it again. the tools are here. the next step is still a very human conversation. and, unfortunately, probably a meeting.

• 
  Ed Giansante (@edugiansante) reported 43 minutes ago

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

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

• 
  Kyle Harrison (@kwharrison13) reported 48 minutes ago

  Maybe. Maybe you'd be fine without data centers. But let me ask you this. Do you use credit cards, debit cards, tap-to-pay, gas pumps, vending machines, parking meters, parking apps, ATMs, online banking, mobile banking, mobile check deposit, Zelle, Venmo, PayPal, Cash App, Apple Pay, Google Pay, splitting a dinner bill, autopay on your bills, payroll that isn't a paper check, direct deposit, digital 401(k), Robinhood, Coinbase, credit score checks, loan applications, mortgage applications, car loan approval at the dealership, insurance quotes, filing an insurance claim, e-filing your taxes, gift cards, store loyalty accounts, digital coupons, rebates, buy-now-pay-later, tipping on a screen, email, text messages, iMessage, WhatsApp, Signal, group chats, voicemail transcription, spam call blocking, FaceTime, Zoom, Google Meet, Discord, Slack, video calls with grandparents, phone number lookups, checking your data usage, paying your phone bill, two-factor codes, push approvals to log in, password managers that sync, "sign in with Google," resetting a forgotten password, digital IDs in your wallet app, gym check-in apps, apartment smart locks, hotel keys on your phone, office badge apps, patient portals, seeing your test results, booking a doctor's appointment, telehealth visits, prescription refill requests, the pharmacy knowing what you're on, insurance verification at the front desk, prior authorization, continuous glucose monitors, insulin pump apps, remote pacemaker checks, CPAP data reports, hearing aid apps, therapy apps, period trackers, fertility trackers, medical alert buttons for elderly parents, symptom checkers, finding an in-network doctor, the weather app, radar, hurricane warnings, tornado warnings, flood alerts, earthquake early warning on your phone, wildfire maps, smoke maps, air quality, pollen counts, Amber alerts, emergency alerts, road closure info, Google Maps, Apple Maps, Waze, live traffic, rerouting around a crash, transit apps, real-time bus and train arrivals, tapping your phone to ride the subway, Uber, Lyft, rental car reservations, Turo, bike share, scooter share, EV charging networks, paying for a charge, phone-as-car-key, remote start, finding your parked car, over-the-air car updates, in-car navigation, in-car voice assistants, stolen vehicle tracking, road trip planning, booking flights, checking in for a flight, mobile boarding passes, seat selection, flight status, rebooking after a cancellation, bag tracking, TSA PreCheck lookups, airport wifi, booking hotels, Airbnb, Vrbo, checking into a hotel, cruise bookings, theme park tickets, ride reservations, airline miles, hotel points, currency conversion, Amazon, all online shopping, order tracking, delivery notifications, returns and exchanges, price checks in-store, self-checkout, store apps, curbside pickup, Instacart, DoorDash, Uber Eats, ordering ahead at a restaurant, OpenTable, Resy, waitlist texts, QR code menus, tipping on delivery, subscription boxes, eBay, Etsy, Facebook Marketplace, Craigslist, Poshmark, StockX, Ticketmaster, StubHub, getting into a concert with a phone ticket, Alexa, Siri, Google Assistant, smart thermostats, video doorbells, security cameras, alarm monitoring, smart locks, smart lights, robot vacuums, garage door openers, baby monitors, pet cameras, automatic pet feeders, GPS pet collars, smart sprinklers, smart fridges, app-connected air fryers, cloud printing, printer ink subscriptions, routers you manage from an app, checking if you left the stove on, iCloud, Google Photos, every photo you've taken in ten years, Dropbox, Google Drive, OneDrive, shared albums, phone backups, setting up a new phone, notes apps, calendars, contact syncing, reminders, to-do apps, document scanning, e-signing a lease, Netflix, YouTube, Hulu, Disney+, Max, Prime Video, Twitch, cloud DVR, on-demand cable, Spotify, Apple Music, podcasts, audiobooks, Kindle books, library ebook borrowing, online multiplayer games, matchmaking, cloud saves, game downloads, game patches, single-player games that phone home for a license check, Steam, PlayStation Network, Xbox Live, Nintendo Online, Roblox, Minecraft servers, fantasy football, sports scores, sports betting apps, movie tickets, Google search, Wikipedia, ChatGPT, Claude, every other AI app, Instagram, TikTok, Facebook, X, Reddit, LinkedIn, Snapchat, Pinterest, dating apps, Yelp reviews, Google reviews, news sites, Substack newsletters, blogs, forums, checking if a business is open, looking up a phone number, recipes, translation apps, Duolingo, Google Docs, Sheets, Gmail, Outlook, Microsoft 365, Teams, Notion, Figma, Canva, shared calendars, scheduling links, VPNs into work, remote desktop, timeclock apps, shift scheduling apps, requesting time off, expense reports, job applications, LinkedIn recruiters, video interviews, Canvas, Blackboard, checking your kid's grades, school lunch accounts, attendance notifications, online homework, Khan Academy, Coursera, FAFSA, student loan portals, tutoring apps, Fitbit, Apple Watch health data, Strava, Peloton, sleep tracking, smart scales, calorie tracking, meditation apps, workout apps, DMV appointments, renewing your license online, paying a parking ticket, jury duty portals, checking your property tax bill, utility accounts, outage maps, paying rent through an app, HOA portals, storage unit access codes, wedding registries, baby registries, funeral arrangements, Ancestry, 23andMe results, church livestreams, volunteer signups, or GoFundMe? If you said yes to ANY of those then you do, in fact, NEED data centers.

• 
  chimeno (@chimeno) reported 48 minutes ago

  And Dropbox was just an ftp server

• 
  🔩⚾️ (@john_dough) reported 51 minutes ago

  @irisivanyi @nickcamsmith If someone has a very fancy and complex portfolio site, they are probably not working very much. My portfolio is 10+ years out of date because I never have the time to update it. I just send a Dropbox folder of images of new work to people these days. ¯\_(ツ)_/¯

• 
  Nathan (@arcane_bloom) reported 53 minutes 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

• 
  Scarlett Bama 🇺🇸🅰️🐘🏈🏖️✝️ (@scarlettbama) reported 54 minutes ago

  @DropboxSupport Fri AM: Dropbox down? Rare if so! Will not allow PDF upload to existing folder. Upload 50x per month. Started after most recent IOS update. Using iPhone. No MacBook access right now. Pls don't sent to Community Forum.

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

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

• 
  Joachim Voth (@joachim_voth) reported 60 minutes ago

  @DropboxSupport why can I only use one core for indexing? Most machines have MANY nowadays. Download speed is not the issue, it is almost always the ultra-slow indexing that dropbox does with only one CPU core active. Am I seeing this right? Why can we not dedicate 5 or 8 cores to something that really slows down your users?