On October 20, 2025, an incident affected PlanetScale due to a DNS misconfiguration in a service provider, leading to capacity constraints and network instability within AWS us-east-1. The issue unfolded in two phases, initially impacting the PlanetScale control plane but leaving customer databases unaffected, followed by network partitions that affected some database branches. During the incident, PlanetScale engineers identified several challenges, including an inability to launch new EC2 instances and partial network partitions, which they managed with interventions such as changing default database regions and optimizing resource use. Despite the challenges, PlanetScale's design focus on isolation and static stability ensured minimal impact, with the resolution achieved through manual interventions and automated failover systems. Reflecting on the incident, PlanetScale plans to enhance resilience against the failure modes of dependent services and improve network partition tolerance, especially in the AWS us-east-1 region, which has six availability zones.