Happy New Year, welcome to 2025!

Same procedure as every year - we kick off the new year by continuing our annual tradition of publishing a breakdown of our uptime in the previous year.

As always the data is independently monitored by 3rd-party service StatusCake.

TL;DR: in 2025 our geocoding API had over 99.999% uptime

You can always see (and subscribe to) the current data on our public status page, hosted by instatus, at status.opencagedata.com.

"OpenCage status page"

We measure uptime for four different services:

  1. Reverse geocoding According to StatusCake’s measurement, reverse geocoding requests had only zero seconds of downtime in 2025! 100% uptime! It doesn’t get better than that.

  2. Forward geocoding Unfortunately we were not able to hit the 100% target with forward geocoding. In 2025 we had 5 minutes, 33 seconds of downtime, which works out to 99.9989% uptime

  3. Geosearch - unfortunately we did not do as well with our geosearch service, StatusCake records 8 minutes, 53 seconds of downtime in 2025, meaning we achieved only 99.998% uptime. One for us to work on in 2026.

These three services are entirely managed by us and hosted with Hetzner.

  1. Our website - finally we also measure performance of our website (account registration, dashboards, and documentation), which is all hosted by Heroku, independently of our geocoding and geosearch infrastructure. Heroku again had a rough year, with four different outages each over five minutes in length. So in total StatsuCake recorded 20 minutes, 39 seconds of downtime for the website in 2025, which works out to “only” 99.996% uptime. This is not the level we aspire to.

Taken as a whole, I am pleased that overall our customers could, once again, depend on our services. We will continue to monitor the situation with Heroku (and our performance generally), hopefully this year’s multiple outages is not the start of a trend.

One standard disclaimer: it’s important to realize that an outage as seen by StatusCake doesn’t imply that 100% of requests are failing. Many, or even most, requests can still be succeeding without incident. In almost every case of measured downtime over the last few years the issue has been network related. Usually it is an issue at a customer’s ISP, over which we have no influence.

Happy geocoding and geosearching, and all good wishes for 2026!

Ed