• Duration: 14:33 UTC – 16:09 UTC (~96 minutes)
• Impact: The api.name.com endpoint was unreachable to external clients, resulting in socket timeouts and 502 errors.
• Root Cause Summary: The outage was triggered by an unanticipated 50x surge in traffic to a specific, heavyweight API endpoint. This volume resulted in severe database resource saturation and row-lock contention on the shared writer database, preventing the API from processing requests.

Resolution: Responders implemented Cloudflare WAF rate-limiting on the offending traffic and temporarily paused API traffic to allow the database update queue to drain and recover.