Coinbase has released a detailed report on the service outage that occurred on July 14, attributing the disruption to a Kubernetes resource name conflict during a routine configuration update. The incident affected several transaction services, including transfers, card transactions, and on-chain services, but user funds remained secure throughout. The issue arose when a configuration change, part of a migration to a new service deployment model, inadvertently modified Kubernetes resources related to the Istio Ingress Gateway, rendering the gateway unavailable. This led to a traffic interruption to the shared production Kubernetes cluster, impacting internal services and causing transaction delays and failures across Coinbase's platforms. Coinbase has outlined measures to prevent future incidents, including enhancing deployment safeguards and redundancy capabilities. The company aims for zero downtime and is committed to infrastructure improvements to ensure faster recovery from similar issues. Users experiencing ongoing issues are advised to contact Coinbase support.