Coinbase 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.

Coinbase Issues Reports

Latest outage, problems and issue reports in social media:

• 
  (Moldz23) (@RMoldz23) reported 59 seconds ago

  @zackdozes @coinbase Coinbase wants giant listing fees ! **** them ! Nobody needs them

• 
  ᑭᖇᗩY乙 (@prayz_dev) reported 2 minutes ago

  I keep coming back to Injective, and honestly it’s less about any single announcement and more about how consistently they’ve been building while nobody was really watching. Think about how most chains get attention. Something ships, CT goes wild for 48 hours, then it fades and everyone’s onto the next thing. Injective has never really played that game. It just keeps stacking wins quietly, month after month, and it wasn’t until I sat down recently and actually listed everything that’s happened this year that I realized how much ground they’ve covered. Native EVM went live, fully built into the core chain instead of being some separate side-project bolted on for optics. That alone would’ve been a big deal for most projects. But then INJ itself migrated off the old wrapped token standard onto that native layer, Coinbase supported it fully, and within weeks you had actual institutions not crypto-native funds, actual industrial companies like LG CNS and POSCO running live trade finance data on the chain. That’s not a partnership announcement with a logo and a quote. That’s someone’s real business process running on Injective’s rails. What gets me is how none of this feels engineered for a headline. There’s no big reveal moment, no countdown timer, no “the wait is over” energy to any of it. It’s just… shipped. Injective Mint quietly entered private beta so institutions can tokenize real assets without needing a dev team. The MCP Server went live so AI agents can actually place trades instead of just narrating market conditions to you. Regulatory filings went out in both the US and Europe at basically the same time, which tells you this isn’t a team hoping regulation goes away, it’s a team building for a world where it doesn’t. I think what’s actually happening is Injective bet early that the next real wave in crypto wouldn’t be another retail trading cycle, it would be institutions quietly finding infrastructure solid enough to trust with real financial processes. And instead of talking about that thesis, they just kept building toward it, sprint after sprint, upgrade after upgrade. Maybe I’m reading too much into a string of updates. But when I actually stack the timeline up, it stops looking like a coincidence and starts looking like a pattern. And patterns like this are usually the ones people only notice in hindsight. Watching where @injective goes from here. injective-protocol:native

• 
  Rosetina Degen 🚢🎒 (@rosetina_degen9) reported 4 minutes ago

  🦋 Two weeks ago,@Morpho shipped the fixed-rate product that previous generations of onchain lending could never make work: Morpho Midnight. Fixed-rate lending onchain already failed once. The 2020–2022 wave (Yield, Element and others) never found real product-market fit. Looking back, most of those products struggled for four clear reasons: 🔹 Liquidity fragmentation: capital had to be locked into one specific maturity bucket just to quote a rate 🔹 Idle capital: if your offer wasn’t matched, the money earned nothing 🔹 No institutional demand: the natural buyers of term credit simply weren’t onchain yet 🔹No secondary market: once matched, positions were locked with almost no clean way to exit early Midnight addresses all four at the mechanism level. One unit of USDC can now quote across multiple maturities at the same time. Only one offer gets filled, so capital isn’t forced into fragmented buckets. Until a match happens, that same USDC continues earning variable yield on Morpho Blue. Positions are fungible zero-coupon-style units that can be traded before maturity. And this cycle the demand side actually exists - institutions are looking for predictable term structures, and distribution rails (Coinbase, Kraken, Bitwise, SG-Forge and others) are already live around Morpho. The earlier products died because they launched before the demand was ready and shipped with capital-inefficient mechanics. Midnight fixed the mechanism problems, and the institutional rails are present this time. Still extremely early. The number to watch is active loan growth.

• 
  severino (@severino_wm) reported 6 minutes ago

  don't have short memory brian ****** up with the trenches last month, we can send this $shitcoin to millions recieve a lot of coinbase stock and nuke that **** remember, coinbase is trash

• 
  Jack699.base.eth (@yike699) reported 7 minutes ago

  2/9 Tokenized stocks are the biggest unshipped thing Base has been working with @coinbase to bring US equities onchain, and Sir Jesse said it's coming very soon, with tooling for lending, borrowing, and memes on top of those stocks. The framing he used: roughly 4 billion people worldwide have no brokerage access at all. Why builders should care: equities become collateral. The second they're composable, options, index vaults, structured credit, and earnings markets all become buildable. Two teams on the call already staked claims here. Building that layer before launch is the asymmetric move.

• 
  Tails (@EatTradeSleep) reported 9 minutes ago

  dear Brian from Coinbase, @brian_armstrong i’m not even going to pretend i’m here to “build a relationship” or “collab” with you. i’m here to beg. you currently have 14 billion dollars worth of airdrops FOURTEEN at this point, you’re basically running a small financial institution 😭 (literally) and somehow, despite the fact that there are billions of beautiful little airdrops sitting in your wallet, i am out here fighting for my life without one. i have checked your wallet. i have checked it again. i have refreshed it. i have stared at it long enough to start questioning my life choices. this is the wallet of a man who clearly has too many airdrops. and this is the wallet of a man who could change my life with literally one click. i’m not asking for two. i’m not asking for three. i’m not even asking for one of the “good ones.” give me the airdrop that you think is ugly. give me the one nobody wants. give me the one with that’s afraid to amplify memecoins. give me the one that looks like he hasn’t slept since 2021. I WILL TAKE HIM. i will love him. i will protect him. i will give him a warm place in my wallet. i will introduce him to everyone as “my airdrop.” i will never sell him. okay maybe i’ll think about selling him. but i won’t. probably. Brian, you have billions. i have zero. this is not financial advice. this is a humanitarian crisis. i am simply asking you to redistribute some of your wealth. one airdrop. that’s all. one tiny little drip of the faucet. one bald businessman. one unemployed looking Jesse pollak. please. i have done everything a respectable man should do. i have liked the tweets. i have replied. i have supported the culture. i have watched from the sidelines. i have admired the Base summers from afar like a peasant looking through the window of a billionaire’s house. but now i have decided to abandon all shame. i am begging publicly. in front of everyone. with absolutely zero dignity left. Brian, please. look into your heart. look into your wallet. look at those billions in airdrop funds staring back at you. then look at me. a humble man. a broken man. a man who simply wants to become an airdrop recipient. you don’t need 14. you only need 13. i don’t need 12. i only need 1. the math is literally perfect. 14 - 1 = 13 13 for you. 1 for me. everybody wins. i’m even willing to call it a charitable donation. you can put “helped a financially irresponsible man acquire a jpeg” on your résumé. tma, i am not above begging. i am below begging. i have entered a new socioeconomic class called professional stonkbroker beggar. please save me. give me one. i promise to behave. probably. thank you for your consideration. i will be checking the wallet every 4 minutes. respectfully, your future airdrop recipient 🫡

• 
  STARLAND (@digitstarway) reported 11 minutes ago

  @coinbase can not sign in

• 
  STRANGE SOUND 🃏 👁️ (@whyalwaysellis) reported 15 minutes ago

  FERMAH IS BUILDING PROTOCOLS FOR HUMANS WHO AREN'T THERE ANYMORE ​There’s a silent assumption baked into almost every protocol engineer’s workflow, state belongs to a session, and finality requires a human to sign off via a wallet. ​Because we take this for granted, we build applications that are fundamentally broken for autonomous agents. It’s not just that agents have a hard time using them, it’s that the composition layer makes these apps entirely unreachable to them. You can't patch your way around it, because the flaw is baked into the foundation. ​Why slapping on an SDK after the fact always fails ​The common belief is that "agent support" is just an SDK layer you bolt on after the core architecture is done. That only works if a human user session and an autonomous execution sequence are identical. They aren't. ​A traditional user session assumes someone is sitting there watching the screen. Every single downstream choice how state persists, how permissions are handled, how finality is reached inherits that assumption. ​An autonomous agent doesn’t work that way. There is no wallet popup to trigger the next step. There is no session boundary to maintain continuity between actions. No amount of frontend tooling can fix a mismatch that deep. We are using the wrong building blocks. ​MCP servers are table stakes now ​The reality of how software is consumed has shifted. Model Context Protocol (MCP) servers aren't a nice-to-have convenience feature anymore; they are a first-class integration requirement for any modern, agent-native application. ​If your app doesn't have a native agent interface, it’s not going to be adapted it’s going to be bypassed completely. Look around: Coinbase and MoonPay are already rolling out agentic wallets, and protocols like x402 are paving the way for machine-to-machine payment rails. The agents are already live and moving. Meanwhile, most protocols are sitting around waiting for humans to click buttons. ​When you try to route real-world, agent-driven execution sequences across live protocols today, you hit the same wall every time. It’s rarely a lack of agent capability or missing tooling. It’s the protocol's built-in assumption that a human is supervising. In most cases reviewed in production, confirmation-dependency is where the entire process grinds to a halt. ​The 4 design choices that actually matter for agents ​If we want protocols that agents can actually use continuously and without human babysitting, we have to make four load-bearing design decisions right at the protocol level: ​Transfer execution context without session continuity: Step 3 needs to instantly know what Step 1 resolved, even though no active session connects them. This has to be specified at the protocol level it’s an architecture problem, not a caching fix. ​Scope permissions per execution sequence, not per wallet: An agent moving across protocols needs explicit, fine-grained boundaries for this specific sequence, rather than relying on historical wallet-wide approvals. ​Pre-resolve branching logic: If an agent hits a price shift, a failed route, or changing conditions mid-flight, it can’t pause to ask a human what to do. Handling ambiguity ahead of time is a design requirement, not a runtime afterthought. ​Decouple finality from wallet interactions: If settlement requires a human signature, your workflow isn’t autonomous. It’s just automated right up until the final hurdle, where it stalls out completely. ​The protocols that make these four decisions explicitly at the design phase are going to own the entire execution surface we're building right now. ​Those that defer these choices will soon realize their "agent layer" is nothing more than a cosmetic wrapper over a deeply human-centric architecture. ​It’s worth asking ourselves: How many protocols out there have actually made all four of these decisions? And how many haven't even realized they missed them yet?

• 
  Heyblade999 (@Heyblade999) reported 15 minutes ago

  Happy Sunday my Boys!!! Every Weekly prep starts with the underlying asset, Spot bitcoin:native , and seeing what they are about. We can clearly see a lil interest coming in from Coinbase and OKX coming in on last week's move up. For me, there are these little things that could already be a warning sign or don't mean much in the end. We're gonna find that out, but on Bybit Spot, you have seen the biggest 30 min delta inflow change on the Friday's market close candle. Stuff like that means people without patience are starting to chase the price. They had all moved 5 Higher Low Retests and bought the breakout. Be careful when **** like this starts to appear. Become cautious.

• 
  Vinay K Abburi (@vabburi) reported 19 minutes ago

  @CoinbaseSupport @coinbase I need executive escalation on an unresolved unauthorized fiat-withdrawal recovery case. Coinbase confirmed in writing that my account was accessed through a session-token compromise: no new login, no new 2FA event, and a previously authenticated session was reused. During that compromised session, a new Green Dot payment method was added and four unauthorized fiat withdrawals totaling $16,970 were completed. Green Dot has confirmed the receiving account was opened using my identity without consent and says funds can be returned only if Coinbase, as the originator, provides a Letter of Indemnity or equivalent recovery documentation. Coinbase has not provided payment rails, trace numbers, originating processor details, or a clear policy/legal basis for refusing institution-to-institution recovery. I can provide all formal complaint, Green Dot, Police report, CFPB, and Coinbase case numbers by DM to verified official support only. Please escalate to Fraud Recovery / Payments Operations for resolution.

• 
  kenny7334 (@chima7334) reported 19 minutes ago

  @VuoriTrading I was actually having doubt of the coin because its not following liquidity, it has broken all the liquidity laws, infact d reason I still hold it is because I just feel coinbase are not stupid listing it

• 
  AlfRed (@Alake99999) reported 24 minutes ago

  @Eze_Wilberforce One message is easy to ignore. Thousands of them create real pressure. Now picture this: Coinbase, Ripple, Stand With Crypto, CryptoLaw, the biggest BTC, XRP, ETH and SOL accounts, and tens of thousands of regular people all pushing at the same time. That’s how we make the CLARITY Act impossible for the Senate to ignore 🇺🇸🔥 This time we do it together. No one sits on the sidelines. Share it. Contact your senators. Let’s go get those 60 votes 🫡 #ClarityAct

• 
  cenger (@cengerus) reported 27 minutes ago

  @CryptoLakhan I'm trying to verify Coinbase, but it's trying to connect to a different wallet it created on the web, instead of the Coinbase wallet extension in the browser. Has anyone else encountered this problem? Has anyone fixed it? How did you do it? The AI ​​isn't working properly.

• 
  Shire BIP110 (@Shireh0dl) reported 28 minutes ago

  @4moonsettler It'll start lower and increase, like these things always do. How is it impossible to coordinate? The mining pools go for it, blackrock, coinbase, and Core. What do you do?

• 
  Marc Baumann 🌔 (@marcb_xyz) reported 31 minutes ago

  The concentration problem. Coinbase custodies 9 of 12 US spot Bitcoin ETFs. It holds 84% of all ETF-linked Bitcoin, roughly $77 billion. It also custodies 8 of 9 spot Ethereum ETFs. Regulators have flagged this as systemic risk. ETF issuers are actively diversifying.