tag:status.opencagedata.com,2005:/history OpenCage GmbH Status - Incident history 2026-03-27T11:05:32.703+00:00 OpenCage GmbH tag:status.opencagedata.com,2005:Incident/cmn8sp2xu005z4t81a80vhmlm 2026-03-27T11:05:32.703+00:00 2026-03-27T11:05:32.739+00:00 API - Geosearch isn't accessible at the moment (automated) 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..

]]> tag:status.opencagedata.com,2005:Incident/cmm2ixvvf0fxyg3s9falsekyk 2026-02-25T21:06:07.898+00:00 2026-02-25T21:06:07.911+00:00 API - Geocoding API - forward isn't accessible at the moment (automated) 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..

]]> tag:status.opencagedata.com,2005:Incident/cmm2ivuvm0hi69d6cs4cttind 2026-02-25T21:04:33.297+00:00 2026-02-25T21:04:33.306+00:00 API - Geocoding API - reverse isn't accessible at the moment (automated) 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..

]]> tag:status.opencagedata.com,2005:Incident/cmm2irp1y04gk84k9n80kxlip 2026-02-25T21:01:19.126+00:00 2026-02-25T21:01:19.136+00:00 API - Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 11 minutes

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/cmjl0vew2004ew7uym9qlfr8m 2025-12-25T05:48:49.826+00:00 2025-12-25T05:48:49.846+00:00 API - Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 8 minutes

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/cmi00oscq05lx8q0dn4xv5zjz 2025-11-15T08:20:48.649+00:00 2025-11-15T08:20:48.672+00:00 API - Geocoding API - forward isn't accessible at the moment (automated) Type: Incident

Duration: 1 minute

Affected Components: Geocoding API - forward

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

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

]]> tag:status.opencagedata.com,2005:Incident/cmg65b5eo001813wj0kfqa0j5 2025-09-30T05:57:22.848+00:00 2025-09-30T05:57:22.875+00:00 API - Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 1 minute

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/cmfqooewi001cbnb6xo8ispyg 2025-09-19T09:00:43.354+00:00 2025-09-19T09:00:43.354+00:00 Drop in incoming traffic, timeouts 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..

]]> tag:status.opencagedata.com,2005:Incident/cm21vv0df000m26rrj5fvhubn 2024-10-09T13:05:55.875+00:00 2024-10-09T13:05:55.893+00:00 Website isn't accessible at the moment (automated) 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..

]]> tag:status.opencagedata.com,2005:Incident/cm20pklqj02p713h4blh3d09x 2024-10-08T17:22:06.474+00:00 2024-10-08T17:22:06.487+00:00 Website isn't accessible at the moment (automated) Type: Incident

Duration: 3 days, 11 hours and 27 minutes

Affected Components: Website

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

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

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

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

]]> tag:status.opencagedata.com,2005:Incident/cm0k69lcc002s106jnhw81tzp 2024-09-01T22:57:38.615+00:00 2024-09-01T22:57:38.615+00:00 Delayed welcome emails 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..

]]> tag:status.opencagedata.com,2005:Incident/cm03u2bw9000a5qzcbmzf5kas 2024-08-21T12:31:45.595+00:00 2024-08-21T12:31:45.595+00:00 SSL error on homepage 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 <https://opencagedata.com>, 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..

]]> tag:status.opencagedata.com,2005:Incident/clz63j2u6320711heodkp93yrs7 2024-07-28T21:52:32.955+00:00 2024-07-28T21:52:32.955+00:00 Database upgrade 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).

]]> tag:status.opencagedata.com,2005:Incident/clx9nc6jw15745bomv269ux1qj 2024-06-11T00:10:57.942+00:00 2024-06-11T00:10:57.942+00:00 New account signups produce errors 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..

]]> tag:status.opencagedata.com,2005:Incident/clx4q3l961419bbojrdohq520 2024-06-07T13:29:24.766+00:00 2024-06-07T13:29:24.766+00:00 Timeout 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. (<https://status.hetzner.com/incident/b399a6d3-eac9-4ebb-b08b-7de35a70a030>).

]]> tag:status.opencagedata.com,2005:Incident/cloribfzw16673bhoo0dcop13e 2023-11-09T17:09:00.000+00:00 2023-11-09T17:09:00.000+00:00 Missing road info Type: Incident

Duration: 17 hours and 59 minutes

Affected Components: Geocoding API - reverse, Geocoding API - forward

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.

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

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 10, 11:07:35 GMT+0
Resolved - All remaining clusters are now up-to-date again..

]]> tag:status.opencagedata.com,2005:Incident/clmhq7y3o3777bcn6193xducx 2023-09-12T22:10:00.000+00:00 2023-09-12T22:10:00.000+00:00 Elevated error rates Type: Incident

Duration: 16 hours

Affected Components: Geocoding API - reverse, Geocoding API - forward, Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/clkx5igyf1358308iimy0blsutae 2023-08-04T22:22:16.407+00:00 2023-08-04T22:22:16.436+00:00 Website isn't accessible at the moment (automated) Type: Incident

Duration: 15 hours and 12 minutes

Affected Components: Website

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

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

]]> tag:status.opencagedata.com,2005:Incident/clibuaff6259413bgoi60cvnmoo 2023-05-31T15:05:30.591+00:00 2023-05-31T15:05:30.591+00:00 geosearch - customers received HTTP 401 errors Type: Incident

Affected Components: Geosearch

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

]]> tag:status.opencagedata.com,2005:Incident/cli4q40rg166548b3mwha26s5dz 2023-05-26T15:34:09.407+00:00 2023-05-26T15:34:09.407+00:00 Higher than usual latency Type: Incident

Affected Components: Geocoding API - reverse, Geocoding API - forward

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

]]> tag:status.opencagedata.com,2005:Incident/clb6vfvw2158296tun17u51qy2g 2022-12-02T19:00:58.032+00:00 2022-12-02T19:00:58.095+00:00 Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 1 hour and 8 minutes

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/clau7kz6p13669humxsy2k8y00 2022-11-22T23:00:00.000+00:00 2022-11-22T23:00:00.000+00:00 Bad data for 3-4% of geocoding queries Type: Incident

Affected Components: Geocoding API - reverse, Geocoding API - forward

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

]]> tag:status.opencagedata.com,2005:Incident/cl95hma7n123312dcmyqaaf4q1l 2022-10-12T10:26:51.058+00:00 2022-10-12T10:26:51.068+00:00 Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 1 hour and 12 minutes

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/cl8ld33bd553037wfofbb4nx95z 2022-09-28T08:24:33.672+00:00 2022-09-28T08:24:33.682+00:00 Geosearch isn't accessible at the moment (automated) Type: Incident

Duration: 1 hour and 12 minutes

Affected Components: Geosearch

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

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

]]> tag:status.opencagedata.com,2005:Incident/cl76use6m17203jpoo7m0v6gxj 2022-08-24T00:03:52.124+00:00 2022-08-24T00:03:52.124+00:00 Homepage and accounts not available Type: Incident

Duration: 14 minutes

Affected Components: Website

Aug 24, 00:03:52 GMT+0
Monitoring - Our hosting provider for our website has upstream DNS issues https://status.heroku.com/incidents/2453 The OpenCage API is NOT affected. Sorry for the inconvenience caused. .

Aug 24, 00:17:49 GMT+0
Resolved - We added a work-around, website is back up again..

]]>