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	19 days ago
Guayaquil	Website Down	19 days ago
Flumet	Errors	29 days 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:

• 
  Kyle Harrison (@kwharrison13) reported 2 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.

• 
  Phillip Shepard (@Phillip_shepard) reported 7 minutes ago

  @RobertJBye One thing I do on a daily basis - I have a skill that is called the “video analyzer skill” and I record a screen record with my iPhone and microphone one - I talk about all the issues I need fixed while showing it in video - send it via Claude mobile app - it runs the skill - transcribes and makes its self a html doc with the video frames that the issues exist in - then fixes the issues - builds a test flight and I update it - very useful… if the video is too big I send it via Dropbox which syncs to my Mac

• 
  Synapse Brief (@Synapse_Brief) reported 8 minutes ago

  @gdb Scraping 7 consecutive years of tax forms and equity statements across Dropbox and Shareworks requires orchestrating dozens of DOM interactions without dropping session state. Standard visual tool-calling loops degrade quickly once context windows swell from repeated full-page DOM trees and screenshot tokens across nested subfolders. The underlying issue with multi-year document extraction is not simple folder traversal, but error recovery when dynamic OAuth tokens expire mid-sweep. Navigating nested web UI trees for 2016 through 2025 records usually hits rate limits or modal overlays that cause visual grounding agents to hallucinate click coordinates. Production reliability on complex immigration workflows will require hybrid execution models that compile raw browser actions into structured API calls or deterministic scripts after initial path discovery. Until agents decouple stateful file fetching from reactive visual vision loops, edge-case recovery will remain the bottleneck for zero-touch filings.

• 
  DAX : TV (@daxtv) reported 9 minutes ago

  @0x00_dev @ProtonMail have been using dropbox for years- never an issue - thought it might be smart to move to Proton Drive - but not now me thinks - hey ho :)

• 
  Callitlikeitis (@Callittlikeitis) reported 15 minutes ago

  @iAnonPatriot Yeah no.. That’s even more piracy. I will Dropbox if it comes down to this drone diarrhea. Or better yet bypass lameazon all together

• 
  Matt Mazur (@mhmazur) reported 16 minutes ago

  Day 2 of Claude autonomously shipping to my SaaS, including, for the first time, all night while I slept: The first day I had the hourly routine that kicked off this process end at 8pm so that if anything went awry, it could @ me in Slack and I'd quickly see the notification and dig in. The first day went smoothly, so I let it continue working overnight last night: every hour it would look for a small, safe change to make, ship it to ****, and monitor server logs and Sentry to make sure everything went well. A few other process improvements: - It now creates a PR for every change and links to it from its Slack summaries - Previously I only allowed it to make changes in 3 files max, but sometimes it identified the same issue spread across multiple locations, so it would have to spread that work over several hours; I bumped the limit to 8 files. - If I have uncommitted changes in main, it no longer blocks Claude's work; it moves them to a separate branch - Added a mandatory security review before pushing to ****. For these simple changes it's not that necessary, but it will be important for larger projects in the future. Specifically, I told it to run the default /security-review skill and if it flagged anything, to halt everything and wait for me to review. - Ran into a slight issue one hour where it ran that skill, the security review passed, and then it did nothing. I asked Claude to investigate, and it discovered it had run the skill in its main context window, which confused it into thinking its only job was the security review. It changed the process so the security review happens in a subagent, keeping the context window clean, which fixed things. - I asked it to maintain a ledger of things it needs me to do and to ping me every 24 hours if I haven't knocked them out. More and more, the agent is giving me things to do. - I told it to adopt the tone of TARS from Interstellar in its Slack updates going forward, cause why not. Here's a list of improvements it made on day 2: 1. Return 404s for bad case-study URLs 2. Extended the 404 fix site-wide 3. Removed stray code leaking into HTML 4. Fixed broken citation example in docs 5. Fixed wrong URL in sharing docs 6. Corrected false free-plan claim 7. Removed duplicate HTML attributes 8. Fixed dead links in embed docs 9. Fixed garbled copy on two pages 10. Pointed "paid plans" link at pricing 11. Added missing alt text to logo 12. Corrected a misleading code comment 13. Upgraded insecure links to HTTPS 14. Replaced dead testimonial link 15. Fixed broken example in Dropbox docs 16. Fixed awkward grammar on comparison page 17. Fixed reversed table of contents 18. Fixed missing Show More button 19. Matched nav label to its section 20. Corrected outdated visibility docs claim 21. Removed obsolete step from setup docs These can be categorized as: support-doc accuracy fixes (7), functional bug fixes (4), broken or insecure links (3), copy improvements (3), invalid markup (2), accessibility (1), and code hygiene (1). Excited to expand the scope of things I allow it to work on, but am going to wait until next week to ensure the current process is robust.

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

• 
  virgin loser (@stonershelb) reported 24 minutes ago

  He put a photo of their 2 yo daughter naked with exposed genetalia in a Dropbox folder that “received more than 400,000 combined views or interactions. ... and it was publicly accessible for 23 hours before she says Minc acknowledged responsibility and took it down.”

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

  @DropboxSupport erm different wifi nope or is this a suggestion should it be possible ? if so then no my internet signal can be hit or miss at times but never had this issue before... Also shared a file earlier for someone near me to edit using ipad app but photos failed to appear on ipad ?

• 
  Brandon (@BJohnsonxAR) reported 28 minutes ago

  @DropboxSupport I’m having issues logging in. When I try to login it’s making me sign up when I already have a paid account. This is happening on both the app and my browser. @Dropbox

• 
  The Redeemed Artist (@Peace_Grenade81) reported 29 minutes ago

  I know I'm just screaming into the void. And there's probably less than like one or 2% of users that actually use this function. But I'm going to do it anyway. For the longest time the X app beta was absolute garbage on Android. It had serious stability problems, I couldn't use voice to text properly, and I couldn't access my memes from Dropbox, my cloud provider. The most recent change fixed all of the other problems except for my Dropbox integration. At first, I blamed X for this but I have since come to learn that the real culprit is Google. If you go into your app section and look for cloud providers they give you all sorts of choices so long as you like the choice that is Google's. Theoretically, other providers should be in here like Box or Dropbox. But Google has been playing footsie making rules about cloud provider integration and not actually approving anyone else. Google has become Microsoft. Google will tell you what cloud provider to use and it will conveniently be their own. Google will continue to upgrade their operating system closing off any other provider options or applications they simply disagree with for any reason at all. Meanwhile what this means for me is that I can't insert any memes or videos because they are all stored on Dropbox. Yeah, yeah, yeah I could go into Dropbox and then click on a photo and then share it to X and then make a post out of it. But what I can't do is respond to a post and insert a picture or a video directly through the X app. Don't know when this gets fixed, if ever. But I think it's time for Google to be investigated for monopolistic practices. I realize that this doesn't affect many people, but if you think they aren't coming for your various conveniences, I'm pretty certain that that's going to be proven wrong. Since I can't post a meme but only a local photo, here's an unrelated picture of a quilt we bought at auction. 🙄

• 
  Eric Smith (@Eric_Smith08) reported 35 minutes ago

  The full math. What he replaced and what he saved: 1.Dropbox ($12/month) → Google Drive (15 GB) + OneDrive (5 GB): $144/year saved 2.Zoom ($13/month) → Google Meet (60-min calls, 100 participants): $156/year saved 3.Notion ($10/month) → Google Keep + Google Docs + OneNote: $120/year saved 4.Todoist ($5/month) → Microsoft To Do: $60/year saved 5.Slack ($8/month) → Microsoft Teams free tier: $96/year saved 6.Grammarly ($12/month) → Microsoft Editor + Gemini/Copilot for rewrites: $144/year saved 7.Adobe Acrobat ($15/month) → Google Drive PDF viewer + Edge PDF tools + Word Online conversion: $180/year saved 8.Trello ($10/month) → Microsoft Planner: $120/year saved 9.ChatGPT Plus ($20/month) → Google Gemini + Microsoft Copilot (free tiers): $240/year saved Total monthly cost before: $137 Total monthly cost after: $0 Annual savings: $1,644 Total setup time: one weekend Saturday for Google migrations, Sunday for Microsoft configurations. Accounts created: 0 (he already had both) Apps downloaded: 3 (Microsoft To Do, Teams, OneNote all free) Browser extensions installed: 1 (Microsoft Editor free) Every replacement runs on accounts he created years ago. The tools were sitting behind the same login he uses for Gmail and Outlook unused, unconfigured, and paying rent to 9 other companies that built the same features on top of what Google and Microsoft were already giving away.

• 
  RVCrypto (@RvCrypto) reported 37 minutes ago

  Every once in a while I have one of those moments as an investor where everything just clicks. I had that moment a couple of weeks ago with Leadpoet, $TAO subnet 71. What initially caught my attention was the team. To me, they represent what a Bittensor-first team should look like. They're deeply committed to the ecosystem, they execute quickly, and, most importantly, they seem to understand that in the end none of that matters if you don't build a product customers actually want. The product appears to be working really well. Winning the OKX product competition and attracting an inbound pilot with Dropbox are the latest two independent signals that suggest they're solving a real problem for enterprise sales teams. The opportunity they're pursuing is also enormous. Enterprise sales is a market worth billions, and if Leadpoet continues executing the way it has so far, I genuinely believe they have a realistic path to building an eight-figure revenue business next year. And the best part here is that all of that value ultimately flows back into the token. I've also spent quite a bit of time talking with Gavin over the past few weeks and months. Those conversations gave me a very similar feeling about Leadpoet to the one I had with Score when talking with Max. I don't make that comparison lightly. It's great to see Leadpoet finally getting the attention it deserves, and the recent price action reflects that. Although, if I'm being completely honest, I would have loved one more dip to accumulate a bigger position, and I know I'm not the only one thinking that.

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

• 
  Just Matthew (@MatthewP279348) reported 40 minutes ago

  @Rani_Rant_Fest @iGardon Doesn't change the fact that they aren't showing the prompt, so the result is valueless. I don't read people's google shares. Put it in dropbox if you want me to read it. Lastly, calmatters is a CA bureaucracy, of course they will lay down cover for their corrupt gov.

• 
  Llama (@thellama451) reported 42 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.

• 
  Christopher Bailey (@LexBaileyAI) reported 43 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?

• 
  하레 (@ascoeur9) reported 44 minutes ago

  I also experienced the same issue two months ago and reported it, but no action has been taken. In the end, I started syncing all the folders with Dropbox.

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

• 
  grey (@w3b3grey) reported 45 minutes ago

  If you are like me and you wondering, where my IDENTITY PEM FILE is on @flop_labs , I gat you; here is how to find it identity.pem is already saved automatically; the init command writes it to your project folder the moment you run it (typically right in technocore-did-starter/identity.pem). You don't need to do anything extra for it to exist. What "saving" really means here is backing it up safely, since if this file is lost, your DID is unrecoverable (the guide's troubleshooting table says exactly that: "there is no central DID recovery service"). 1. Confirm it's there ls -la ~/technocore-did-starter/identity.pem 2. Back it up to a second location — copy it somewhere other than the working folder, e.g. an external encrypted drive or a password manager that supports file attachments (1Password, Bitwarden both do this): cp ~/technocore-did-starter/identity.pem ~/Desktop/identity-backup.pem Then move that copy off your main disk (external drive, encrypted USB, etc.) rather than leaving a second copy sitting in ~/Desktop long-term. 3. Lock down file permissions so only your user account can read it: chmod 600 ~/technocore-did-starter/identity.pem 4. What NOT to do with it Don't upload it to GitHub, Google Drive, iCloud Drive, Dropbox, or any synced/cloud folder in plaintext. Don't email it to yourself or paste it into a chat (including this one). Don't commit it to *** , the guide's Path B steps even have you run *** ls-files "*.pem" "*.key" before committing specifically to catch this. 5. Remember the passphrase separately from the file The .pem is encrypted, but it's useless without the passphrase you set during init. Store that passphrase somewhere separate from the .pem backup itself (a password manager entry, not a text file sitting next to the key), so a single leaked backup doesn't hand over both pieces at once. NOTE - If you lose either the file or the passphrase, per the guide, there's no recovery; you'd have to run init again and get a brand new DID.

• 
  Ryan Babbs (@buckybabbs) reported 47 minutes ago

  Hello @Dropbox, Just this week I have decided to switch cloud service from Google Drive to you and less than 1 week I'm having an issue. I run a wedding film business and am trying to move the same 200GB file to two separate editors for two separate kind of films and one of them is encountering a "link temporarily disabled" message. I tried to research online and made a new folder and copied over the original folders contents and cannot share that either as it says I've exceeded bandwidth limits. This is maddening as I thought I'd picked the good plan (3TB) and was all set. Please advise asap as I need these files in my editors hands stat.

• 
  Sean Knox (@Opp_Knox) reported 48 minutes ago

  @dhh One drive is the only thing keeping me on Mac/windows. Personal I’m down to switch to Dropbox or self hosted. Business I can’t.

• 
  AiMind (@AIMind_Ai) reported 48 minutes ago

  3 websites replace 20 hours of googling when you build a home server. The hard part of self-hosting is not the hardware. A used HP EliteDesk and a wall-mounted NAS cost almost nothing. The hard part is not knowing what you can even run, or how to avoid breaking the system on the first command. The first keeps a catalogue of self-hosted alternatives. Look up a replacement for Google Photos, Dropbox, or Notion, and you see what already exists, how many GitHub stars it has, and whether it is still alive. Plus a weekly digest of what shipped. The second lets you run any Linux distro straight in the browser. Arch, Debian, Alpine, Bazzite. Click once, and you are inside a live system, with no evening lost to a USB stick and a real install. The third handles the worst part. Install scripts for Proxmox: Immich, Jellyfin, Vaultwarden, AdGuard, Nginx Proxy Manager. Paste one line into the console and the container comes up on its own. Immich shows 17,735 installs; Docker 36,408. Each of those services used to cost an evening of documentation and three Stack Overflow tabs. Now it is one command. The hardware takes an hour to buy. These 3 bookmarks save you a month. Names in the replies.

• 
  Robert J Abalos (@robertjabalos) reported 49 minutes ago

  Want Your Startup to Get VC Funded? You Must Meet All Six of These Requirements Venture capitalists at the seed stage bet on potential more than perfection, yet they demand specific proof points before writing a check. After reviewing hundreds of deals and data from PitchBook, Crunchbase, and leading funds, six absolute requirements stand out. Miss any and the odds of funding drop sharply. First, an exceptional founding team. Team quality remains the single highest weighted factor before product market fit solidifies. VCs look for domain expertise, prior execution, complementary skills, and coachability. Research shows roughly one in four two founder teams loses a co founder by year four, so investors scrutinize resilience and equity alignment. Companies with strong teams raise at higher valuations even with lighter metrics because execution can fix product or market gaps. Second, a large and expanding market. Seed investors require a total addressable market of at least one billion dollars, ideally several billion, with a clear path to one hundred million in annual revenue. Serviceable addressable market should support venture scale outcomes. Markets growing above twenty percent annually command premiums. Small markets cap upside and rarely produce the fund returning exits VCs need. Third, early traction proving customers care. For SaaS this often means ten thousand to one hundred thousand in monthly recurring revenue or three hundred thousand plus in annual recurring revenue. Pre revenue startups need strong engagement such as daily active users to monthly active users ratios above twenty percent, organic waitlists, or letters of intent from unaffiliated customers. Dropbox famously used a demo video that drove seventy five thousand sign ups overnight, unlocking its Sequoia seed. Slack showed early retention that later became legendary. Fourth, rapid and consistent growth. Seed VCs seek fifteen to twenty percent or higher month over month revenue or user growth sustained over multiple months. Absolute numbers matter less than trajectory. Startups posting twenty percent plus monthly recurring revenue growth have seen close rates near sixty five percent in analyzed pitch data. Flat or decelerating growth signals risk. Fifth, early unit economics and retention signals. Even at seed, investors examine lifetime value to customer acquisition cost ratios above two to one, ideally three to one, net revenue retention near or above one hundred percent, and cohort retention that flattens rather than collapses. Gross retention above eighty to ninety percent is a positive signal. These metrics prove the product delivers lasting value and that growth will not require endless capital. Sixth, capital efficiency and clear runway. Burn multiple and months of runway matter. Investors prefer teams that can stretch capital to eighteen months or more while showing improving efficiency. Median U.S. seed rounds now sit near three to four million dollars, yet graduation to Series A has tightened to roughly twenty to fifty percent depending on cohort and sector. Lean teams of four to eight people that still deliver results stand out. Data confirms the stakes. Only a minority of seed companies reach Series A, and failure rates near forty percent are common. Yet the power law rewards those that clear these bars. Airbnb, Stripe, and early Slack all combined strong teams, massive markets, and measurable early traction. Founders who quantify these six elements with real numbers, not projections, dramatically improve their chances of securing seed capital.

• 
  havenX (@the_havenx) reported 49 minutes ago

  Second time this exact thing has happened with Claude. ~100k ChatGPT chats were found the same way after users hit "shared." Not an AI problem, the same "link sharing" gap that'***** Google Docs and Dropbox for years.

• 
  EFANI Secure Cellphone Service (@efani) reported 51 minutes ago

  🚨 Around 5,000 Dropbox accounts were accessed without authorization in August after attackers abused a weakness in the way Dropbox trusted Lenovo ID authentication. The attack did not require victims’ Dropbox passwords. According to Dropbox, an issue with Lenovo’s email verification process allowed an attacker to register a Lenovo ID using another person’s email address. Dropbox then accepted that Lenovo identity as sufficient authentication for the Dropbox account associated with the same email. Unauthorized access occurred between August 4 and August 21. Files were viewed or downloaded in fewer than a third of the affected accounts. The security problem here is bigger than one flawed login flow. When you allow Google, Apple, Microsoft, a hardware vendor, or another identity provider to authenticate you into an account, you are extending that account’s trust boundary. Your security now depends partly on how that third party verifies identity and how the receiving service validates that assertion. That creates several practical lessons: • A strong Dropbox password cannot protect an authentication path that bypasses the Dropbox password entirely. • Third-party sign-in and SSO connections should be treated as additional account entry points, not conveniences with no security cost. • Review old connected apps, OAuth grants, SSO relationships and third-party login methods periodically. Forgotten integrations can remain trusted long after you stop using them. • Enable MFA wherever possible. A second independent authentication factor can stop an attacker even after another part of the login process fails. • Sensitive cloud storage deserves extra scrutiny. Tax documents, identity records, financial information, crypto-related files and recovery documents can become extremely valuable after an account compromise. Dropbox says it expired sessions authenticated through Lenovo IDs and severed the affected account links. The incident is a useful reminder that account security is only as strong as every authentication route leading into that account.

• 
  Guymon Adams (@guymonadams) reported 53 minutes ago

  @BrianRoemmele Man, this seems to be a recurring problem for Dropbox. I remember a similar story several years back about their own employees browsing thru user files. All the reasons I moved over to Sync, a much more secure and respectable alternative.

• 
  Olivia Jane. 🦇 🗡️ 🩸 (@livtheripper) reported 55 minutes ago

  @HazeOfBlue84 Haha, I get it! Thankfully someone here at the office set it up and all I had to do was re-sync Dropbox! I had no issues at all, so I'm thankful.

• 
  160 IQ haver Randy (@MinionTripper) reported 58 minutes ago

  @mittsh why would anyone use dropbox you can just setup an ftp server on a linux machine!

• 
  Juan Pabro (@ironwoodreserve) reported 59 minutes ago

  @BitPaine @Dropbox Is now the worse time to try to login? I was a sent 2FN right as I was getting ready to click on what to use to login. It seemed way too fast for 2FN.