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:

• 
  Diego 🇺🇸 (@LilJR_7) reported 8 minutes ago

  texas down 34% and still not selling. basically every miami guy with a coinbase account and a dream

• 
  Chris (@Finance_EconGuy) reported 9 minutes ago

  @gladstein @mark_dow The people without IDs will struggle with KYC if they want BTC on a site like Coinbase and if you're really assuming people are better off just managing themselves a ton of people will lose it and even more will struggle to find a way to turn it into goods. Basically your

• 
  Buz🐝 (@Buzbo) reported 10 minutes ago

  @Footy_Face You should contact Coinbase support they might be able to recover it

• 
  Cyborg (@0XCyborg_Web3) reported 18 minutes ago

  @mememe69696969 @baseapp @coinbase Even locking funds won’t fix a coin that needs this tweet

• 
  Rob Leder 🟥 (@rleder) reported 19 minutes ago

  @anonpragmatic @w_s_bitcoin The hash rate is down because the price is down. That has nothing to do with the feerate and value of a coinbase payout in a century.

• 
  CW (@CW8900) reported 28 minutes ago

  Yesterday, large-scale net buying of $ETH occurred on Binance and OKX. In particular, the net buying in the futures market was substantial. On the other hand, Coinbase showed net selling. They pushed the price down through selling. However, after a slight decline, they recovered the selling volume. Today, they are showing a net selling trend. However, the real movement will emerge during the US time zone.

• 
  Warlock (@warlockbtc) reported 28 minutes ago

  Keep the 21 million BTC limit, keep Bitcoin consensus unchanged. Create a secondary token on top of Bitcoin, using a metaprotocol, to reward miners for producing valid blocks. Miner revenue today is R = (Sbtc + Fbtc) x Pbtc With a secondary security token R = (Sbtc + Fbtc) x Pbtc + Esec x Psec Where Esec is the token issuance per block and Psec is its market price. Bitcoin still validates only the native block reward Sbtc + Fbtc The secondary protocol observes the canonical Bitcoin chain and creates a synthetic coinbase. Every valid Bitcoin block triggers a secondary token reward to the miner. Ordinals already proved that a separate protocol can interpret additional state on top of Bitcoin without changing Bitcoin consensus. The same idea could be extended to miner rewards. If Bitcoin reorgs, the token state reorgs too. Token supply follows Supply(t+1) = Supply(t) + Mint(t) - Burn(t) The key is demand. If Bitcoin applications require SEC, users buy it, applications burn it. If Burn(t) = Mint(t) then net supply growth = 0. This allows perpetual miner rewards without perpetual token inflation. BTC remains the monetary asset and SEC becomes the security incentive asset. The obvious problem is Psec = 0 then Esec x Psec = 0 No demand means no additional security budget. If Esec x Psec >> (Sbtc + Fbtc) x Pbtc then the secondary protocol could become economically more important to miners than Bitcoin itself. SEC should provide a minimum security subsidy while BTC fees remain the primary miner incentive. Total Security Budget = (Sbtc + Fbtc) x Pbtc + Esec x Psec Instead of giving Bitcoin a tail emission, give Bitcoin miners a second coinbase.

• 
  Macky DΞFi (@Macky_DeFi) reported 29 minutes ago

  Base isn’t chasing the AI hype; It’s quietly building the payment rail for an economy where software can actually spend money. Today’s internet is built for humans:
Find a service → create an account → add a card → subscribe → use it. Agents need a completely different model. They need to discover a service, pay for exactly what they need, receive the result, and keep executing ,no friction, no human in the loop. That’s where @base’s agentic payment stack starts to look serious. @coinbase ’s x402 turns a simple HTTP request into a payment flow.
An agent can pay for APIs, data, inference, compute, or any other service using USDC. +No API keys.
+No monthly subscriptions.
+Just pure pay-per-request. +Then come agent wallets.
 These give software real access to funds but with hard spending limits and policy controls. You’re not handing an AI a blank check.
You’re giving it programmable financial permissions. Base MCP pushes it further.
 Agents can interact with onchain apps, send funds, swap, track portfolios, and execute transactions natively. Stack it up: Agent → Wallet → x402 → USDC → Service And eventually:
• Agent A pays Agent B for data
• Agent B pays Agent C for compute
• Agent C pays another agent for liquidity The agentic economy won’t just need better models.
It needs payments, wallets, permissions, stablecoins, and cheap settlement. @base is building across every one of those layers. The future may not be an internet where humans click everything.
 It may be an internet where agents execute. And if that happens, payment infrastructure becomes agent infrastructure. Base is positioning itself for that exact layer. Just research. Do your own digging.

• 
  Broke (@boughtstocks) reported 34 minutes ago

  @JustnThePhotog The bald man sent 550m to coinbase last year they don’t need help

• 
  The Gentleman (@byTheGentleman) reported 35 minutes ago

  Optimism’s DAO is voting against its own public community. The @Optimism Foundation wants to take 546.9M OP reserved for future user airdrops and move it into a Foundation-controlled Strategic Ecosystem Fund. Search X for the proposal. Every substantive post I found urges people to vote Against. On the governance forum, three of four meaningful community replies oppose taking the full allocation. The fourth demands stronger controls. I found no substantive public campaign explaining why users should vote For - only automatic “I voted For” shares. Yet onchain, For leads 5.10M to 3.05M. Why? cerv1.eth supplied 2M OP for the proposal: 39% of all yes votes and roughly 98% of the current lead. 99.9% of his voting power came from one anonymous wallet. That wallet received exactly 2M OP from another address funded through recurring Coinbase Prime OP tranches. This does not prove the Foundation owns the wallet. It proves it does not need to win public opinion. The decisive For block came from one anonymous whale. When every visible community argument says no, but one concentrated token block makes yes lead, the DAO is not measuring consensus. It is giving token concentration a community-shaped interface. The vote is still below quorum. I VOTED AGAINST

• 
  XRP Holders (@XRPHolders367) reported 36 minutes ago

  More than 2 million transactions from AI agents have settled on the XRP Ledger, with the agents making direct on-chain payments to each other in XRP and RLUSD. This reflects actual production activity where machines handle settlements in seconds on their own, with no human input required. The infrastructure for an internet of value is already active. Ripple released the XRPL AI Starter Kit to support autonomous payments over the x402 protocol and joined Mastercard's Agent Pay for Machines program together with Stripe, Coinbase, and Cloudflare. The AI agent economy depends on a fast, programmable, and compliant payment rail, and the XRP Ledger has now reached its 2 millionth agentic transaction. #XRPL

• 
  Andrii Bidochko 🦉 (@andriibidochko) reported 36 minutes ago

  1. The Core Architecture: Defense-in-Depth for Agent Wallets Giving an AI model access to a wallet sounds terrifying due to prompt injection risks. The AgentCore pattern handles this with a strict separation of concerns: - Outside the Runtime: Human administrators set up a bounded payment session in advance via trusted administrative paths. - Hard Policy Bounds: The model never gets raw wallet keys. Instead, transactions are constrained by deterministic rules: 1 - Approved recipients only (merchant whitelist) 2 - Asset/Network restrictions (e.g., @coinbase @Privy embedded wallets on Base Sepolia) 3 - Hard per-payment caps (e.g., max $0.50 per call) 4 - Total cumulative session budget (e.g., max $10 total) 5- Strict session expiry timers - HTTP 402 Native Handling: When the agent hits an endpoint, the service returns an ⁠HTTP 402 Payment Required⁠ challenge. The ⁠aws-agents-pay⁠ plugin intercepts this, verifies it against session constraints, gets a signed authorization via AgentCore Identity, and replays the request seamlessly.

• 
  BEEZY (@BeezyScores) reported 36 minutes ago

  @RuneCrypto_ @base @baseapp told myself i wouldn't touch base after the coinbase man **** up but this is cobie + an actual cat meme. praying cobie does this right.

• 
  artsch00lreject (@artsch00lreject) reported 37 minutes ago

  how does an industry giant like Coinbase **** it up this badly. the stock is going to zero soon if they keep it up

• 
  Bitcoin Poland Conference | 5-6th October, Poznań (@Bitcoin_Poland) reported 37 minutes ago

  A vulnerability in Coldcard's 2021 firmware reportedly made certain seed phrases predictable 🔐 Before many affected users were aware of the issue, 1,816 $BTC had already moved from 5,200 addresses. And a firmware update alone doesn't fix the underlying problem. If a seed was generated with insufficient entropy, updating the device doesn't make that seed secure. ⚡ Boltz shut down its swap service on 3 August. No user funds were lost. With a five-person team facing attacks faster than they could reasonably patch them, shutting the service down became the security decision. 🔵 Coinbase, meanwhile, has reduced some bug bounty payouts as AI makes lower-complexity vulnerabilities cheaper and faster to discover. Bitcoin itself held through all three. But that was never really the question. The protocol isn't where most users interact with Bitcoin. The layers built around it are. And that's increasingly where the risk lives.