Ipregistry incident
INVALID_API_KEY error for API calls in some regions
Resolved after 44 minutes, on February 23, 2026.
A surge in load for a replicated database cluster saturated available connections. A recent backend library change introduced an overly aggressive connection timeout, which led to cascading timeouts in a subset of regions, while others were unaffected. We sincerely apologize for the disruption caused. We adjusted connection settings, and put additional safeguards in place to reduce the risk of similar issues. We are also improving testing and monitoring around connection handling to better detect and mitigate such situations in the future..
Update timeline
- investigating Feb 23, 2026, 09:05 PM UTC
We are currently investigating this incident..
- identified Feb 23, 2026, 09:17 PM UTC
We are continuing to work on a fix for this incident..
- monitoring Feb 23, 2026, 09:41 PM UTC
We implemented a fix and are currently monitoring the result..
- resolved Feb 23, 2026, 09:49 PM UTC
This incident has been resolved..
- monitoring Feb 23, 2026, 09:56 PM UTC
A surge in load for a replicated database cluster saturated available connections. A recent backend library change introduced an overly aggressive connection timeout, which led to cascading timeouts in a subset of regions, while others were unaffected. We sincerely apologize for the disruption caused. We adjusted connection settings, and put additional safeguards in place to reduce the risk of similar issues. We are also improving testing and monitoring around connection handling to better detect and mitigate such situations in the future..
Your product runs on more than Ipregistry
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services