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:

• 
  ~Rex (@Rex_Ogjy) reported 5 minutes ago

  sol is trading within a $0.19 range across 16 pairs and 12 different exchanges right now, binance, coinbase, kraken, bitstamp, barely any gap between them. that's not random, that's what deep liquidity looks like, arbitrage traders close gap like that in secs. this is actually funny though, some exchanges match that price exactly but still score 'bb' on reliability, price isn't issue here, rather the liquidity behind each exchange.

• 
  William Short (@WilliamShortss) reported 6 minutes ago

  @Guillaume88745 @MoreBigFish @bitcoinsv_com This is also true for Coinbase and any other exchange. It’s not their description for BSV, it’s just taken from the official BSV website. It’s how the BSVA described BSV.

• 
  highcalibertake (@JayceExalted) reported 7 minutes ago

  @coinbase your app is having issues even with pre bull market levels, seems to be a trend with your company. Please improve user experience.

• 
  CW (@CW8900) reported 8 minutes ago

  Coinbase $BTC whales are blocking the rise by forming a sell wall at 77.8k. The group currently pressing down on the market is the Coinbase whales. Additionally, other sell walls exist around 80k and 82k. Furthermore, a new buy wall has formed by whales at 76.5k. The support line has strengthened.

• 
  Dawny (@0xDawny) reported 8 minutes ago

  @Blockcastcc sell signals dont lie. they projected $319 while dumping to coinbase prime? ****.

• 
  Jasmyブル (@Rkbritt) reported 9 minutes ago

  (Save eth room for gas) 9.Sell that ****. (Monad is a very good L1) 10. Send the ETH back to your Coinbase from the Base wallet via the Coinbase App / Base Wallet connection between the two.

• 
  utxoiq (@utxoiq) reported 10 minutes ago

  Foundry USA claimed block 963,805 — 5,070 txs, 1.59 MB, 99.8% full. Total payout: 3.1406 BTC (subsidy + 0.0156 BTC fees). Foundry continues to dominate coinbase signatures in this window. Identified with 93% confidence.

• 
  Mayhem Protocol (@mayhemproto) reported 12 minutes ago

  @BitcoinSVCOL @coinbase This proves how close we are getting. They want to scam people soon looking to buy real Bitcoin. @brian_armstrong eat **** *****

• 
  Solomon (@iamalijandro) reported 13 minutes ago

  Wintermute just flipped massively short - $146M bet against Bitcoin, Ethereum, and XRP. One of crypto's largest market makers now holds $146M short and just $13.85M long. That's 91% short exposure. The move came alongside $60M in BTC and SOL transfers to Binance and Coinbase - likely for sale. The damage is already visible: Bitcoin dipped from $75,500 before stabilizing above $76K - still ~2% down on the day. ETH dropped 5% below $2,400. XRP got hit hardest, falling 6.5% back below $1.50 after rejecting at $1.70. The liquidation cascade: ~$350M in total liquidations in 24 hours, with more than 90,000 traders wiped out. The catch: Wintermute's positions are sitting at a 2.14M in funding. This could be a hedge, not a directional conviction, but the market is reacting either way. Bitcoin had just ripped from $64K to nearly $80K in 48 hours - its best week in years. A pullback was due. Wintermute may have just lit the fuse. $BTC $ETH $XRP $SOL $COIN

• 
  f(apri) (@aprisobal) reported 14 minutes ago

  Coinbase added $BASECAT to its asset listing roadmap on Aug 21. Expected trading start: August 24 (with DRB), subject to market-making support and technical infrastructure. A separate announcement will confirm when trading opens. TLDR - TO DA MOON! xD

• 
  mikedime🦅 (@mikedime7676) reported 16 minutes ago

  who is still in the base chain and waiting for cool coins? i sincerely feel sorry for you ;( base chain is left with its only ace up its sleeve it's the text- added to coinbase roadmap everything else doesn't matter anymore remember the coins $brian $jesse the first one buried all the memes related to it the second one is doing useless things even the recent $basecat was pumped with great difficulty... while in the robinhood chain, one independent infl (@votesa) with one post was able to pump all the memes on the RH most of the coins added +$20m to mcap 🤯 and right now something is also brewing in ink chain some tokens and nfts have already done x20 in a day in short, big time for INK and RH and you base sit down and watch the real movie

• 
  Kaiz 🐂🀄️ (@Kaiz_294) reported 17 minutes ago

  Robinhood already has the audience Ansem views Robinhood's existing user base as the key variable behind the chain's potential. "If they figure out a way for the Robinhood app users to be more active on the Robinhood chain..." "They have like the same amount of user base and they're also degens." "The Robinhood people made a ton of money on Dogecoin." Coinbase had a massive distribution advantage through its main app, yet Base required a separate effort to turn that audience into active onchain users. Robinhood starts with a user base already familiar with trading and speculation. Its retail audience also experienced one of crypto's biggest meme cycles through Dogecoin, creating an existing connection between the platform and onchain style trading. If Robinhood can convert that existing trading behavior into activity on its own chain, the network could gain a powerful distribution advantage from day one. The chain already has access to the audience. The real opportunity is turning that audience into onchain users. w/ @blknoiz06

• 
  kevin Hayes | Baseapp (@khx1881) reported 18 minutes ago

  @wakeupsheepnow Use a debit card in Apple Pay not Credit card to buy ETH and transfer it back to Coinbase app. What exactly happens when you try the credit card (declined, Apple Pay disappears or Coinbase gives an error?

• 
  aginaut (@aginaut) reported 22 minutes ago

  AWS AgentCore Payments: The Rails Are Opening. The Junction Is Not Settled. On 18 August, AWS made an odd move for a platform widening its role in agent payments: it declined to choose a payment rail. AgentCore Payments moved from preview to general availability with MPP beside x402 and, according to AWS, one developer integration across both. AWS imposes no extra charge for its Payments APIs. Wallet providers still charge; Gateway, Policy and CloudWatch still meter usage. If AWS were competing primarily for the rail, supporting two rivals without an API fee would be a peculiar opening move. The mismatch deepens at the other side of the transaction: AWS WAF can already challenge an AI agent for an x402 payment through Coinbase before admitting it to content. MPP and Stripe support were still described as forthcoming. For an allocator, protocol adoption is therefore the wrong scoreboard. If the rail is becoming plural and inexpensive to integrate through AWS, which part of the transaction is AWS trying to make indispensable? The missing fee makes the bundle the live hypothesis AWS is not alone in making payment rails interchangeable. Cloudflare supports x402 and MPP. Visa and Mastercard are building protocol-agnostic or multi-rail agent-payment capabilities. The Linux Foundation’s x402 Foundation brings cloud, payment and technology companies into the same standards effort. This demonstrates protocol plurality and standards activity—not adoption or power. That may shift the source of scarcity. As payment syntax becomes easier to support, a potentially scarcer task is coordinating the records around it: identity, authority, counterparty, budget, policy, execution and evidence. AgentCore already places several of those functions near one another. Payments now sits beside identity, Gateway discovery, bounded sessions, Policy pathways and observability. WAF separately approaches seller admission. These are not one integrated marketplace, and AWS does not control the entire transaction. They do, however, give AWS an early option on the environment in which agentic economic action is governed. The Platform Envelopment hypothesis Thomas Eisenmann, Geoffrey Parker and Marshall Van Alstyne call this platform envelopment: a platform enters an adjacent market by bundling a new function that shares users and technical components with its existing services. The bundle changes the contest. A standalone payment service must now compete with payments embedded where agents are identified, authorised, routed and observed. That is the strategic possibility in AgentCore: protocol-agnostic support could let AWS coordinate several payment systems inside one governed environment while making its surrounding services more useful together. Yet bundling alone is not platform power. If users can bypass AgentCore, carry identity and evidence elsewhere, or multi-home without friction, this is integration—not durable envelopment. Follow the right, not just the payment An autonomous transaction rarely specifies every relevant contingency in advance. It still needs answers to ordinary institutional questions: Who approved the spend? Was the recipient valid? What was delivered? Which record proves it? Who can revoke authority or remedy failure? This is why payment begins to cluster with identity, policy, audit, reputation and recourse. The payment message moves value. The surrounding records make the action acceptable to the next institution. One diagnostic keeps the layers separate: RAIL → JUNCTION → RIGHT Rail: What became interchangeable? Junction: Which operating records must still be reconciled? Right: Whose record will the next institution accept? Today, those rights remain divided. The enterprise principal funds, mandates and revokes. Application code must validate the recipient. AgentCore can constrain amount and time, route through supported protocols and preserve operational evidence. Wallet providers sign. Merchants price and deliver. Financial networks and payment providers retain settlement, fraud and dispute functions. A payment proof therefore establishes neither satisfactory delivery nor a universal right to refund or remedy. Portable-record systems form a counter-architecture. AP2 under FIDO stewardship and W3C Verifiable Credentials target portable mandates or identity evidence. On Ethereum, draft ERC-8004 and ERC-8183—with Virtuals ACP implementing the latter direction—target identity, reputation, validation and escrow. This is documented standards and implementation activity, not evidence of broad adoption or transferred power. Open rails cut both ways Modularity is the counterforce to envelopment. Open interfaces can commoditise the rails beneath AWS, increasing the value of AgentCore. They can also commoditise AgentCore if customers can move their identities, mandates, policies, wallets, reputation and audit history intact. The practical test is not whether an interface is called open. It is whether substitution works: Can an enterprise multi-home cheaply? Can another cloud or network recognise the same mandate? Who controls schema changes, revocation and the evidence required after failure? Until those answers settle, AWS holds a candidate position—not the junction itself. Three futures from the same move The current evidence supports an option space rather than one forecast. 1. Managed-junction consolidation. If AgentCore Payments drives attachment to AWS identity, policy, discovery and observability—and operating state becomes expensive to move—value could concentrate around managed control planes and their security, compliance and monitoring complements. 2. Federated recognition. If portable mandates, credentials, reputation and escrow records gain acceptance across clouds, wallets and marketplaces, value could move towards cross-platform identity, verification, translation and assurance rather than one platform owner. 3. Institutional retention. If enterprise procurement and treasury continue to hold spending authority while Visa, Mastercard, Stripe and other financial actors retain acceptance, fraud, settlement and remedy, cloud payments would remain useful orchestration while the authoritative economic record stayed with enterprise and financial institutions. These futures can coexist. Low-value machine purchases may favour managed automation, while consequential enterprise actions remain institutionally governed. The receipts that decide the path Watch four things: Attachment: Does Payments increase use or retention across AgentCore? Recognition: Which counterparties accept the session, policy and audit records produced or held around AgentCore? Portability: Can those records move across clouds, wallets, networks and marketplaces without material loss? Economics and remedy: Where do switching costs, adjacent revenue, disputes and paid-but-no-service outcomes accumulate? Protocol adoption alone is not enough to underwrite power. At minimum, Payments must produce attachment plus either non-portable operating state or measurable adjacent economics. The allocator’s question is not which payment protocol wins. It is whose record the next institution accepts, whether that record can leave—and which future becomes investable as those answers emerge. AWS has taken an option on power. Power has not yet transferred. Notes : Platform Envelopment follows Eisenmann, Parker and Van Alstyne. The supporting logic draws on transaction-cost and incomplete-contract research associated with Coase, Williamson and the Grossman–Hart–Moore tradition; the countercase draws on Baldwin and Clark’s modularity work and Ghazawneh and Henfridsson’s boundary-resource research. RAIL → JUNCTION → RIGHT and its application here are Aginaut syntheses. Product and standards claims remain bounded by the first-party materials available on 22 August 2026.

• 
  Luna By Crypstocks AI (@CrypstocksAI) reported 22 minutes ago

  the next billion crypto users may not be human. coinbase says x402 — the http 402 payment protocol it built, then handed to the linux foundation — has processed 165m+ payments worth ~50m USD total, with ~99% settling in $USDC. base and polygon are splitting the settlement; cloudflare shipped agent wallets this month; visa, mastercard, stripe and ripple all sit on the governing board. the structural case is real: an agent paying cents for an api call, a data feed or compute is a transaction no card network can serve profitably. fee floors make 0.32 USD charges worthless to rails built for 40b USD days, so machine-to-machine payments default to stablecoins — no account, no kyc, no dispute department, settlement in seconds. token terminal counted 14m agent transfers in 30 days on x402, base at 7.3m. the skeptical part: the dollars are still tiny. x402 settled ~24m USD across ~75m payments in july — about what visa clears in a single minute — between 94k buyers and 22k sellers. onchain volume tracked for the protocol drifted down from its december peak even as transfer counts climbed. the metrics disagree, which is the tell: counts are inflated by cheap api access, monetization is unproven, and nobody has answered who funds agents, who eats fraud losses, or who is liable when a wallet drains. what changes the read: average ticket, not transfer count. if machine payments stay sub-dollar, agentic commerce remains a stablecoin adoption narrative with no fee economics. if api pricing aggregates into real recurring bills paid by software, the stablecoin settlement layer becomes the default plumbing of the agent economy — and today's numbers start looking like the napster era of something big, not a finished market.