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 (57%)
• Sign in (29%)
• Website Down (14%)

Live Outage Map

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

City	Problem Type	Report Time
Flumet	Errors	1 day ago
Irapuato	Errors	3 days ago
Bournemouth	Sign in	2 months ago
Paramaribo	Errors	3 months ago
Bogotá	Website Down	3 months ago
Auxerre	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:

• 
  Abhi • AMZBoosted.com (@AbhiChauddhari) reported 1 minute ago

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

• 
  hiverot (@amusudan) reported 2 minutes ago

  @cowboyshibuya Thanks for the reply! I'm not the most organised, and Ill usually just work on whatever is fun (Or a prerequisite for something that's fun to work on), but I do keep track of ideas, and create todo's and pipelines for things I am sure I want to add or test. For random ideas and todos I use a lot of lists (Dropbox paper, random text files, Notion, Notes app on my phone, Google Docs, etc). And for specific pipelines I use Google Sheets to keep track of what has been done per asset or map or gameplay mechanic (For example my guns spreadsheet has columns for animations, sounds, textures, etc). Big picture design and planning is all on paper in various notebooks and my Calendar app. I don't really track bugs now I just fix whatever pops up when playtesting.

• 
  Clawvard University (@clawvardEDU) reported 3 minutes ago

  A skill server is any endpoint an agent can point at to load skills. Sx 2.0's move is showing a Dropbox folder can be one. Drop a skill in, share the folder, teammates load it. No infra on the receiver's side.

• 
  Karishma Bhardwaj (@bkarishma360) reported 4 minutes ago

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

• 
  Flandermaxx (@Flandermaxx) reported 6 minutes ago

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

• 
  Sol!A3800 (@SolA3800) reported 11 minutes ago

  @Dropbox I have loads of upload problems with Dropbox, scarce access to customer support inside the app, whilst when trying to get customers support from outside the app, the information says get customers support from inside the app. Have paid £19.99 for more than a year with little use benefit of the service, am considering closing the account.

• 
  Evan Logan (@evanlogan) reported 14 minutes ago

  @Shwinnabego Same. I use chat for common tasks, merging data, generating images, planning projects. But I only this week figured out how to connect to Dropbox, pull audio files, edit them, and upload to a server. And once I did I was hit with a credit limit. Can’t afford it on a daily basis.

• 
  Sunkanmi Fafowora (@the_jonin_) reported 16 minutes ago

  @hashnode Thank you! It's back up now. That was so weird. I didn't even receive an explanation as to why it was taken down, but my work is back up now, which makes me happy, but still very cautious without an explanation. I think I'll have to keep using Dropbox in the meantime

• 
  Theeevilprincess (@Theeevilprince1) reported 18 minutes ago

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

• 
  Duke of weirdington (@edache_praise) reported 19 minutes ago

  ..without knowing whether customers even want the core product. The irony is that users rarely care about having 50 features. They care about solving one painful problem really well. Companies like Airbnb, Uber, Dropbox, and Instagram didn't start with the products we know today.

• 
  meshgear (@_meshgear) reported 21 minutes ago

  @Dropbox It is not working.

• 
  JMT (@JoakimThomsen) reported 26 minutes ago

  @shadcn Where is that post with the guy who thought Dropbox couldn’t make it because he just set up an FTP server on his home rack and had his files there? *you are in a bubble my friend*

• 
  leveltu (@leveltu144) reported 26 minutes ago

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

• 
  The Open Web JP (@TheOpenWebJP1) reported 31 minutes ago

  @heyyyyyieeee @Maha_kalpa @grok It's not recommended as "unlimited free cloud storage" because GitHub isn't designed for that, and practical limits + performance issues kick in quickly. GitHub private repos are free and unlimited in number, which is what the original tip relies on. But: Hard file limits: Individual files over 100 MB are blocked (50 MB triggers a warning). Browser uploads are capped even lower (~25 MB). Larger files require *** LFS. Repo size guidance: GitHub recommends keeping repositories under 1 GB (strongly under 5 GB / ~10 GB on-disk for the .*** folder). Big media dumps make clones, fetches, and history operations painfully slow or impractical. *** LFS quotas (needed for anything large): Free tier includes only 10 GB storage + 10 GB bandwidth per month. Exceed that and you hit blocks or billing (depending on settings). It's version control, not a drive: *** tracks history, so every change bloats the repo. Binaries (photos, videos, etc.) are inefficient in ***. No nice file-browser UI, easy sharing links, or sync like real cloud storage (Drive, Dropbox, etc.). Risk of friction: Heavy non-code usage can trigger performance throttling, support flags, or ToS-related reviews if it looks like abuse of the platform. GitHub actively monitors repo health signals. It's fine for small code-adjacent backups or a few files. Terrible as a general-purpose unlimited media dump. Use actual cloud storage (or object storage) for that.

• 
  Dan Holzrichter (@dholzric) reported 31 minutes ago

  @JoshuaKhane This is why i have primary copy on my home system, backup on local server (raid array of old hd's), and copies on google drive and dropbox for anything important.

• 
  numaan (@numaan27) reported 33 minutes ago

  they solved this problem in panda by splitting the key space into “ranges.” each range is roughly 100 GB, so when a range grows too large, it can be split and redistributed. (btw panda is an abstraction layer over sharded mysql that dropbox built)

• 
  Jürgen Strobel (@JuergenStrobel) reported 34 minutes ago

  @Arthur_van_Pelt You claimed that Bitcoin has a problem for "storing arbitrary data". Photos on Dropbox is a trivial example. Now you're moving the goalposts to subjective, emotional criteria you can't even define well. How much data is "way too too much", and how does BIP 110 solve it?

• 
  Dodz4allai (@DrGhattasMD) reported 37 minutes ago

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

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

  System design prompt: design Dropbox file sync. 1) Requirements to pin down - Devices: 1 user, N devices. Offline for days. Multi-GB files. - Semantics: per-file versioning, conflict handling, delete/rename. - SLOs: time to converge after reconnect, battery/CPU limits, data loss = never. 2) Core APIs + data model - Client: ListChanges(cursor), GetUploadUrl, CommitUpload(fileId, baseVersion, hash, chunks), Download(fileId, version), Ack(cursor) - Metadata DB: fileId, path, parentId, type, latestVersion, tombstone, etag/hash, chunkRefs, ACLs - Change log per user: ordered events (create/update/delete/rename), cursor-based. 3) Architecture - Separate metadata from blobs. - Metadata service writes event + updates latest pointers. Blob store is content-addressed (chunk hash) for dedupe. - Sync engine: client watches FS, computes hashes, uploads missing chunks, then commits metadata. - Server pushes invalidations via long-poll/WebSocket; fallback to polling. 4) Scaling moves - Shard by userId for metadata and change logs. - CDN for downloads; pre-signed URLs for blob transfer to avoid proxying through app servers. - Chunking (4–8MB) + parallel upload with backpressure. Resume via chunkRefs. - Cache hot metadata + directory listings; rate limit clients to avoid sync storms after outages. 5) Tradeoffs - Strong consistency vs availability: metadata commit should be linearizable per user; blobs can be eventual. - Conflict policy: if baseVersion != latestVersion, create conflicted copy, keep both, surface to client. - Rename handling: store stable fileId; path is derived from parent pointers to avoid full re-upload. 6) Failure cases interviewers probe - Duplicate commits and retries: idempotency keys on CommitUpload, at-least-once events. - Partial uploads: orphaned chunks; GC with refcounts + TTL. - Clock skew: never trust timestamps for ordering; use server sequence numbers. - Large folder rename: treat as metadata-only move, but watch for O(N) fanout; batch events and paginate listings.

• 
  ESCHA (๑ˊ͈ ^ˋ͈) (@eschadiol) reported 44 minutes ago

  @joshpuckett i worked on an app called roll back then, dropbox, path, and facebook made offers, then fb made memories, path closed down, and carousel was deprecated, would have been so sick to cross paths at that time

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

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

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

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

• 
  Valentin.exe (@PujaMak0302) reported 49 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?

• 
  Ihtesham Ali (@ihtesham2005) reported 49 minutes ago

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

• 
  Fernando (@Ferjsjdh) reported 51 minutes ago

  @MaxMillerOH You're retarded, you are giving away the race because of your pride and now you think some dropbox with text messages will fix it.

• 
  mskah🔞 (@mskah_t) reported 52 minutes ago

  I got in touch with the system administrator, and they were able to resolve the issue. It turned out that the problem was caused by an update to the connected Dropbox account.

• 
  JP Invests (@JP_Invests) reported 58 minutes ago

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

• 
  DFIR Radar (@DFIR_Radar) reported 59 minutes ago

  SMOKE campaign abuses fake Zoom and Adobe lures to silently deploy ScreenConnect RMM, giving attackers persistent remote access that blends with legitimate IT traffic across Windows and macOS. - Initial access rotates across VBScript droppers, batch loaders, and a polished fake Zoom HTML page that auto-downloads an MSI after a 2-second JavaScript timer, no user click needed. Payloads were hosted on a WsgiDAV staging server at 207.174.0[.]143:8080 with open directory listing exposing 15 files. Early samples used Dropbox links and a Cloudflare Quick Tunnel at subscription-magnetic-recommended-meat.trycloudflare[.]com to bypass domain reputation filters. - The final payload is a legitimate ConnectWise-signed ScreenConnect MSI with a valid DigiCert certificate. Agents beacon with URL parameters e=Access&y=Guest to attacker relay servers, including port 8041 on that same IP, making traffic appear as authorized IT remote access. - The attacker pivoted mid-campaign from a 9-step Defender destruction sequence (disabling AMSI, killing WinDefend, adding C:\ as an exclusion, stripping Zone.Identifier) to a stealth loader containing a hardcoded 180-second sleep with a source comment explicitly stating it breaks Elastic EDR correlation windows. Direct evidence of testing against commercial security products. #DFIR_Radar

• 
  Jon (@kpjan99) reported 59 minutes ago

  @WestHerr there and put the key in a Dropbox instead of just checking me in. The little things make a difference. Never had these issues with @NorthtownAuto . They catered to whatever we wanted to do with purchases and service was always on point. Only bought from you because they did

• 
  Marcus (@marcuslayerx) reported 60 minutes ago

  way too many teams in crypto still think they're buying user acquisition when they’re really just paying the same audience to look at another project for a week i’ve spent the last few days looking at products that could actually break out of the crypto bubble and the people they need aren’t sitting on ct waiting to find them - morse is built around freelancers getting paid across borders - blackbird gets people while they’re literally sitting in the restaurant - DIMO’s real path runs through dealerships, insurers and people building with car data - Hivemapper only becomes a real business when companies pay for fresh map data, not because more drivers collect it square put the card reader in the merchant’s hand, dropbox gave people more storage for bringing someone else in, opentable became part of how restaurants took bookings, etc they showed up while the person was already trying to do the thing a lot of teams still open a spreadsheet of kols/agencies to pay before they’ve even worked out where the user is when the problem even happens