[Coinbase Reviews July 14 Service Outage: Configuration Error Caused 50-Minute Downtime, User Funds Unaffected] Odaily Planet Daily News – Coinbase released a review report on the July 14 service outage, stating that the incident was caused by a critical network component misconfiguration triggered by a routine configuration update. The impact lasted approximately 50 minutes, during which user funds remained secure. Coinbase stated that at 12:34 PM Beijing time on July 14 (12:34 AM Eastern Time), the company deployed a routine configuration change to the shared production Kubernetes cluster that hosts core infrastructure services. The update was originally intended to migrate to a new service deployment model to improve system performance and reliability. However, due to a resource name conflict that was not detected by the pre-production environment's validation mechanism, the configuration change unexpectedly affected Kubernetes resources related to the Istio Ingress Gateway within the cluster, rendering the network component unavailable. Approximately three minutes later, all inbound traffic to the cluster was interrupted, making multiple infrastructure components inaccessible to internal services. Coinbase noted that because many asynchronous workflows rely on these infrastructure services—such as transaction settlement, fund transfers, and debit card transaction authorizations—multiple business lines were affected. The impacted services included: - Retail users were unable to complete off-chain transactions, deposits, and withdrawals. Some transactions in progress appeared stuck but were completed after services were restored. - Coinbase Card debit card transactions temporarily failed. Credit card payments were unaffected, but some card management features were unavailable. - Coinbase DEX's on-chain swap services on Base and Solana were suspended. - Coinbase Exchange and Prime institutional clients experienced transfer and settlement failures or delays. - Coinbase Developer Platform customers were unable to complete account setup, fund transfers, and deposit services. Coinbase stated that the Ingress Gateway was restored at 1:20 PM Eastern Time, and the incident was mitigated by 1:23 PM. The system then began processing the backlog of tasks, with most services returning to normal quickly, and the remaining queues cleared within the following hours. During the recovery process, Coinbase encountered two additional challenges. First, the deployment tool itself relied on the affected Ingress Gateway to operate, creating a "failure impacts recovery tools" circular dependency that prevented the normal rollback process. Second, while the emergency recovery process (break-glass access) was effective, the permission verification and manual review processes added to the recovery time. Coinbase emphasized that this incident did not involve any risk to asset security but highlighted the need for ongoing optimization of automated deployment, system dependencies, and disaster recovery mechanisms in large-scale financial infrastructure. The company will further strengthen system resilience to reduce the likelihood of similar incidents in the future.