Skip to content

Outage tracker / Coinbase

Is Coinbase down?

I'm having a problem

Vendor reports an incident, no impactWhat Coinbase reports

Coinbase reports an incident on its status page: GYEN conversion to USDC.

Impact: no impact. Since 2026-10-20 15:14 UTC.

Latest update, 2026-10-20 15:14 UTC: GMO-Z.com Trust Company, Inc., the issuer of GYEN, is winding down the GYEN stablecoin. Coinbase will convert all GYEN held on Coinbase to USDC from October 26 - 30, 2026. Send and receive support for GYEN will be disabled on Coinbase from October 26, 2026. Any GYEN that remains on platform as of October 26, 2026 will be converted to USDC from October 26 - 30, 2026. Your tokens will be converted at the market rate at the time of conversion. There will be no transaction fees associated with the conversion. If you do not wish for your GYEN to be converted to USDC please send it to a compatible self-custody wallet before October 26, 2026. Tax consequences may apply. Please consult your local tax professional. After the conversion is complete, you will no longer be able to withdraw GYEN and Coinbase will no longer support deposits of GYEN. Please do not send GYEN to your Coinbase deposit address, as these deposits may not be recoverable and will not be converted to USDC.

Coinbase's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 7 minutes ago

Our checks of Coinbase pass from all 10 regions we check.

As of Oct 22, 2026, 11:32 PM UTC, RealUptime's checks of Coinbase passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 11:32 PM UTC
US-East117 msChecks passing
US-West88 msChecks passing
Europe367 msChecks passing
Asia-Pacific907 msChecks passing
US-Central112 msChecks passing
Canada32 msChecks passing
UK38 msChecks passing
Southeast Asia1437 msChecks passing
Australia250 msChecks passing
South America355 msChecks passing
their status pagetheir claim, not our reading

Coinbase reports: All systems operational (“All Systems Operational”)

from Coinbase's own status page, checked Oct 22, 2026, 11:22 PM UTC

Coinbase reports an active incident: GYEN conversion to USDC (all systems operational, since Oct 20, 2026, 3:14 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

Coinbase's own status page shows no incident, and our checks of Coinbase pass right now.

Coinbase's own component breakdown, as they publish it

  • BitcoinOperational
  • Coinbase - WebsiteOperational
  • Credit & Debit CardsOperational
  • Dapp walletOperational
  • Proof of AddressOperational
  • WalletsOperational
  • Bitcoin CashOperational
  • Coinbase - MobileOperational
  • Dapp browserOperational
  • ID verificationOperational
  • PaymentsOperational
  • US Bank AccountsOperational
  • Coinbase - Advanced TradeOperational
  • EthereumOperational
  • ID authentication (Japan)Operational
  • StablecoinsOperational
  • US WiresOperational
  • Ethereum ClassicOperational
  • TradingOperational
  • US DerivativesOperational
  • International DerivativesOperational
  • LitecoinOperational
  • Onchain ToolsOperational
  • SEPA TransfersOperational
  • 0xOperational
  • Coinbase - APIOperational
  • UK Faster PaymentsOperational
  • Basic Attention TokenOperational
  • Coinbase Wallet - ExtensionOperational
  • EU Debit / Credit Cards (3DS)Operational
  • WebhooksOperational
  • Coinbase Wallet - MobileOperational
  • PayPalOperational
  • PortalOperational
  • USD CoinOperational
  • Deribit - WebsiteOperational
  • ZcashOperational
  • XRPOperational
  • iDEALOperational
  • SWIFTOperational
  • StellarOperational
  • Augur REPOperational
  • Customer SupportOperational
  • 2FAOperational
  • Apple PayOperational
  • DAIOperational
  • EOSOperational
  • Google PayOperational
  • ChainlinkOperational
  • Coinbase BorrowOperational
  • PayID (Australia)Operational
  • Coinbase TaxesOperational
  • FAST (Singapore)Operational
  • TezosOperational
  • Coinbase OneOperational
  • DashOperational
  • Interac (Canada)Operational
  • EFT (Canada)Operational
  • OrchidOperational
  • CosmosOperational
  • PIX (Brazil)Operational
  • Peer-to-Peer Send/ReceiveOperational
  • Kyber NetworkOperational
  • Samsung PayOperational
  • Blik (Poland)Operational
  • Coinbase Card (Debit)Operational
  • OmiseGOOperational
  • Coinbase One Card (Credit)Operational
  • IMPS (India)Operational
  • MakerOperational
  • CompoundOperational
  • AlgorandOperational
  • Band ProtocolOperational
  • NumeraireOperational
  • CeloOperational
  • UMAOperational
  • LoopringOperational
  • yearn.financeOperational
  • UniswapOperational
  • RenOperational
  • BalancerOperational
  • Wrapped BitcoinOperational
  • DecentralandOperational
  • CivicOperational
  • district0xOperational
  • NuCypherOperational
  • FilecoinOperational
  • BancorOperational
  • AaveOperational
  • SynthetixOperational
  • The GraphOperational
  • SushiSwapOperational
  • PolygonOperational
  • SKALEOperational
  • CardanoOperational
  • AnkrOperational
  • StorjOperational
  • Curve DAO TokenOperational
  • NKNOperational
  • Enjin CoinOperational

These are Coinbase's components, named and scored by Coinbase. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Coinbase's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Coinbase response time, by region

US-East
1.8sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 111ms2026-09-24 UTC: p95 201ms2026-09-25 UTC: p95 423ms2026-09-26 UTC: p95 411ms2026-09-27 UTC: p95 438ms2026-09-28 UTC: p95 376ms2026-09-29 UTC: p95 473ms2026-09-30 UTC: p95 575ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 560ms2026-10-03 UTC: p95 628ms2026-10-04 UTC: p95 590ms2026-10-05 UTC: p95 573ms2026-10-06 UTC: p95 580ms2026-10-07 UTC: p95 355ms2026-10-08 UTC: p95 188ms2026-10-09 UTC: p95 275ms2026-10-10 UTC: p95 527ms2026-10-11 UTC: p95 488ms2026-10-12 UTC: p95 611ms2026-10-13 UTC: p95 727ms2026-10-14 UTC: p95 667ms2026-10-15 UTC: p95 239ms2026-10-16 UTC: p95 485ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
US-West
1.6sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 313ms2026-09-24 UTC: p95 332ms2026-09-25 UTC: p95 425ms2026-09-26 UTC: p95 488ms2026-09-27 UTC: p95 267ms2026-09-28 UTC: p95 477ms2026-09-29 UTC: p95 565ms2026-09-30 UTC: p95 512ms2026-10-01 UTC: p95 598ms2026-10-02 UTC: p95 526ms2026-10-03 UTC: p95 560ms2026-10-04 UTC: p95 489ms2026-10-05 UTC: p95 578ms2026-10-06 UTC: p95 507ms2026-10-07 UTC: p95 580ms2026-10-08 UTC: p95 341ms2026-10-09 UTC: p95 444ms2026-10-10 UTC: p95 633ms2026-10-11 UTC: p95 615ms2026-10-12 UTC: p95 545ms2026-10-13 UTC: p95 640ms2026-10-14 UTC: p95 597ms2026-10-15 UTC: p95 384ms2026-10-16 UTC: p95 481ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
Europe
913msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 305ms2026-09-24 UTC: p95 336ms2026-09-25 UTC: p95 606ms2026-09-26 UTC: p95 568ms2026-09-27 UTC: p95 445ms2026-09-28 UTC: p95 406ms2026-09-29 UTC: p95 551ms2026-09-30 UTC: p95 663ms2026-10-01 UTC: p95 327ms2026-10-02 UTC: p95 414ms2026-10-03 UTC: p95 470ms2026-10-04 UTC: p95 357ms2026-10-05 UTC: p95 293ms2026-10-06 UTC: p95 312ms2026-10-07 UTC: p95 344ms2026-10-08 UTC: p95 308ms2026-10-09 UTC: p95 260ms2026-10-10 UTC: p95 404ms2026-10-11 UTC: p95 404ms2026-10-12 UTC: p95 397ms2026-10-13 UTC: p95 500ms2026-10-14 UTC: p95 484ms2026-10-15 UTC: p95 326ms2026-10-16 UTC: p95 286ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 913ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 703ms2026-09-24 UTC: p95 717ms2026-09-25 UTC: p95 710ms2026-09-26 UTC: p95 614ms2026-09-27 UTC: p95 568ms2026-09-28 UTC: p95 523ms2026-09-29 UTC: p95 589ms2026-09-30 UTC: p95 464ms2026-10-01 UTC: p95 730ms2026-10-02 UTC: p95 443ms2026-10-03 UTC: p95 509ms2026-10-04 UTC: p95 642ms2026-10-05 UTC: p95 523ms2026-10-06 UTC: p95 756ms2026-10-07 UTC: p95 538ms2026-10-08 UTC: p95 607ms2026-10-09 UTC: p95 637ms2026-10-10 UTC: p95 473ms2026-10-11 UTC: p95 434ms2026-10-12 UTC: p95 629ms2026-10-13 UTC: p95 478ms2026-10-14 UTC: p95 539ms2026-10-15 UTC: p95 740ms2026-10-16 UTC: p95 786ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 961ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 354ms2026-09-24 UTC: p95 396ms2026-09-25 UTC: p95 592ms2026-09-26 UTC: p95 523ms2026-09-27 UTC: p95 393ms2026-09-28 UTC: p95 483ms2026-09-29 UTC: p95 442ms2026-09-30 UTC: p95 459ms2026-10-01 UTC: p95 445ms2026-10-02 UTC: p95 406ms2026-10-03 UTC: p95 377ms2026-10-04 UTC: p95 368ms2026-10-05 UTC: p95 531ms2026-10-06 UTC: p95 434ms2026-10-07 UTC: p95 477ms2026-10-08 UTC: p95 478ms2026-10-09 UTC: p95 269ms2026-10-10 UTC: p95 270ms2026-10-11 UTC: p95 251ms2026-10-12 UTC: p95 152ms2026-10-13 UTC: p95 238ms2026-10-14 UTC: p95 402ms2026-10-15 UTC: p95 260ms2026-10-16 UTC: p95 519ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 502ms2026-09-24 UTC: p95 505ms2026-09-25 UTC: p95 582ms2026-09-26 UTC: p95 613ms2026-09-27 UTC: p95 184ms2026-09-28 UTC: p95 683ms2026-09-29 UTC: p95 470ms2026-09-30 UTC: p95 633ms2026-10-01 UTC: p95 241ms2026-10-02 UTC: p95 398ms2026-10-03 UTC: p95 529ms2026-10-04 UTC: p95 511ms2026-10-05 UTC: p95 637ms2026-10-06 UTC: p95 747ms2026-10-07 UTC: p95 353ms2026-10-08 UTC: p95 277ms2026-10-09 UTC: p95 440ms2026-10-10 UTC: p95 328ms2026-10-11 UTC: p95 409ms2026-10-12 UTC: p95 461ms2026-10-13 UTC: p95 546ms2026-10-14 UTC: p95 438ms2026-10-15 UTC: p95 482ms2026-10-16 UTC: p95 552ms2026-10-17 UTC: p95 984ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
UK
477msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 314ms2026-09-24 UTC: p95 419ms2026-09-25 UTC: p95 509ms2026-09-26 UTC: p95 362ms2026-09-27 UTC: p95 259ms2026-09-28 UTC: p95 396ms2026-09-29 UTC: p95 302ms2026-09-30 UTC: p95 301ms2026-10-01 UTC: p95 363ms2026-10-02 UTC: p95 313ms2026-10-03 UTC: p95 334ms2026-10-04 UTC: p95 534ms2026-10-05 UTC: p95 352ms2026-10-06 UTC: p95 531ms2026-10-07 UTC: p95 210ms2026-10-08 UTC: p95 311ms2026-10-09 UTC: p95 327ms2026-10-10 UTC: p95 338ms2026-10-11 UTC: p95 274ms2026-10-12 UTC: p95 348ms2026-10-13 UTC: p95 239ms2026-10-14 UTC: p95 273ms2026-10-15 UTC: p95 331ms2026-10-16 UTC: p95 342ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 477ms
Sep 23Oct 7Oct 22
Southeast Asia
2.1sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 954ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 585ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 829ms2026-10-03 UTC: p95 562ms2026-10-04 UTC: p95 885ms2026-10-05 UTC: p95 812ms2026-10-06 UTC: p95 885ms2026-10-07 UTC: p95 594ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
Australia
2.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 988ms2026-09-24 UTC: p95 785ms2026-09-25 UTC: p95 661ms2026-09-26 UTC: p95 644ms2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 798ms2026-09-29 UTC: p95 793ms2026-09-30 UTC: p95 671ms2026-10-01 UTC: p95 782ms2026-10-02 UTC: p95 755ms2026-10-03 UTC: p95 762ms2026-10-04 UTC: p95 723ms2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 945ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 805ms2026-10-12 UTC: p95 925ms2026-10-13 UTC: p95 794ms2026-10-14 UTC: p95 803ms2026-10-15 UTC: p95 944ms2026-10-16 UTC: p95 892ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.8s
Sep 23Oct 7Oct 22
South America
1.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 673ms2026-09-24 UTC: p95 670ms2026-09-25 UTC: p95 871ms2026-09-26 UTC: p95 723ms2026-09-27 UTC: p95 673ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 577ms2026-10-01 UTC: p95 797ms2026-10-02 UTC: p95 826ms2026-10-03 UTC: p95 697ms2026-10-04 UTC: p95 746ms2026-10-05 UTC: p95 544ms2026-10-06 UTC: p95 530ms2026-10-07 UTC: p95 546ms2026-10-08 UTC: p95 652ms2026-10-09 UTC: p95 593ms2026-10-10 UTC: p95 443ms2026-10-11 UTC: p95 904ms2026-10-12 UTC: p95 794ms2026-10-13 UTC: p95 699ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 699ms2026-10-16 UTC: p95 629ms2026-10-17 UTC: p95 2.8s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 2.9s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22

Check your own site while you wait on Coinbase

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Coinbase. It cannot diagnose Coinbase's own systems.

Email me when Coinbase reports an incident on its status page, and again when it reports it resolved.

Get an email when Coinbase reports an incident

Email me when Coinbase reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Coinbase's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 117msstatus code: 200checked: Oct 22, 2026, 11:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Coinbase normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 88msstatus code: 200checked: Oct 22, 2026, 11:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Coinbase normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 112msstatus code: 200checked: Oct 22, 2026, 11:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Coinbase normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 32msstatus code: 200checked: Oct 22, 2026, 11:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Coinbase normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 355msstatus code: 200checked: Oct 22, 2026, 11:20 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Coinbase normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 367msstatus code: 200checked: Oct 22, 2026, 11:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Coinbase normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 38msstatus code: 200checked: Oct 22, 2026, 11:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Coinbase normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 907msstatus code: 200checked: Oct 22, 2026, 11:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Coinbase normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1437msstatus code: 200checked: Oct 22, 2026, 11:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Coinbase normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 250msstatus code: 200checked: Oct 22, 2026, 11:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Coinbase normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Coinbase, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Coinbase yet, which is not evidence that nothing is wrong.

Recent probe events

Mina - Delayed Sends & Receives, 5h 47mdeclared on their status page2026-10-22
Card Payment Unavailable (US) - Try Another, 3h 9mdeclared on their status page2026-10-22
Degraded Performance - Derivatives Portfolio Transfers, 52mdeclared on their status page2026-10-22
Delayed Sends/Receives - TON Network, 1h 1mdeclared on their status page2026-10-22
Delayed Sends and Receives - Solana, 10mdeclared on their status page2026-10-21
GYEN conversion to USDCdeclared on their status page2026-10-20
Delayed Sends and Receives - Kusama (KSM) Network, 2h 1mdeclared on their status page2026-10-16
Delayed Sends and Receives - Flare Network, 58mdeclared on their status page2026-10-16

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Coinbase since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Coinbase covering any window you pick, with our check readings and Coinbase's own claim at the time, side by side.

Full check history for Coinbase: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Coinbase uptime by RealUptime's checksLive, from this page's own readings.
[![Coinbase uptime by RealUptime's checks](https://realuptime.io/outages/coinbase/badge.svg?days=30)](https://realuptime.io/outages/coinbase)
<a href="https://realuptime.io/outages/coinbase"><img src="https://realuptime.io/outages/coinbase/badge.svg?days=30" alt="Coinbase uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Coinbase down?", https://realuptime.io/outages/coinbase. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://api.coinbase.com/v2/currencies
secondary
https://status.coinbase.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.coinbase.com

RealUptime is not affiliated with Coinbase; the name identifies what we checked, and nothing here speaks for Coinbase's own team. We send a single web request to Coinbase from 10 regions on our own schedule and time the response. We do not see inside Coinbase's systems, do not use an account or real transaction, and are not the same signal Coinbase's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Coinbase is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.