Duration: 1 hour and 23 minutes

Jun 26, 09:46:53 GMT+0
Resolved - This incident has been resolved, we are now able to receive emails again 🎉.

Jun 26, 08:24:12 GMT+0
Identified - We are currently having issues with our email provider and are unable to receive emails..

Duration: 3 minutes

Affected Components:

Mar 27, 11:08:03 GMT+0
Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service..

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..

Duration: 6 minutes

Affected Components:

Feb 25, 21:12:00 GMT+0
Resolved - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service..

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..

Duration: 8 minutes

Affected Components:

Feb 25, 21:12:12 GMT+0
Resolved - API - Geocoding API - reverse is now operational! This update was created by an automated monitoring service..

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..

Duration: 11 minutes

Affected Components:

Feb 25, 21:12:26 GMT+0
Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service..

Feb 25, 21:01:19 GMT+0
Investigating - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 8 minutes

Affected Components:

Dec 25, 05:56:31 GMT+0
Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service..

Dec 25, 05:48:49 GMT+0
Investigating - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 1 minute

Affected Components:

Nov 15, 08:21:57 GMT+0
Resolved - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service..

Nov 15, 08:20:48 GMT+0
Investigating - API - Geocoding API - forward cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 1 minute

Affected Components:

Sep 30, 05:58:31 GMT+0
Resolved - API - Geosearch is now operational! This update was created by an automated monitoring service..

Sep 30, 05:57:22 GMT+0
Investigating - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..

Affected Components: , , ,

Sep 19, 09:41:43 GMT+0
Resolved - This incident has been resolved..

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..

Duration: 15 hours and 10 minutes

Affected Components:

Oct 9, 13:21:05 GMT+0
Resolved - Website is now operational! This update was created by an automated monitoring service..

Oct 9, 13:05:55 GMT+0
Investigating - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 3 days, 11 hours and 27 minutes

Affected Components:

Oct 8, 18:45:32 GMT+0
Resolved - Website is now operational! This update was created by an automated monitoring service..

Oct 8, 18:35:16 GMT+0
Identified - Waiting for <https://status.heroku.com/incidents/2684>.

Oct 8, 17:52:40 GMT+0
Identified - Intermitten connectivity issues at our website hoster (Heroku). API and customers not affected..

Oct 8, 17:22:06 GMT+0
Investigating - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..

Affected Components:

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..

Duration: 36 minutes

Affected Components:

Aug 21, 13:08:12 GMT+0
Resolved - We can no longer reproduce the issue..

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, 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 <https://opencagedata.com>, API not affected. We are currently investigating this incident..

Duration: 10 minutes

Affected Components:

Jul 28, 22:02:14 GMT+0
Resolved - User database upgrade was a success (postgresql 14->16).

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..

Duration: 58 minutes

Affected Components:

Jun 11, 01:09:24 GMT+0
Resolved - This incident has been resolved..

Jun 11, 00:45:21 GMT+0
Monitoring - Resolved but we're testing a couple of signup scenarios..

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..

Jun 11, 00:10:57 GMT+0
Investigating - We are currently investigating this incident..

Affected Components: ,

Jun 7, 13:29:24 GMT+0
Resolved - Network issue at one datacenter. Elevated number of API timeouts. (<https://status.hetzner.com/incident/b399a6d3-eac9-4ebb-b08b-7de35a70a030>).

Duration: 17 hours and 59 minutes

Affected Components: ,

Nov 10, 11:07:35 GMT+0
Resolved - All remaining clusters are now up-to-date again..

Nov 10, 05:01:20 GMT+0
Monitoring - The missing roadinfo data was backfilled on one cluster and all affected customer's API requests are redirected to that cluster. We're continuing to backfill data on the remaining clusters..

Nov 9, 23:15:04 GMT+0
Identified - We started backfilling the missing data. Currently at 30% (the world has lots of road).

Nov 9, 17:09:00 GMT+0
Investigating - We are currently investigating why road info (width, lanes) and speed info are not returned for those users who set &roadinfo=1 in their requests.

Duration: 16 hours

Affected Components: , ,

Sep 13, 14:09:45 GMT+0
Resolved - It's isolated to the Nuremberg, Germany, data center. We're directing all traffic to other data centers now..

Sep 12, 22:10:00 GMT+0
Monitoring - We're seeing elevated error rates of HTTP 504 with 0.15% of responses. There's been a network backbone maintenance this night and some connections between our clusters seem unstable. While HTTP 504 indicates a server disconnect none of the individual servers is offline. We're continue to monitor the situation..

Duration: 15 hours and 12 minutes

Affected Components:

Aug 4, 22:37:28 GMT+0
Resolved - Website is now operational! This update was created by an automated monitoring service..

Aug 4, 22:22:16 GMT+0
Investigating - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..

Affected Components:

May 31, 15:05:30 GMT+0
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..

Affected Components: ,

May 26, 15:34:09 GMT+0
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..

Duration: 1 hour and 8 minutes

Affected Components:

Dec 2, 19:02:05 GMT+0
Resolved - Geosearch is now operational! This update was created by an automated monitoring service..

Dec 2, 19:00:58 GMT+0
Investigating - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..

Affected Components: ,

Nov 22, 23:00:00 GMT+0
Resolved - System mis-configuration lead to 3-4% of queries being partially empty for 18 hours. [Details](https://blog.opencagedata.com/post/bad-data-incident)..

Duration: 1 hour and 12 minutes

Affected Components:

Oct 12, 10:28:02 GMT+0
Resolved - Geosearch is now operational! This update was created by an automated monitoring service..

Oct 12, 10:26:51 GMT+0
Investigating - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..

Duration: 1 hour and 12 minutes

Affected Components:

Sep 28, 08:25:45 GMT+0
Resolved - Geosearch is now operational! This update was created by an automated monitoring service..

Sep 28, 08:24:33 GMT+0
Investigating - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..