OpenCage GmbH - Notice history

All systems operational

Uptime is measured independently by performance monitoring company StatusCake.

Changes to our API are published in our CHANGE LOG on GitHub.

Follow us on Mastodon, and please visit our blog for our annual uptime reports.

Website - Operational

100% - uptime
May 2023 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2023
Jun 2023
Jul 2023

Website - Email sending (via Postmarkapp.com) - Operational

100% - uptime

Geocoding API - reverse - Operational

100% - uptime
May 2023 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2023
Jun 2023
Jul 2023

Geosearch - Operational

100% - uptime
May 2023 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2023
Jun 2023
Jul 2023

Geocoding API - forward - Operational

100% - uptime
May 2023 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2023
Jun 2023
Jul 2023

Notice history

Jul 2023

No notices reported this month

Jun 2023

No notices reported this month

May 2023

geosearch - customers received HTTP 401 errors
  • Resolved
    Resolved

    Between 14:13 and 14:41 UTC our geosearch customer received HTTP 401 errors for some of their queries. The customer API key list wasn't correctly synced to all servers. There is a backup/fallback for geocoding if that happens but there wasn't for geosearch yet. Geocoding customers were not affected.

Higher than usual latency
  • Resolved
    Resolved

    We saw a higher amount of geocoding taking > 1000ms today in 3 one hour timeslots. Less than 3% of geocoding affected. We identified the affected server and took it offline. Inconclusive what exactly caused it, we suspect network hardware of the virtual machine and will replace the server.

May 2023 to Jul 2023

Next