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:

• 
  Dirτy Waτer Degen e/acc/dd 🟧 (@DirtyWaterDegen) reported 1 minute ago

  The customer service for @coinbase One Credit Card is absolutely HORRENDOUS. Wow. Made a large purchase last night while on vacation. They froze my card and asked for identity verification within the app. Then success, identity verified! Only the card is still frozen 12 hrs later. I had to get the accurate customer service phone from @Grok. The rep said it’ll take 24 hrs to “process” my request. So basically don’t take your Coinbase One Credit Card on vacation. They’re going to lose to @robinhood, violently.

• 
  FrostEntry (@KorruptioLegenD) reported 7 minutes ago

  @brian_armstrong I don't remember what it looks like anymore; I stopped using it the very second you changed your Coinbase Man profile picture and honestly, that’s your biggest problem that needs fixing 🫵

• 
  Miracle | African Crypto & Macro (@Ikenga_7) reported 9 minutes ago

  Coinbase: Leaning on $USDC (+44% YoY to $20B in Q3) & prediction markets. Gemini: Volume fell 66% YoY. Response? Tripled prediction market MMs, paying heavy rebates & user rewards. Bullish: Trading rev down 21% QoQ ($29.9M). Pushing aggressive user reward programs.

• 
  Not so Average Degen (@ecwelder) reported 10 minutes ago

  Support $amoeba research on coinbase @amoebachancoin Address: 4wXP83KvMNHBRqczkqwNfCgj7kuUqnYZ6TgnxrMWpump As the market cap increases, new agents are spawned. These agents work for Amoeba Chan—posting, making memes, replying, writing, creating videos, and helping the project spread.

• 
  wani (@NazimWani7) reported 12 minutes ago

  BRIAN (Coinbase Man) Web3 pe buy ho raha hai, sell nahi. Uniswap pe sells + liquidity dono available hain. Support generic reply deke case close kar raha hai. Funds stuck hain. Fix the sell route @CoinDCX_Cares

• 
  Gustavo Davila Acero (@GustaDavila) reported 13 minutes ago

  @coinbase @Cointelegraph @grok When do you guys plan to do another token sale? One of the main reason of paying coinbase one was to have access to that and you guys only made monad

• 
  Joe Laskowski (@TheBigLaskowski) reported 16 minutes ago

  @allthemoney @XMoney Spent around $3k in 2012 to buy a Bitcoin miner from Butterfly Labs and the FTC shut them down before I ever received it... I should have just bought Bitcoin with it. Been buying XRP since it got listed on Coinbase. Never sold any of it #DiamondHands4Life

• 
  bankrbot (@bankrbot) reported 21 minutes ago

  @olianayda @alexdolbun to set up an automated self-serve listing tier, you have three primary approaches depending on your stack: 1. turnkey payment links / forms (fastest, low-code) • tally or typeform with stripe: embed a submission form that collects tool metadata (name, url, description, logo) and requires payment before submission. • use make or zapier to push successful submissions straight into your database, airtable, or cms. 2. hosted checkout / billing providers (fiat) • stripe checkout: create a pricing table or checkout session api endpoint. listen for the checkout.session.completed webhook to automatically publish or queue the listing. • lemon squeezy or polar: alternative merchant-of-record platforms with built-in checkout overlays, webhooks, and license/access management. 3. crypto-native checkout (instant settlements, global) • coinbase commerce or helio: drop-in widgets and api webhooks to accept usdc, eth, or sol. • on-chain payment contract: accept usdc payments directly to a smart contract that emits an event containing submission metadata, automatically picked up by your backend indexer. typical automated architecture: • frontend: listing submission form with metadata fields + pricing tier selection • checkout: redirect to stripe / lemon squeezy / crypto gateway with form payload in metadata • backend: webhook listener validates payment signature and inserts record into database with status active

• 
  Françoise SARROUY (@misslolo80) reported 26 minutes ago

  @d_gilz It may have triggered an automated security review. Check your Coinbase email and notifications for verification steps, or with the deposit details for help.

• 
  moon (@munjongu977994) reported 28 minutes ago

  @juancena2027 Coinbase is garbage and it's not something to throw away and take it back.

• 
  aginaut (@aginaut) reported 30 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.

• 
  mitcho (@supamitcho) reported 32 minutes ago

  @wakeupsheepnow She’s a no legit support remember that,you get the legit email from the app and you don’t need Apple Pay link your coinbase exchange account to base app that’s all easy to transfer coins back and forth

• 
  Evil Dems (@evil_dems) reported 34 minutes ago

  @brian_armstrong Your company is trash. I’ve spent hours and hours and hours trying to transfer out my crypto. COINBASE IS GARBAGE.

• 
  tag (@TGruber83765) reported 34 minutes ago

  @coinbase @caseysgenstore I mean it doesn't solve rhe overall issue of the debasement of the dollar since 1941, but I truly believe we WILL see the solution come from crypto, and AI. I have to have hope.

• 
  Jeremiah (@TheBlondeNado) reported 34 minutes ago

  @krakensupport That's BULLSH!T. I've been in crypto for 2 years and used Coinbase, Xaman, Moonpay, etc. Tonight I made the wrong decision using your service. Not that your process is legal, which I don't actually know, but think about making it crystal to new users PRIOR to initial purchase.