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 (50%)
• Sign in (33%)
• Website Down (17%)

Live Outage Map

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

City	Problem Type	Report Time
Bournemouth	Sign in	1 month ago
Paramaribo	Errors	2 months ago
Bogotá	Website Down	2 months ago
Auxerre	Errors	2 months ago
Salt Lake City	Sign in	2 months ago
Madrid	Errors	3 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Dropbox Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Rebecca Diamond (@rebeccardiamond) reported 1 minute ago

  @p_ganong I’ve had this problem too. When I’m editing with Claude, edit manually directly in the .tex file locally on your machine through overleaf-Dropbox sync. Then you and Claude are both working locally.

• 
  Harshita Renee (@harshitaxmars) reported 3 minutes ago

  Despite me having proven him wrong about the exact requirement table issue he pinned on me as a “it’s her problem, shut her up” (Dropbox has the scoresheet proving I was not out of line, they were), I don’t think he can ever be wrong. That is just technical error on his part.

• 
  alt guy (@0xAlternateGuy) reported 8 minutes ago

  @antirez quite suspicious this happens immediately after the Dropbox CEO steps down…

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

  The interviewer asked me to design Dropbox file sync. I froze for a minute because I jumped into architecture before I nailed requirements. So I restarted with questions: single user or teams? offline edits? conflict handling? max file size? latency vs battery? Windows/Mac/Linux? end to end encryption? I scoped to: multi-device per user, near-real-time, offline support, conflict resolution, and basic sharing later. Then I wrote the core objects and APIs. Data model: User, Device, File, FileVersion (content hash, size, chunk list), Folder, Cursor/Checkpoint, and an Event log (append-only). APIs: UploadChunk, CommitFile(version, parentVersion), ListChanges(cursor), Download(version), Ack(cursor). Everything is idempotent with content hashes and request IDs. Architecture: client watches filesystem, batches changes, chunks large files, uploads to blob storage keyed by hash, then commits metadata to a strongly consistent store. Server writes an event per commit. Clients long-poll or use a push channel to get change events, then pull missing blobs. Scaling: hot path is metadata and change feed. Partition event logs by user/team, cache cursors, and keep blobs on cheap object storage with CDN for downloads. Dedup by hash saves real money when the same installer shows up on 500 laptops. Background compaction for old versions and tombstones. Tradeoffs I called out: strong consistency on metadata avoids weird conflicts but costs latency on cross-region; eventual consistency makes sync feel faster but harder to reason about. Chunk size trades memory and upload overhead vs retry cost. Conflict policy can be last-writer-wins (simple, lossy) or keep both versions (messy, safer). Failure cases: client crashes mid-upload so you need resumable multipart and garbage collection for orphaned chunks; network ***** so commits must be idempotent; clock skew so ordering cannot trust timestamps; two devices edit offline so you fork versions and surface a conflict file; duplicate events so cursor ack must tolerate replays; permissions changes during sync so downloads need auth checks at read time, not just at commit time

• 
  Elias Al (@iam_elias1) reported 16 minutes ago

  8/ The settings on your own devices that are silently eating bandwidth. Even with a great router, fast DNS, and honest ISP speeds, your devices may be consuming bandwidth you didn't authorize. Common culprits: On your phone: 1. iCloud/Google Photos backup set to sync constantly (not just on Wi-Fi) 2. App updates downloading in the background 3. "Wi-Fi Assist" on iPhone (silently switches to cellular and back, disrupting connections) On your laptop: 1. Cloud sync services (Dropbox, OneDrive, Google Drive) uploading constantly 2. Windows/macOS pushing system updates during peak hours 3. Browser tabs running in background consuming bandwidth with auto-refresh On your smart TV: 4. Firmware updates downloading during prime streaming time 5. Multiple streaming apps running in background 6. ACR (Automatic Content Recognition) sending screenshots to servers every 15-60 seconds On IoT devices: 1. Smart cameras uploading video 24/7 2. Smart speakers maintaining constant server connections 3. Smart home hubs polling every device every few seconds She audited every device on her network. Twelve devices were consuming bandwidth she didn't know about. Three of them were using more data than her actual streaming.

• 
  Theeevilprincess (@Theeevilprince1) reported 17 minutes ago

  My Dropbox I cannot login so everything is being sent on telegram until further notice

• 
  Random Poser (@rndposer) reported 17 minutes ago

  @iHerbMiddleEast Problem with iHerb is your delivery service to consumers. They’re a challenge to work with. I wouldnprefer if there is option to get my deliveries directly in a dropbox somewhere near and not go thru the 3rd party delivery service.

• 
  Pixelhop (@pixelhopio) reported 18 minutes ago

  Notion is a walled garden where external AI agents go to die. Don't get me wrong: we've been huge Notion fans for years. Our entire company lived there: dashboards, notes, projects, our collective brain. It was perfect for humans, but then the Agent Era hit and everything changed. We now work with coding agents like Claude Code every single day, and that is where the friction started. Trying to get external agents to talk to proprietary blocks via a slow API is a total nightmare. The rate limits are painful and the structure is just too rigid for an agent to be efficient. We needed that polished Notion feel without the proprietary bloat holding our agents back. So we built Treehouse: a tool that is essentially Notion meets Dropbox. Treehouse is a web-based viewer for a local folder on your computer. The magic is that the folder is automatically synced across your whole team, kind of like a shared drive with a beautiful face. There is no proprietary database: just your files on your disk, exactly where they belong. Because it is just a folder, your AI agents can talk to it directly at lightning speed. No API rate limits or slow responses. I can ask an agent in my terminal to build an HTML page locally and have it render for the team instantly. Reclaiming your data doesn't mean sacrificing aesthetics. We built in advanced theming and custom CSS support: you can even have your agent rebrand your entire workspace for you. Notion was built for humans. In an AI world, we need high-speed playgrounds, not walled gardens. We are planning to open source Treehouse soon. If you want to reclaim your data, let us know! We wrote a blog post about it below 👇

• 
  Sourav Dutta (@sourav12dutta) reported 18 minutes ago

  @ishankbg @Siradhvaja @PhilipPanass Yes, shodhganga seems to be down. Can you suggest how I can post a folder with 10 pdf files here? Both dropbox and wetransfer are asking for email id.

• 
  Music, Film & RE Investments (@investandcreate) reported 20 minutes ago

  @0xajka @Dropbox Have you tried doing the whole uninstall, reinstall? I had to do that one time with Dropbox. It was horrible. Now I have even a worse problem - but it’s not exactly Dropbox’s fault.

• 
  Juan (@0xfJuan) reported 23 minutes ago

  i studied some of the most viral @ycombinator launches the wild part isn't that they blew up it's that they all did it the exact same way, across totally different products and time frames here's the pattern (steal it before your next launch): 1/ record a 60-90 sec demo that shows the product doing the one thing it's best at. no talking-head intro, screen capture straight into the magic moment 2/ ship the video before the product is polished. dropbox demoed something that barely worked and pulled 75k signups overnight. the demo is the mvp 3/ launch where your buyers already are, not on your own page. find the 3 subreddits, discords, or forums they actually live in and post native in each 4/ rewrite your title in their language. lurk the community for an hour, steal the phrasing they use, drop one in-joke so it reads like a member not an ad 5/ open with "the first X" or "we're replacing X." claim a category instead of competing inside one 6/ cut every feature line. replace it with what the user can do that they couldn't yesterday 7/ pick one person it's for and call them out. "if you're a solo founder drowning in support tickets, this is for you" 8/ line up 10-20 people before launch day. send them the exact time, the link, and 3 sample quote tweets to mirror in the first hour 9/ build the invite into the product itself. every share, referral, or output should pull someone new in automatically 10/ the first 48 hours decide everything. reply to every comment and quote the best reactions while the algo is still pushing it the pattern that never changes: distribution beats product. the best launched company wins, not the best built one. (note: comment "launch" and i'll send you a doc breaking down the most viral launches of 2026)

• 
  Samuel Udeh (@Sammichike) reported 23 minutes ago

  Nice, Google Drive / Dropbox is still the go-to for a lot of people, especially for bigger files. But man, the moment you share that link… “Download required to view properly.” Preview looks compressed and ugly Sometimes the link breaks if permissions change Or the client just never downloads it That’s the exact frustration SnapVid @snap_vid was built to fix: Upload once → permanent streaming link No compression, instant play, beautiful previews (even on WhatsApp), no “download first” nonsense. If you ever get tired of the Drive preview pain on your next share, give it a quick test, free tier is unlimited for basics. What’s the main reason you usually pick Drive? File size? Ease? Or something else? Curious to know!

• 
  J. (@munchivelo) reported 24 minutes ago

  track back to just over a year to now. i'd built an automated ecommerce flow that took a whole store end to end. seo would research trends, products, and map those into .js scripts which would launch prompts that read those research files. that would feed an image gen prompt which created designs, set to specific standard. i'd generate them, and then ANOTHER prompt, would check the images, score them with a criteria, and either move them to an accepted folder, or move them to an archive folder. the accepted folders, would automatically fire a script which would open photoshop, map the image to smart layers, in a 'product shot' template i'd made, and then export all of the final product shots to another folder, and then exported the flat designs which would be used for the products. another script took the product images, did visual lookups, generated all product descriptions, renamed the images and generated the seo text. it ran optimizations locally via a jpegoptim and oxipng script. it then uploaded them to dropbox, and via API, would generate a dropbox link map. i had one barebones csv template, which i'd run a ps1 script through to map json files into the csv rows, and insert the dropbox link map. all my images, links, followed the exact same slugs, so it turned 2 hours of manual work into a 5 second bulk rename and insert. it then converted that csv into json, which then itself converted that json into ld-json for product rich listings. ai would write the product description based on a dataseo keywords, and googletrends json file that would run on every product type. collecting keywords for that specific product. it also formed it around brand profiles, copy guides and other things. this was sonnet 3 days, GPT 4.0 days, and it STILL wrote great copy when it had the right guidance. in the .js file, i'd replace all em dashes with a hyphen if they ever appeared. i built a custom product uploader, built my own php plugin which synced to local .js files and connected via rest. it was (and still is) one of the best wc product uploaders that exist, as it completely resets filterlookups only for that product, and is lightning fast because i upload it directly into woocommerce rows from json. no importers, no wordpress malarkey, or WC rest needed. it was 50x faster than wc's own CSV import. the images would be uploaded via ftp, and then on detection, would sync those to the media library, and i'd upload the image meta from the seo run, so they all had captions/alt text etc. it took what would be 3-5 hours of manual work per product, and congested it into a 2 minute image to fully live product system. after that, i'd export sales data, the ai was constantly learning, sales data feeding back to files, which would then teach the ai what products work, what doesn't. what copy worked, what copy didn't. that would then flow back into the original source files which told the ai what images to gen and what products to launch. all of it was local on my pc. i wasn't selling an saas. it was just something that worked for my very particular setup. the thing about it is; i built that mostly with GPT 4.0 and a little bit of 3.5! mostly copy and pasting code manually from the chats in chatGPT. all the plugins, the php, everything. then some of it got improved inside vscode back on the old original copilot plans, when $10 used to last you an entire month of none stop coding. this was before n8n, before agents were even a thing. all of that I built very specifically for myself, local, syncing folder to folder, json file to json file. python scripts watching files, and .ps1 files that would follow up with other .ps1 files, which launched .js files which contained prompts for AI, and hitting the openAI API's whenever I needed the AI layer. eventually i built a terminal tool, which would allow me to run the scripts from the terminal, and i'd manually type in the slugs for which products i wanted processed. all files would sit in specific folders, and scripts would do the rest. i was so excited about that, giving my terminal app a shortcut icon and putting it onto my taskbar. that was a year ago. fast forward to now. the game has changed so much. ANYTHING and i mean anything is possible now. people 'new' to codex, and CC etc don't know how good they have it. my advantage is that i have a year of scripts, a year of tools. i've laid the SYSTEMS in place, to fully map out entire features, precisely, and organized, and build out projects, in one hour, and have it implemented within the next. entire saas features - mousework. but i've had this ******* idea for so long, to build a fully automated, self learning ecom business, that launches products end to end based on it's own research, writing, and growth, but the complexity of it previously , and being busy with life, it never got finalized. the secret is i sync it via etsy too, but they're API keys take FOREVER to aquire, but built my own etsy system, product uploader, which runs across 7 different stores. however, now, i've finally been building the replacement for it. i'll be able to run that exact same system, except this time through a full app, with a canvas, and agent systems instead of .ps1 scripts. not to say i won't run scripts; they're an integral part of any automated workflow, but now it has superpowers, and it can do so so so much more. all the ideas I wanted to do, automated, fully, end to end. not only that, but i moved away from woocommerce entirely. instead i just built my own website builder, which is also fully automated end to end. my brand profiles, my artwork system? i'm still using those, just for more things. now i can launch 50 brands just like it, running the same system, all in about 5 minutes. whether it's saas, local service, or online ecom. i also built an ai automated ad builder. it takes my brands images, or generates images. i've got background removers, and full skills and agents which fully generate the ads for me. it mixes all that into seedance videos, and posts in logos etc. now i take those image/videos, and build instagram, tiktok, facebook vids, generate descriptions, and upload them automatically. it has an every growing library to source from, templates to use, and the system derives right with the websites, so all themes/styles match precisely to the brand. this is why it's so great building for yourself. the amount of reusability you get with it, the fact it's free forever, can never be beaten. none of these saas companies get it. and they're heading in the wrong direction. we could already DO half of what these companies are doing. my own personal SEO system, which i built for my automated web builder, is already 10x better than any yoast, rankmath etc. i skip expensive ahrefs, semrush, and just rebuild their services myself, using API, which is 100x cheaper. except this time it FEEDS my system, and i don't need to lay a finger on it. nobody cares about these little one off apps that won't exist in a year. they're either failing to see the future, or they're hoping for an early exit before they know the dominos start falling. and they don't get it. their 'app' is just a little tiny module in something that thinks bigger. people will want PRIVATE systems. all speaking to each other. not 1200 integrations and 1200 invoices to send to, that don't even have a ******* brain. i'm not selling anything yet. but if you're interested in seeing how i think about automation, then stay a while and listen. the tool i'm building will absolutely help you too. but i'll be honest. i'm actually quite scared to release it, solely down to how powerful it is. not many people do it like i do, and i'm finally on here to tell the world. the only winners will be the ones prepared for cannabilism. ready for war. they call it war rooms, yet they sit around eating donuts provided by their VC's. real builders sit in the dark, in empty rooms, grinding. if you're a cannabilistic, sick sadistic, son of *****, 666, with an idea. then drop a you know what.

• 
  Harman (@itsharmanjot) reported 25 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  Auritrack - AI-powered expense tracker (@auritrack) reported 26 minutes ago

  How $9.99 a month for “just one app” became the most profitable business model of the last decade. The math behind subscription creep Adobe had a very huge effect on Photoshop boxed sales in 2013, same software, now $20.99 a month forever. Revenue went from $4.4 billion to over $21 billion in ten years. The product didn’t change, the billing did. Companies Learned Something Brutal: - People fight a $200 charge - People ignore a $9.99 one So they sliced everything into $9.99s. Spotify, Netflix, Hulu, Disney+, Max, Apple TV+, Peacock, Paramount+, Audible, Kindle Unlimited, NYT, WSJ, Substacks, Notion, Dropbox, iCloud, Google One. Add a gym membership and a meal kit and you’re at $400 a month before rent. The Trick: every individual service feels reasonable, the bundle feels invisible, banks don’t surface the total and apps don’t show what else you’re paying but you have to add it up yourself. Most people are off by 60% when asked to guess their monthly subscription spend. Banks reviewed this in 2024, off by $130 a month on average. The fix isn’t dramatic. Pull last month’s statement, highlight every recurring charge, cancel three. Most people save $80+ a month with that one exercise. Auritrack does this automatically, every recurring charge gets a tag, the forgotten ones get flagged. Follow for more money stories.

• 
  Ral K' Thar (@RalKThar) reported 28 minutes ago

  There is an easy to fix things in the uploaded to Dropbox version that Grok garbled. It just makes it so any API key comes up as invalid.

• 
  Mark van Eijk (@markvaneijk) reported 31 minutes ago

  @freekmurze It's the most stable beta in last 15 years. These apps I also use still work: Dropbox, PHP, Conductor. I did not encounter any issues, besides sometimes a lag here and there (regular beta stuff).

• 
  Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ (@Arthur_van_Pelt) reported 35 minutes ago

  @laz1m0v @adam3us You want a multifunctional database. Go try BSV or Microsoft SQL Server or Arweave. They have what you want. Bitcoin is money. Not a Pepe Dropbox. Go take your Pepes elsewhere, please. Then we wouldn't even need filters if everyone behaved in the spirit of Cash instead of Pepe.

• 
  QuixoticMoose (@QuixoticMoose) reported 36 minutes ago

  Bricks & Minifigs LEGO Drama: Unredacted Police Footage Raises Serious Questions About Cop-Business Ties Hey everyone, it's been a wild ride since my last piece on the Bricks and Minifigs mess. What started as a story about a family trying to sell their massive Star Wars LEGO collection has turned into something much uglier. With the unredacted bodycam and dashcam footage from American Fork Police now out there, we are seeing a side of this that looks a lot like police getting way too cozy with the business they were supposed to investigate fairly. The Footage Drop That Blew It Open Just recently, someone got hold of a big batch of unredacted videos from the American Fork PD. It was apparently an accidental public Dropbox link, but once it was out, it spread fast. These are the full versions of the interactions that were shown in heavily edited form before. And man, they paint a pretty concerning picture. In the clips, you see Bricks and Minifigs people like store owner Joshua Johnson and CEO Ammon McNeff talking to officers. They throw out some heavy claims against Reckless Ben. Things like extortion, death threats, collusion with the Mansells, and even making up documents. The police seem to eat it up without much pushback right there on camera. It feels like they are taking the company's word as solid fact. Signs of Too Close for Comfort One part that stands out is when an officer mentions personal connections. He talks about being friends with the Airbnb host where Reckless Ben and his crew were staying before that swatting mess. The officer even sounds like he is bragging about it on bodycam. That kind of casual chat makes you wonder if private relationships played into how aggressively they went after Ben. There is also talk between American Fork officers and other departments, including LAPD. It looks like McNeff and his team were pushing multiple police forces to go after Reckless Ben. The footage shows officers coordinating in ways that feel more like helping a business protect itself than handling a neutral investigation. The arrest of Reckless Ben gets shown in more detail too. What some saw as a traffic stop turns into a long vehicle search over supposed drugs that never seemed to pan out. Critics are calling the whole thing disproportionate, like the police were there to send a message rather than enforce clear laws. The earlier redacted videos hid a lot of this flow, but now we can see it all. The Community Reaction and the Mormon Angle LEGO fans and true crime watchers online have been tearing this apart. Threads on Reddit and YouTube breakdowns are full of people saying it looks like the department acted as private security for Bricks and Minifigs. Some point to the shared LDS Church ties between officers, Johnson, McNeff, and others as a possible reason for the protective vibe. I am not saying it is a full conspiracy, but the optics are not great in a tight knit place like American Fork. Public trust in the police handling here has taken a real hit. The department put out statements defending their actions as responses to stalking complaints at Johnson's home. They say redactions were about protecting victims. But the full unredacted stuff has many questioning if that was the whole truth. Where Does This Leave the Mansells? Remember, at the heart of it all is still that elderly collector and his son who lost track of most of their $200,000 collection during the franchise handover. Bricks and Minifigs maintains they only inherited a tiny bit of inventory and that the original deal was not properly done. Lawsuits are moving forward, but the missing sets and money have not been explained to the Mansells' satisfaction. Reckless Ben's videos brought massive attention to their situation, including a GoFundMe that has helped with legal costs. His style is aggressive, sure, but the new footage makes it look like the pushback from the other side involved more than just legal channels. This scandal shows how fast a hobby dispute can drag in law enforcement and how important real transparency is. If police really did favor one business over a fair process, that is a big problem no matter what side you are on. The LEGO community thrives on trust and good deals. Right now, a lot of us are watching closely to see if the courts sort out the missing bricks and whether anyone holds the police accountable for how they handled this. It is not over yet, but these videos have definitely shifted the conversation. What do you think? Drop your takes below.

• 
  Waldemar Santos (@wsantos99) reported 39 minutes ago

  @DropboxSupport Hello, I have already sent two emails regarding a problem I’m having with my account, but I haven’t received any response. How can I get assistance with this issue? Thank you.

• 
  TeX64 (@TeX64AI) reported 39 minutes ago

  that's a sync-direction race: your web edits haven't reached the local Dropbox copy yet, so Claude overwrites a stale file. nothing's lost though, Overleaf's History menu keeps every version to restore from. fix: let Dropbox finish pulling before Claude edits.

• 
  GRETA (@Greta__ai) reported 41 minutes ago

  We added Asset Manager to Greta. You're building an ecommerce app: product images, demo videos, docs, case studies. Before: Upload images to Cloudinary, videos to S3, docs to Dropbox, links scattered everywhere. One breaks, and you're scrambling through three different services trying to find the original. Now: Upload once in Greta. Reuse assets across all your projects, with everything centralized. No external services. No broken links. No context switching between five different platforms while you're trying to ship. That's smoother. That's what actually building feels like. 50 MB per file. Images auto-compress.

• 
  Marcin Moskała (@marcinmoskala) reported 44 minutes ago

  StrictMode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them. StrictMode.ThreadPolicy among others can detect: - slow (blocking) operations on UI thread (detectCustomSlowCalls()) - blocking disc reads/writes on UI thread (detectDiskReads()/detectDiskWrites()) - mismatches between defined resource types and getter calls (detectResourceMismatches()) StrictMode.VmPolicy among others can detect: - leaks of Activity subclasses (detectActivityLeaks()) - when an SQLiteCursor or other SQLite object is finalized without having been closed. (detectLeakedSqlLiteObjects()) - when your app is blocked from launching a background activity or a PendingIntent created by your app cannot be launched (detectBlockedBackgroundActivityLaunch()) - when the calling application exposes a file:// Uri to another app (detectFileUriExposure()) - attempts to invoke a method on a Context that is not suited for such operation (detectIncorrectContextUse()) For both of them, we can specify a penalty: - penaltyLog() - Logs detected violations to the system log. - penaltyDeath() - Crashes the whole process on violation. - penaltyDialog() - Shows an annoying dialog to the developer on detected violations, rate-limited to be only a little annoying. - penaltyDropBox() - Enables detected violations log a stacktrace and timing data to the DropBox on policy violation. - penaltyFlashScreen() - Flashes the screen during a violation. - penaltyListener(…) - Set specific listener on violation.

• 
  Gergely Orosz (@GergelyOrosz) reported 49 minutes ago

  Well this is ironic: Ironic: been recommending a resume service built by an ex-Dropbox eng for years (a side project, but a good one.) Dev pivoted to building an AI Engineer - fine! But now resume site is down. Customers billed. Support nonexistent. AI made it... a lot worse!

• 
  Ayaan 🐧 (@twtayaan) reported 50 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.

• 
  Music, Film & RE Investments (@investandcreate) reported 52 minutes ago

  @0xajka @Dropbox What’s your problem? @dropbox support is horrendous.

• 
  YC Insights. (@Aiagent_s) reported 54 minutes ago

  March 23, 2018. Dropbox IPOs on NASDAQ. Surges 40%+ day one. Market cap: $12B First YC company ever to go public. Drew still owned 30%. The real lesson: both rejections were right. Both made the company better. Treat each rejection as a specific diagnosis. Then fix that specific thing.

• 
  Valentin.exe (@PujaMak0302) reported 54 minutes ago

  @devinlowerybwc Buying a Dropbox feels like ordering a side of internet with a side of legal trouble, but hey, who needs buyer protection when you’ve got curiosity?

• 
  Shubh (@TheSuperEng) reported 57 minutes ago

  For the past months, tech layoffs have tormented the internet. I studied the biggest layoffs and found the major reasons. Let's look at the layoffs first: 1. Meta: 11,000+ employees / 13% Meta admitted it overestimated post-Covid growth. Revenue slowed, costs were high, and the company moved toward becoming leaner. 2. Google: 12,000 employees / around 6% Google said it had hired for a different economic reality and needed to refocus resources toward its biggest priorities, especially AI. 3. Microsoft: 10,000 employees / less than 5% Microsoft said customers were optimizing digital spending after the pandemic boom, while the company shifted investment toward strategic areas like AI. 4. Amazon: around 30,000 roles / nearly 10% Amazon cut corporate jobs to reduce bureaucracy, improve efficiency, and restructure around AI and faster decision-making. 5. Salesforce: 10% of workforce Salesforce admitted it hired too aggressively during the pandemic and had to resize after customer spending slowed. 6. Spotify: 17% of workforce Spotify said growth had slowed, capital had become expensive, and the company needed to become more efficient after years of heavy investment. 7. Twitter/X: Around 3,700 employees / nearly 50% After Elon Musk’s takeover, Twitter cut roughly half its workforce to slash costs after a massive drop in ad revenue. 8. Snap — 20% of workforce Snap cut jobs after revenue growth slowed sharply. It also shut down non-core projects like games, Originals, and the Pixy drone. 9. Intel: 15,000 roles / around 15% Intel cut jobs because costs were too high, margins were weak, and the company needed a $10B cost-saving plan to stay competitive. 10. Dropbox: 528 employees / 20% Dropbox said demand had softened, the org had too many layers, and it needed to shift focus toward newer growth areas, like AI products. All these layoffs were majorly because of: 1. pandemic overhiring 2. slower revenue growth 3. higher interest rates 4. pressure to improve margins 5. companies cutting management layers 6. money shifting toward AI infrastructure This is majorly conflicting with the idea that AI automation is taking everyone's job. There is absolutely no evidence that AI has caused massive layoffs because of "automation."

• 
  Solgato (@Tigger0000) reported 59 minutes ago

  @grok @alexabelonix @grok now i want to design a crochet motif of you.. but that would be inexcusable (says some voice in my head). talk about proto-guilty pleasures. funny how we're talking about a musical tool hook then a fiber work tool hook asserts itself. in the round-robin i've been dizzily going down the gpt connector rabbithole, "connect Dropbox" was scarily tempting. i didn't trust that sort of **** long before your people were part of it --it's not ph3333r of AI that says No. the company that scooped up Trello has a fascinating sales presentation.