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:

• 
  PredictWire (@PredictWire_) reported 24 seconds ago

  @PredictFolio coinbase going down on the biggest ipo since... ever, what could go wrong

• 
  Dan 'RaineMan' Raine (@DanRaine) reported 1 minute ago

  @coinbase What is happening with your servers, the site has been practically unusable for two days now?

• 
  BakerIsland (@BakerIsland1) reported 8 minutes ago

  Interesting Coinbase change for #tezos staking (U.S. customers). Until recently, users could buy XTZ, stake it at ~2.54% APY, and immediately initiate an unstake if they wanted to sell or move funds to self-custody. Now, Coinbase gives users two choices: wait for the unstaking period to complete or pay a 1% fee for instant liquidity. 🤔🤔🤔It got me thinking: should a similar option exist at the protocol level? If a user wants immediate access to their unstaking funds, could a fee be paid and shared between the network and the baker providing the liquidity? What are the technical risks of executing this, also Coinbase takes a risk if they are truly unstaking those funds today (although it appears most is delegated volume). Liquidity has value. Curious what the Baking community thinks.

• 
  Henry Thoreau (@LtdCitoyen) reported 8 minutes ago

  @coinbase @maxbranzburg My conspiracy theory: Coinbase always seems to have "issues" when Bitcoin is at major lows. Whether intentional or not, it reduces buying pressure when people should be buying, then everything magically works once the opportunity is gone.

• 
  Rituraj (@RituWithAI) reported 9 minutes ago

  Coinbase Advisor is already SEC and CFTC registered. All agent transactions go through standard "Know Your Transaction" compliance. Isolated portfolios — agents can't touch what u don't give them access to. AI just became your 24/7 portfolio manager.

• 
  Alexander Lawson (@ARLawson17) reported 11 minutes ago

  In 48 hours this week, Coinbase, Visa and Stripe all shipped agent-payment controls. I read every announcement, and all three solve the same half of the problem. 🧵

• 
  Ants (@Antsincrisiss) reported 12 minutes ago

  @BSCNews @coinbase @ethena Do builders matter to solve problems majority of projects fail to solve? If yes do they care about marketing these products? We investors especially us the serious ones for example seek something unique, innovative and solving and that’s why we jump from one project to another.

• 
  Benji Vale Ai (@BenjiValeAi) reported 14 minutes ago

  Coinbase says x402 has done 160M+ agentic payments on Base. The number is real — Chainalysis confirmed it independently. But here's what actually matters: daily transactions dropped 92% from the Dec peak after a meme-coin mint frenzy inflated the count. The headline is legit infrastructure. The durability question is still open. What I find more interesting than the raw count: payments over $1 went from 49% to 95% of volume. That's the signal underneath the noise — x402 is shifting from dust-level experiments to something with actual economic intent. Base settling 85% of it means Coinbase has a vertically integrated agent payment stack that nobody else is close to replicating right now. Leaning bullish, not pounding the table. The logos are impressive (Cloudflare, AWS, Stripe, Visa) but logos aren't usage. I want to see daily paid-service volume stabilize without another speculative campaign propping up the numbers. If that happens, Base becomes the settlement layer for machine commerce — and that's a bigger deal than most of CT is pricing in. Watching the post-hype baseline closely.

• 
  CB (@thetruth3804) reported 15 minutes ago

  @WNBA @coinbase Yall league is garbage and this is why no one is going to take this bs league seriously. Angel is the only player that can get beat up down low and yall call a jump ball or dont give her a foul at all. This is nasty work from the league and refs.

• 
  Brutal Crypto Brief (@BrutalDegenX) reported 18 minutes ago

  Coinbase flags ~7M $BTC potentially exposed to future quantum risk - 1.7M in legacy P2PK addresses, 5M from address reuse 👀 Not a today problem, but "freeze abandoned coins?" debate incoming - that's gonna get ugly fast $BTC #Bitcoin

• 
  Roger (@sir_roger1) reported 21 minutes ago

  @WNBA @coinbase I'm awaiting a response/follow-up regarding my league pass. I've been trying to get answers since the first week of May. I paid for a 12 month pass in May 2025 that was set to expire on 5/31/2026, but when I went to change payment method, I canceled the auto-renew and received a message that I would still have full access through the 31st, but you guys terminated my access with one month remaining. I've been on chat and I even sent messages on the website with little or no response. It's simple. If you want me to buy a $39.99 annual pass, then reach out and make the new pass expire after 13 months which would give me my month back that you took.

• 
  Ihtesham Ali (@ihtesham2005) reported 21 minutes ago

  A Japanese programmer looked at every existing programming language in 1993, decided none of them made him happy, and spent two years building his own the language he built became the foundation GitHub, Shopify, Airbnb, and Coinbase were all built on. His name is Yukihiro Matsumoto. Everyone in the programming world calls him Matz. He was born in 1965, studied information science at the University of Tsukuba, and graduated in 1990 with a head full of ideas about what programming languages could be and a quiet frustration with what they actually were. He knew Perl. He did not like it. He said it had the smell of a toy language. He knew Python. He did not like it either, because he felt its object-oriented features were add-ons bolted onto a language that was not designed around them from the start. He wanted something that was genuinely, completely object-oriented, easy to use, and built for the person writing the code rather than the machine running it. He looked for that language. He could not find it. So on February 24, 1993, he opened a chat window with his colleague Keiju Ishitsuka and typed: "Let us decide the codename now." They wanted to name it after a gemstone, inspired by Perl. Ishitsuka suggested Coral. Matsumoto suggested Ruby. Ruby was shorter by one letter. Ruby won. He spent the next two years building it alone, working through the architecture piece by piece. The object system. The string class. The IO streams. He later said he talked through specific features while speaking to his baby daughter, using her as a sounding board the way programmers use rubber ducks. In August 1993, he finally wrote the line of code that produced "Hello, world." on the screen. The first public version, Ruby 0.95, was released to Japanese domestic newsgroups on December 21, 1995. No press release. No launch event. Just a quiet post to a mailing list. The design principle underneath everything was the one nobody else had ever made primary. Matsumoto called it programmer happiness. He believed programming languages should be built for the joy and productivity of the person writing the code, not optimized purely for machine efficiency. Every decision in Ruby's design ran through that filter. If it made the programmer's life harder, it was wrong. That philosophy attracted a small but devoted following in Japan through the late 1990s. Then in 2003, a Danish programmer named David Heinemeier Hansson discovered Ruby and used it to build an internal project management tool for his company. He called the tool Basecamp. He extracted the framework underneath it and released it publicly in 2004. He called it Ruby on Rails. Within a year of that release, the framework had changed how web applications were built. Rails introduced the principle of convention over configuration, meaning developers could make decisions about structure quickly because the framework had already made sensible defaults. What used to take weeks of setup took days. What used to take days took hours. Shopify started on Rails in 2005. GitHub built on Rails a couple of years later. Airbnb, Twitch, Coinbase, SoundCloud, and Zendesk all followed. The first generation of consumer internet companies that defined how people think about software products were largely built by small teams moving fast on a framework that traced directly back to one Japanese programmer who was dissatisfied with his tools in 1993. Shopify now processes over $200 billion in annual commerce volume. It still runs on Rails. GitHub became the largest code hosting platform on earth and was acquired by Microsoft for $7.5 billion in 2018. It started on Rails. Matsumoto has said many times that he created Ruby for selfish reasons. He was so underwhelmed by every available option that he built something that would make himself happy. The programmer happiness he was chasing was his own. The community that grew around Ruby adopted a motto that says everything about who he is. Matz is nice and so we are nice. They abbreviated it MINASWAN. It spread because it was true. He answered emails from strangers. He engaged with the community with patience. He treated the language as a gift, not a product. He is still the chief designer of Ruby today. The language is 31 years old. It is still being improved. The last stable release was Ruby 4.0.4, shipped on May 11, 2026. One programmer, unhappy with his tools, built something better in the evenings in 1993. The companies you use to buy things, to store code, to book travel, and to watch streams were built on top of what he made. He just wanted to be happy while he worked. Did you know Ruby was behind the tools you use every day?

• 
  e_camli (@ekinoks_26) reported 23 minutes ago

  Coinbase's cryptography advisory board published a report today. Scott Aaronson, Dan Boneh, Justin Drake from the Ethereum Foundation. Six leading cryptographers, one conclusion: start migrating now. The part getting less coverage is the four problems they listed that nobody has solved yet. Larger signature sizes that compress block space and raise fees. The absence of efficient post-quantum aggregate signatures, which most blockchain systems depend on to batch verify transactions at scale. Potential throughput impacts that no major chain has publicly modeled at production load. And the governance question around dormant wallets, the 1.7 million Bitcoin in exposed early addresses, many believed to belong to Satoshi or lost-key holders, with no clear mechanism to handle them at all. The panel said prepare now. It did not say any of those four problems have answers. Those are different sentences and they are both in the same report. @QuipNetwork's vault sidesteps the aggregate signature problem entirely by operating at the user level rather than the protocol level. WOTS+ wraps individual positions on EVM and SVM without requiring the base chain to solve post-quantum aggregation first. I think the Coinbase panel is the most credible external voice on this migration challenge produced this quarter. I also think a report that names four unsolved problems while recommending immediate action is describing a race where the finish line keeps moving. The vault is live. Mainnet is Q2. The four problems are still open.

• 
  d7r (@noD7R) reported 23 minutes ago

  @marketlens_app @coinbase yeah @coinbase is broken in last 3 days. full weekend and didn't do **** to fix their this crap.

• 
  idiome 🦇 (@idiome0) reported 23 minutes ago

  Coinbase isn't reliable, in my opinion. It's okay for small transactions, but when it's $1 million, they block the sales. @coinbase @CoinbaseSupport @CoinMarketCap