Critical incident

namecom: API outage

Affected: name.com API

Current status of namecom: Operational — live namecom status

Timeline

1. Apr 29, 2026, 15:03 UTC
   investigating
   We're currently investigating the issue.
2. Apr 29, 2026, 16:22 UTC
   monitoring
   After further remediation, we are seeing recovery. We are still monitoring closely to ensure its sustained.
3. Apr 29, 2026, 16:32 UTC
   resolved
   This incident has been resolved.
4. May 8, 2026, 15:29 UTC
   postmortem
   * **Duration:** 14:33 UTC – 16:09 UTC \(~96 minutes\) * **Impact:** The [api.name.com](http://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.

Updates as published by namecom (original).