OpenCage had 10 outages in the last 2 years — averaging 0.4 incidents per month.
There were 10 OpenCage outages since June 7, 2024. Each is summarised below — incident details, duration, and resolution information.
Type: Incident Duration: 3 minutes Affected Components: Geosearch Mar 27, 11:05:32 GMT+0 - Investigating - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 27, 11:08:03 GMT+0 - Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service.
Type: Incident Duration: 6 minutes Affected Components: Geocoding API - forward Feb 25, 21:06:07 GMT+0 - Investigating - API - Geocoding API - forward cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 25, 21:12:00 GMT+0 - Resolved - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service.
Type: Incident Duration: 8 minutes Affected Components: Geocoding API - reverse Feb 25, 21:04:33 GMT+0 - Investigating - API - Geocoding API - reverse cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 25, 21:12:12 GMT+0 - Resolved - API - Geocoding API - reverse is now operational! This update was created by an automated monitoring service.
Type: Incident Affected Components: , Geocoding API - forward, Geocoding API - reverse, Geosearch, API → Sep 19, 09:00:43 GMT+0 - Resolved - We saw a drop in incoming traffic of 70% for a 30min period between 8:15 to 8:45 UTC. Our hosting provider had a router outage. Traffic was rerouted to another data center but the automatic DNS switch-over didn't kick in to reroute all traffic. Sep 19, 09:41:43 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 15 hours and 10 minutes Affected Components: Website Oct 9, 13:05:55 GMT+0 - Investigating - Website cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 9, 13:21:05 GMT+0 - Resolved - Website is now operational! This update was created by an automated monitoring service.
Type: Incident Affected Components: Website - Email sending (via Postmarkapp.com) Sep 1, 22:57:38 GMT+0 - Resolved - Some non-realtime emails were delayed for up to 48 hours. That affected the 'welcome' email after signup (accounts were created fine) and 'contact us' emails. They have all been processed and resend now. Other emails like confirmation, password resets, account deletion were not affected. We're sorry for the confusion. Whie no user contacted us about the issue we saw increased number of duplicate accounts, for example users trying login with email&password, and login-with-google shortly after.
Type: Incident Duration: 36 minutes Affected Components: Website Aug 21, 12:31:45 GMT+0 - Investigating - Error in Firefox "There is conflicting information between the SSL connection, its certificate and/or the included HTTP requests." on , API not affected. We are currently investigating this incident. Aug 21, 12:43:14 GMT+0 - Monitoring - We checked multiple browsers, multiple computers and ran validation suites on the SSL certificate chains (sslabs) but all looks good. We assume it's temporary issue with our hosting providers' routing endpoint. Aug 21, 13:08:12 GMT+0 - Resolved - We can no longer reproduce the issue.
Type: Incident Duration: 10 minutes Affected Components: Website Jul 28, 21:52:32 GMT+0 - Identified - To avoid writing to the database during the upgrade we put the website into maintainance mode. API/Geocoding/Geosearch are unaffected. Jul 28, 22:02:14 GMT+0 - Resolved - User database upgrade was a success (postgresql 14->16)
Type: Incident Duration: 58 minutes Affected Components: Website Jun 11, 00:10:57 GMT+0 - Investigating - We are currently investigating this incident. Jun 11, 00:45:21 GMT+0 - Monitoring - Resolved but we're testing a couple of signup scenarios. Jun 11, 01:09:24 GMT+0 - Resolved - This incident has been resolved. Jun 11, 00:39:18 GMT+0 - Identified - Earlier user database change ran out of RAM without error message. We're in the process of running the steps in smaller chunks now.
Type: Incident Affected Components: Geocoding API - reverse, Geocoding API - forward Jun 7, 13:29:24 GMT+0 - Resolved - Network issue at one datacenter. Elevated number of API timeouts. ()