Coinbase International Exchange Outage History

Coinbase International Exchange is up right now

Coinbase International Exchange had 8 outages in the last 2 years totaling 803h 47m of downtime — averaging 0.3 incidents per month.

There were 8 Coinbase International Exchange outages since August 22, 2025 totaling 803h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.international.coinbase.com

Minor May 28, 2026

Timeout errors on certain Coinbase International Rest APIs

Detected by Pingoru
May 28, 2026, 10:08 PM UTC
Resolved
May 28, 2026, 11:17 PM UTC
Duration
1h 9m
Affected: REST API
Timeline · 2 updates
  1. investigating May 28, 2026, 10:08 PM UTC

    We are currently investigating an issue causing errors on the Coinbase International Rest APIs endpoint. Some customers may experience failures when retrieving account information via API. Core exchange functionality remains available at this time. Our team is working to identify the root cause and restore normal performance. We will provide an updated status as soon as more information is available.

  2. resolved May 28, 2026, 11:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Degraded REST API

Detected by Pingoru
May 11, 2026, 10:30 PM UTC
Resolved
Jun 12, 2026, 11:59 PM UTC
Duration
32d 1h
Affected: REST API
Timeline · 3 updates
  1. investigating May 13, 2026, 07:55 AM UTC

    We are currently investigating an issue causing degraded performance on Coinbase International Rest APIs. Some customers may experience failures when retrieving account information via REST API. Core exchange functionality remains available at this time. Our team is working to identify the root cause and restore normal performance. We will provide an updated status as soon as more information is available.

  2. monitoring May 14, 2026, 03:25 AM UTC

    A fix has been implemented and we are monitoring the results. Some customers may see gaps in data from May 11 through May 13. We are backfilling affected data.

  3. resolved Jun 12, 2026, 11:59 PM UTC

    The backfill is now complete.

Read the full incident report →

Minor May 8, 2026

502 errors on certain Coinbase International Rest APIs

Detected by Pingoru
May 08, 2026, 08:15 PM UTC
Resolved
May 08, 2026, 08:27 PM UTC
Duration
12m
Affected: REST API
Timeline · 2 updates
  1. investigating May 08, 2026, 08:15 PM UTC

    We are currently investigating an issue causing 502 errors on the Coinbase International Rest APIs endpoint. Some customers may experience failures when retrieving account information via API. Core exchange functionality remains available at this time. Our team is working to identify the root cause and restore normal performance. We will provide an updated status as soon as more information is available.

  2. resolved May 08, 2026, 08:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026

Degraded Performance

Detected by Pingoru
May 08, 2026, 01:32 AM UTC
Resolved
May 08, 2026, 05:29 PM UTC
Duration
15h 56m
Affected: FIX Order APIUSDC (Arbitrum Network)FIX Market Data APIUSDC (Avalanche C-Chain Network)AAVE-PERPUSDC (Base Network)FIX Drop Copy APIADA-PERPREST APIUSDC (Ethereum Network)AERO-PERPWebsocket FeedUSDC (Optimism Network)AEVO-PERPDirect Access UIUSDC (Polygon Network)AI16Z-PERPUSDC (Solana Network)AIXBT-PERPBTC (Bitcoin Network)AKT-PERPETH (Ethereum Network)ALGO-PERPALT-PERPLTC (Litecoin Network)ANIME-PERPXRP (Ripple Network)APE-PERPSOL (Solana Network)ARB-PERPEURC (Base Network)EURC (Ethereum Network)ASTER-PERPATH-PERPAVAX (Avalanche C-Chain Network)ATOM-PERPDOGE (Dogecoin Network)AVAX-PERPLINK (Ethereum Network)AVNT-PERPXLM (Stellar Network)AXS-PERPADA (Cardano Network)BCH (Bitcoin Cash Network)AZTEC-PERPBARD-PERPARB (Arbitrum Network)BCH-PERPSEI (Sei Network)INJ (Ethereum Network)BERA-PERPFIL (Filecoin Network)APT (Aptos Network)NEAR (Near Network)ICP (Dfinity Network)BIRB-PERPBNB-PERPUNI (Base Network)BRETT-PERPPEPE (Ethereum Network)BOME-PERPHBAR (Hedera Network)BTC-PERPONDO (Ethereum Network)CAKE-PERPBONK (Solana Network)CFX-PERPSHIB (Ethereum Network)CRV (Base Network)COIN50-PERPCRV (Ethereum Network)COMP-PERPTAO (Bittensor Network)COW-PERPAAVE (Ethereum Network)CRV-PERPJASMY (Ethereum Network)ATOM (Cosmos Network)DASH-PERPDOGE-PERPALGO (Algorand Network)DYDX-PERPAERO (Base Network)VET (Vechain Network)EIGEN-PERPPENGU (Solana Network)ENA-PERPZORA (Base Network)FARTCOIN (Solana Network)ETC-PERPPUMP (Solana Network)ETH-PERPDOT (Polkadot Network)ETHFI-PERPEURC-PERPFAI-PERPFARTCOIN-PERPFET-PERPGUN-PERPHBAR-PERPHYPE-PERPIMX-PERPINJ-PERPIP-PERPJASMY-PERPJUP-PERPJTO-PERPKAITO-PERPKAS-PERPKERNEL-PERPLDO-PERPLINK-PERPLIT-PERPLTC-PERPMEME-PERPMERL-PERPMON-PERPMOODENG-PERPMORPHO-PERPNEO-PERPNIGHT-PERPNOM-PERPONDO-PERPOP-PERPOPN-PERPPAXG-PERPPENDLE-PERPPENGU-PERPPEOPLE-PERPPNUT-PERPPOL-PERPPOPCAT-PERPPUMP-PERPPYTH-PERPRAY-PERPRED-PERPRENDER-PERPRESOLV-PERPS-PERPSAGA-PERPSAND-PERPSENT-PERPSOL-PERPSOMI-PERPSPK-PERPSPX-PEPRTAO-PERPTHETA-PERPTIA-PERPTON-PERPTOWNS-PERPTURBO-PERPVET-PERPVVV-PERPVIRTUAL-PERPWIF-PERPWLFI-PERPXLM-PERPXRP-PERPXPL-PERPZAMA-PERPZEC-PERPZEN-PERPZK-PERPZRO-PERPZORA-PERP1000PEPE-PERP1000BONK-PERP1000MOG-PERP1000SHIB-PERP1000TOSHI-PERPETH-USDCBTC-USDCESP-PERPTSLA-PERPMSFT-PERPMETA-PERPGOOGL-PERPAAPL-PERPAMZN-PERPSPY-PERPNVDA-PERPQQQ-PERPPRL-PERPKAT-PERPEDGEX-PERPBASED1-PERPGOLD-PERPSILVER-PERPINTC-PERPARM-PERPAMD-PERPMU-PERPSNDK-PERPAI-PERP
Timeline · 2 updates
  1. investigating May 08, 2026, 01:32 AM UTC

    We are aware that customers may be experiencing degraded performance at this time. Our team is investigating this issue and will provide an update.

  2. resolved May 08, 2026, 05:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2025

Site Performance

Detected by Pingoru
Dec 05, 2025, 09:40 AM UTC
Resolved
Dec 05, 2025, 09:40 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 05, 2025, 09:40 AM UTC

    We are aware that customers have been unable to access Coinbase due to Cloudflare outage. This is now resolved.

Read the full incident report →

Minor November 18, 2025

Exchange Connectivity Degraded

Detected by Pingoru
Nov 18, 2025, 03:55 PM UTC
Resolved
Nov 18, 2025, 04:07 PM UTC
Duration
12m
Affected: FIX Order APIFIX Market Data APIFIX Drop Copy APIREST APIWebsocket FeedDirect Access UI
Timeline · 2 updates
  1. investigating Nov 18, 2025, 03:55 PM UTC

    We are currently experiencing client connectivity issues impacting order placement and cancellation across all major channels: FIX, REST, UI, and WebSocket. Our teams are actively investigating and working to restore normal operations as quickly as possible. This disruption may affect your ability to place or cancel orders via any of these interfaces. We will provide updates as soon as more information becomes available. Thank you for your patience as we work to resolve this issue

  2. resolved Nov 18, 2025, 04:07 PM UTC

    All services are now operating normally. Thank you for your patience while we worked to restore full functionality.

Read the full incident report →

Notice October 16, 2025

Degraded experience on FIX Order Entry Sessions

Detected by Pingoru
Oct 16, 2025, 05:20 PM UTC
Resolved
Oct 16, 2025, 06:02 PM UTC
Duration
42m
Affected: FIX Order API
Timeline · 2 updates
  1. investigating Oct 16, 2025, 05:20 PM UTC

    We are currently investigating an issue with our FIX Order Entry Session. Some clients may experience minor disruptions.

  2. resolved Oct 16, 2025, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 22, 2025

MANTLE-PERP - Degraded Performance

Detected by Pingoru
Aug 22, 2025, 06:25 AM UTC
Resolved
Aug 22, 2025, 10:30 PM UTC
Duration
16h 5m
Timeline · 4 updates
  1. investigating Aug 22, 2025, 06:25 AM UTC

    We have identified an issue with MANTLE-PERP and are working on this issue. We will provide updates as the situation changes.

  2. investigating Aug 22, 2025, 06:30 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 22, 2025, 10:30 PM UTC

    We are continuing to investigate this issue.

  4. resolved Aug 22, 2025, 10:30 PM UTC

    This incident has been resolved.

Read the full incident report →