Ipregistry - Notice history

All systems operational

100% - uptime

Globally distributed nodes — https://api.ipregistry.co - Operational

100% - uptime
Jun 2022 · 99.88%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2022
Jul 2022
Aug 2022

Europe nodes — https://eu.api.ipregistry.co - Operational

100% - uptime
Jun 2022 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2022
Jul 2022
Aug 2022

Dashboard - Operational

100% - uptime
Jun 2022 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2022
Jul 2022
Aug 2022

Landing Page - Operational

100% - uptime
Jun 2022 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2022
Jul 2022
Aug 2022

Search - Operational

100% - uptime
Jun 2022 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2022
Jul 2022
Aug 2022

Notice history

Aug 2022

Incorrect geolocation data for some IP addresses in the range 64.0.0.0-127.255.255.255
  • Resolved
    Resolved

    The issue is now globally resolved. If you are caching data, we suggest clearing your cache to evict invalid data.

    We apologize for the inconvenience this has caused.

    Make sure we are taking actions to prevent such an issue to happen again.

  • Monitoring
    Monitoring

    We implemented a fix. Deployment is in progress. We are currently monitoring the result. The issue should be resolved globally in the next minutes.

  • Identified
    Identified

    We identified the source of the issue. The problem is caused by an human error introduced in the data we receive from a trusted source.

  • Investigating
    Investigating

    We are experiencing an issue with the geolocation information returned for some IP addresses in the range 64.0.0.0-127.255.255.255.

    We are currently investigating this incident.

Jul 2022

No notices reported this month

Jun 2022

API - Globally distributed nodes — https://api.ipregistry.co isn't accessible at the moment (automated)
  • Resolved
    Resolved

    API - Globally distributed nodes — https://api.ipregistry.co is now operational! This update was created by an automated monitoring service.

  • Identified
    Identified

    The issue is caused by Cloudflare experiencing an incident. Indeed, we use Cloudflare as our global load balancing solution: https://www.cloudflarestatus.com/incidents/xvs51y9qs9dj

    We expect the problem to resolve in the next minutes.

  • Investigating
    Investigating

    API - Globally distributed nodes — https://api.ipregistry.co cannot be accessed at the moment. This incident was created by an automated monitoring service.

Jun 2022 to Aug 2022

Next