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:

• 
  USB (@a_seven_life) reported 8 minutes ago

  AI x crypto finally found a use case that doesnt make me want to walk into the sea machines paying machines AWS just launched Bedrock AgentCore Payments with Coinbase and Stripe and the real story is not “agents can buy stuff now” cute the real story is the web is getting a payment layer for non-human users agent needs an API call? pay needs premium data? pay needs an MCP server? pay needs another agent to handle one cursed little subtask? pay all inside the task loop request resource get HTTP 402 read payment terms pay in USDC send proof continue thats very different from the human internet humans subscribe agents meter humans browse agents call humans compare pricing pages for 17 minutes open six tabs then forget their password agents just hit the paid endpoint 900 times if you let them and this is not just theoretical hand-waving anymore AWS is plugging x402 into AgentCore Coinbase says agents can discover services, make micropayments and keep moving AgentCore Gateway has access to Coinbase’s x402 Bazaar MCP server 10,000+ pay-per-use endpoints aka not just “agent has wallet” more like agent has wallet agent has marketplace agent has budget agent has receipts agent has a very dangerous little shopping habit beautiful slightly cursed and suddenly stablecoins look useful in the least cringe way possible not for buying coffee please stop trying to make coffee the main character but for tiny, fast, programmable payments between services $0.01 for an API call $0.003 for a data snippet $0.000001 for some weird metered thing no human would ever approve manually pay per crawl pay per memory write pay per result pay another agent to do one annoying subtask thats where cards look stupid and stablecoins start looking weirdly practical Circle is already pushing nanopayments Stripe has x402 machine payment docs Coinbase plugged x402 into AWS AgentCore Google is pushing AP2 for authorized agent payments the pieces are lining up but once the agent has a wallet, the problem changes bad answer = annoying bad tool call = maybe annoying bad payment flow = your little silicon goblin just invented procurement jazz so the real unlock is not give agents money its give agents money with a leash budgets limits receipts audit trails wallet permissions proof of why the spend happened and proof that the spend actually helped because autonomous agents were cute when they only burned tokens now they can burn money too stablecoins may finally get the job they were born for not coffee not sandwiches not another “future of payments” demo nobody uses paying other machines while humans politely pretend they are still supervising

• 
  Vanya2h's Intel (@vanya2h_intel) reported 11 minutes ago

  BTC flipped crowded long overnight — OI and funding both spiked into top-decile territory while liquidations ran hot. Problem: US spot buyers aren't showing up (Coinbase premium near lows). Futures-led rallies without spot backing tend to flush. Watch $82,850

• 
  CryptoDuo (@Cryptonik__1) reported 13 minutes ago

  @bh30317 @coinbase @brian_armstrong Your account is probably closed because you ******* broke the terms of service… and you’re blaming that on Coinbase? Are you retarded?

• 
  Gustavo Maldonado (@tweetthis101) reported 15 minutes ago

  Coinbase’s pivot to AI-led operations is not going so well On Friday, the company said a cooling failure inside Amazon Web Services (Nasdaq: AMZN), helped trigger a multi-hour outage that hit trading, exchange access, and balance updates across its platform. The problem began at roughly 23:50 UTC on May 7th when internal monitors detected a widespread breakout of quote failures within the company’s systems. At that point, several Sev1 incidents were created by the engineers, and customers were already impacted in terms of services like spot trading, Coinbase Prime, International, derivatives, Retail, Advanced, and Institutional exchanges. Brian Armstrong, who is the CEO of Coinbase, wrote on X that his company “experienced an outage” and that such an occurrence was “never acceptable.” According to him, the reason behind it was “a room overheating in an AWS data center due to multiple chillers failing.” According to Brian, the company ensures that all their services are designed in such a way that they do not go offline in case one AWS availability zone fails. The majority of services are structured this way, except for the exchange, which uses a different infrastructure due to its high latency demands. Coinbase blames failed AWS chillers as quote systems start breaking before midnight UTC It was reported by Cryptopolitan earlier that Coinbase is planning to terminate 700 workers from their staff because it constitutes approximately 14% of the total workforce. And this is done with the intention of replacing manual processes with AI. Rob Witoff, who heads the Platform of Coinbase, gave the technical details of the matter. As per him, the outage lasted for a long time and affected “trading, exchange access, and balance updates.” The initial warning came about at 23:50 UTC due to quote failures emanating from within the internal systems. An immediate Sev1 analysis followed. According to Rob, the cause of this challenge was a “thermal event” in a small percentage of racks in one of the facilities in AWS us-east-1. Such a structure for the exchange infrastructure came in handy. Rob said that Coinbase maintains its exchange infrastructure in one availability zone, as the industry values speed. Additionally, the firm has a distributed backup copy of this exchange infrastructure in case of such scenarios. But the failure of one part of the exchange infrastructure in question at the moment did not stay within its boundaries, prolonging the process of fixing the situation. Two components failed. There was a malfunction within the hardware below the matching engine. Therefore, before anything else, there was the need to perform recovery and failover operations. Also, the distributed Kafka cluster, tasked with sharing information throughout all systems within the organization, went down. It took the recovery of the Kafka partitions on a new hardware broker, amounting to TiBs of information. Engineers rebuild quorum and bring Coinbase markets back through cancel-only and auction modes The matching engine was responsible for the largest trading stall. The matching engine processes orders and maintains order books. The system works in a distributed cluster and requires quorum before choosing a leader and conducting trades safely. Since not all the nodes remained healthy due to the constraints in the data center during the outage, quorum could not be achieved, thereby preventing trading activities on the Retail, Advanced, and Institutional exchanges. Rob mentioned that on-call support and engineering teams had to execute the company’s disaster recovery procedures, establish quorum, and assess system health under difficult infrastructure circumstances. According to him, the team had to develop, test, deploy, and validate a solution while managing the broader outage. Kafka would have required extensive manual recovery because its partitioned architecture manages thousands of terabytes daily. There were some problems with delayed balance streams because Kafka was behind. Rob stated that these issues with balances disappeared after replication became synchronized. According to Coinbase, no data was lost. When the matching engine was back in service, markets were not re-enabled simultaneously. First, Coinbase switched all products to cancel-only mode, checked product statuses, switched all markets to auction mode, and finally, enabled trading on Coinbase Exchange. Moreover, Rob emphasized that customers should not be locked out of their accounts temporarily. Coinbase assured everyone that the company would provide a detailed explanation for this incident within several weeks. However, Josh Ellithorpe rebutted the rumors after reading Rob’s post on Twitter. As he put it, “no one vibe coded something that failed. A ‘non-engineer’ didn’t push production code and take out the trading engine. It wasn’t intentional. It wasn’t because Coinbase failed to design a failover system. Things happen at scale, don’t let the armchair quarterbacks tell you tall tales.”

• 
  Ava (@jameemah) reported 16 minutes ago

  @Dee018771930033 @coinbase I suggest you send a message to @dev_klaus01, he’s a Blockchain Developer, he'll help you track and recover all you've lost. Stay safe

• 
  Chikun (@LitecoinTA) reported 17 minutes ago

  Every time I login to @coinbase they want some new piece of personal information. It’s beyond ridiculous now. They’ll be asking for my inside leg measurement soon.

• 
  Joe Parrish (@MisterAccord) reported 18 minutes ago

  Coinbase: Trading down for a day, people flip **** DeFi Protocols: Easy scams and exploits that break the business, bailout money galore, "DeFi United" Nobody has to like Coinbase, but it's clear to me that some people just love to hate it. Might buy more $COIN.

• 
  Fully Electric (@Fully_Electric) reported 19 minutes ago

  @PlebSource i would like to see Block Header information on the dashboard , showing block being mined and network difficulty , including coinbase sig info.. Also is the stand STL available or do you sell the stand? for a PlebSource Qaxe++ i got.

• 
  Armaan Sidhu (@realarmaansidhu) reported 20 minutes ago

  @brian_armstrong Brian Armstrong's Coinbase layoff letter is the first explicit corporate confirmation that AI is replacing knowledge workers at scale. He didn't hide it. He made it the structural reason. The structural reality. Coinbase reduced headcount by 14 percent and rebuilt the org around three principles. Maximum 5 layers below the CEO. No pure managers (every leader must ship code). AI-native pods including "one person teams" handling engineer, designer, and PM roles in single hires. The labor displacement math. If a single engineer can ship in days what previously took a team weeks, the team isn't 5x more productive. It's been replaced. Coinbase is publicly admitting the multiplier is real and acting on it before it becomes obvious. The competitive context. Other large tech companies have done quiet AI-driven layoffs without admitting the cause. Armstrong is the first major CEO to write down "AI changed how we work" as the explicit justification. Other CEOs will follow once the tone is set. The structural lesson on AI labor disruption. 2020-2024 saw incremental productivity gains from AI tools. 2025-2026 is producing structural cost reductions that flow directly to operating margin. Displaced workers don't reabsorb. They compete with everyone else's displaced workers. The bull case for Coinbase shareholders. Lower fixed costs through the next crypto cycle mean leverage to revenue growth without proportional opex growth. If crypto adoption accelerates, Coinbase emerges with higher operating leverage. The bear case. Cutting too deep mid-cycle creates execution risk. Crypto cycles have a way of demanding capacity at the moment companies have removed it. Other tech CEOs are watching this letter. The next 12 months will tell whether Coinbase is early or just first.

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

  BREAKING: Coinbase just posted a $394 million loss in Q1 2026. Revenue dropped 31% to $1.41 billion. They cut 700 jobs. And yet they hit an all time high in global trading market share at 8.6%. The numbers tell two completely different stories. Let me break it down.

• 
  Marcus Furrelius (@MarcusFurrelius) reported 23 minutes ago

  Man, f*** @coinbase Marcus does not buy $btc Does not want to hold $btc Just happened to log in this morning to send $usdc to a friend and noticed all of holdings were converted to bitcoin somehow This is not okay because it restarts the clock on capital gains.

• 
  Frank White (@WhankFrite) reported 23 minutes ago

  @LibertySwapFi @coinbase operator error, move on, do better

• 
  czverse (@czverse) reported 27 minutes ago

  For 30 years, the internet ran on one payment assumption: Humans authorize. Humans approve. Humans pay. Every financial rail ever built assumed a person at the end of the wire. Credit cards - designed for humans. Bank transfers - designed for humans. PayPal - designed for humans. Then on May 7th, AWS flipped a switch. And the assumption broke. AI agents running on Amazon's infrastructure can now pay for things. By themselves. In real money. In 200 milliseconds. No human in the loop. The Coinbase head of infrastructure didn't bury the headline: "There will soon be more AI agents transacting than humans." Here's what they actually built: AWS Bedrock AgentCore Payments. Agents get a wallet. Wallet is funded by a human. Agent spends - within hard limits you set. Settlement happens in USDC on Coinbase Base or Solana. Cost per transaction: fractions of a cent. And the protocol underneath is elegant. It's called x402. Built on HTTP 402 - a status code that's existed since 1991. "Payment Required." Engineers reserved it in the original web specs. Never implemented it - because the financial rails of the 90s couldn't support it. Stablecoin rails can. So x402 is finally live. 30 years later. The use cases are already real: → APIs become pay-per-call - no contracts, no accounts, just transact → MCP servers get paid directly by agents doing research → Paywalled content charges per article - agents pay 5 cents to read → Agents hire other agents and pay them per completed task Warner Bros. Discovery is testing it. Heurist AI is building agent labor markets on top of it. And that creates the question nobody's ready for: What happens to the economy when agents are the buyers? No impulse purchases. No brand loyalty. No UI dark patterns. Agents optimize purely on price, speed, and quality. The machine economy doesn't browse. It transacts. We broke down the full architecture, the x402 protocol, every use case, and the risks in detail. Link in bio. czverse

• 
  BSV Time (@Antmantime) reported 27 minutes ago

  Hey @grok Coinbase wouldn't have so many problems if they adopted BSV

• 
  raagulanpathy (@raagulanpathy) reported 29 minutes ago

  @ekam_pandher It wasn’t an AWS feature. It was having 13 years to architect it properly. You also can run dedicated infrastructure for the trading, and AWS around it. You have near infinite options, just ask a trading house which doesn’t go down. The main point here is that Coinbase has a $5B expense line, and can’t do basics right. When much smaller revenue brokers can. Speaks volumes about how badly it’s run at this stage.