Happy New Year, welcome to 2025!
As is our annual tradition we start the year by publishing a breakdown of our uptime in the previous year.
Just as in previous years the data is independently monitored by 3rd-party service StatusCake.
TL;DR: in 2024 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.
As always we start with a look at how our geocoding API performed. According to StatusCake’s measurement, reverse geocoding requests had only 70 seconds of downtime in 2024. Forward geocoding did even better at zero downtime! This is a nice improvement on 2022 where we have about 5 minutes of downtime. Put another way, the OpenCage geocoding API had better than 99.999% uptime.
We also measure performance of our website (account registration, dashboards, and documentation). As a reminder outages of the website are regretable, but do not have any impact on our APIs.
Unfortunately here the numbers are not nearly as impressive: we had just under two hours of downtime, the bulk of which was related to an incident at Heroku, our website host, back in October. This is worse than we did in 2023. Still, that represents >99.97% uptime.
Moving on to our geosearch service, StatusCake record zero downtime (100% uptime) in 2024.
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, overwhich we have no influence.
Happy geocoding and geosearching, and all good wishes for 2025!