Ipregistry Outage History

Ipregistry is up right now

Pingoru has recorded 13 incidents for Ipregistry: 3 in the last 12 months and 0 in the last 90 days.

Source: ipregistry.instatus.com

13incidents recorded
3last 12 months
0last 90 days
37 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Ipregistry in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 741 (0%)

Incidents, newest first

Minor May 8, 2026 Intermittent HTTP 502 Errors Affecting API Responses in Some Regions 21m

Started May 08, 2026, 08:19 AM UTC· resolved May 08, 2026, 08:40 AM UTC

  1. investigating May 08, 2026, 08:19 AM UTC

    We are currently investigating this incident..

  2. identified May 08, 2026, 08:27 AM UTC

    We are continuing to work on a fix for this incident..

  3. monitoring May 08, 2026, 08:34 AM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved May 08, 2026, 08:40 AM UTC

    This incident has been resolved..

Read the full incident report →

Major April 25, 2026 Ipregistry API: incident detected for 45m 45m Ipregistry API

Started Apr 25, 2026, 11:27 AM UTC· resolved Apr 25, 2026, 12:13 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 23, 2026 INVALID_API_KEY error for API calls in some regions 44m

Started Feb 23, 2026, 09:05 PM UTC· resolved Feb 23, 2026, 09:49 PM UTC

  1. investigating Feb 23, 2026, 09:05 PM UTC

    We are currently investigating this incident..

  2. identified Feb 23, 2026, 09:17 PM UTC

    We are continuing to work on a fix for this incident..

  3. monitoring Feb 23, 2026, 09:41 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Feb 23, 2026, 09:49 PM UTC

    This incident has been resolved..

  5. 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..

Read the full incident report →