OpenCage GmbH Status - Incident history https://status.opencagedata.com OpenCage GmbH Fri, 27 Mar 2026 11:05:32 +0000 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. Type: Incident

Duration: 3 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>11:05:32</var> GMT+0</small><br><strong>Investigating</strong> - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>11:08:03</var> GMT+0</small><br><strong>Resolved</strong> - API - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 27 Mar 2026 11:05:32 +0000 https://status.opencagedata.com/incident/cmn8sp2xu005z4t81a80vhmlm https://status.opencagedata.com/incident/cmn8sp2xu005z4t81a80vhmlm 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. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:06:07</var> GMT+0</small><br><strong>Investigating</strong> - API - Geocoding API - forward cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:12:00</var> GMT+0</small><br><strong>Resolved</strong> - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 25 Feb 2026 21:06:07 +0000 https://status.opencagedata.com/incident/cmm2ixvvf0fxyg3s9falsekyk https://status.opencagedata.com/incident/cmm2ixvvf0fxyg3s9falsekyk 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. Type: Incident

Duration: 8 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:04:33</var> GMT+0</small><br><strong>Investigating</strong> - API - Geocoding API - reverse cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:12:12</var> GMT+0</small><br><strong>Resolved</strong> - API - Geocoding API - reverse is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 25 Feb 2026 21:04:33 +0000 https://status.opencagedata.com/incident/cmm2ivuvm0hi69d6cs4cttind https://status.opencagedata.com/incident/cmm2ivuvm0hi69d6cs4cttind 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. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:01:19</var> GMT+0</small><br><strong>Investigating</strong> - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:12:26</var> GMT+0</small><br><strong>Resolved</strong> - API - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 25 Feb 2026 21:01:19 +0000 https://status.opencagedata.com/incident/cmm2irp1y04gk84k9n80kxlip https://status.opencagedata.com/incident/cmm2irp1y04gk84k9n80kxlip 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. Type: Incident

Duration: 8 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>05:48:49</var> GMT+0</small><br><strong>Investigating</strong> - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 25</var>, <var data-var='time'>05:56:31</var> GMT+0</small><br><strong>Resolved</strong> - API - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 25 Dec 2025 05:48:49 +0000 https://status.opencagedata.com/incident/cmjl0vew2004ew7uym9qlfr8m https://status.opencagedata.com/incident/cmjl0vew2004ew7uym9qlfr8m 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. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>08:20:48</var> GMT+0</small><br><strong>Investigating</strong> - API - Geocoding API - forward cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>08:21:57</var> GMT+0</small><br><strong>Resolved</strong> - API - Geocoding API - forward is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 15 Nov 2025 08:20:48 +0000 https://status.opencagedata.com/incident/cmi00oscq05lx8q0dn4xv5zjz https://status.opencagedata.com/incident/cmi00oscq05lx8q0dn4xv5zjz 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. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>05:57:22</var> GMT+0</small><br><strong>Investigating</strong> - API - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>05:58:31</var> GMT+0</small><br><strong>Resolved</strong> - API - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 30 Sep 2025 05:57:22 +0000 https://status.opencagedata.com/incident/cmg65b5eo001813wj0kfqa0j5 https://status.opencagedata.com/incident/cmg65b5eo001813wj0kfqa0j5 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. Type: Incident

Affected Components: , , ,

<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>09:00:43</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>09:41:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 19 Sep 2025 09:00:43 +0000 https://status.opencagedata.com/incident/cmfqooewi001cbnb6xo8ispyg https://status.opencagedata.com/incident/cmfqooewi001cbnb6xo8ispyg 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. Type: Incident

Duration: 15 hours and 10 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>13:05:55</var> GMT+0</small><br><strong>Investigating</strong> - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>13:21:05</var> GMT+0</small><br><strong>Resolved</strong> - Website is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 9 Oct 2024 13:05:55 +0000 https://status.opencagedata.com/incident/cm21vv0df000m26rrj5fvhubn https://status.opencagedata.com/incident/cm21vv0df000m26rrj5fvhubn 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. Type: Incident

Duration: 3 days, 11 hours and 27 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>17:22:06</var> GMT+0</small><br><strong>Investigating</strong> - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>17:52:40</var> GMT+0</small><br><strong>Identified</strong> - Intermitten connectivity issues at our website hoster (Heroku). API and customers not affected..</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>18:35:16</var> GMT+0</small><br><strong>Identified</strong> - Waiting for <https://status.heroku.com/incidents/2684>.</p> <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>18:45:32</var> GMT+0</small><br><strong>Resolved</strong> - Website is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 8 Oct 2024 17:22:06 +0000 https://status.opencagedata.com/incident/cm20pklqj02p713h4blh3d09x https://status.opencagedata.com/incident/cm20pklqj02p713h4blh3d09x 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. Type: Incident

Affected Components:

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>22:57:38</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Sun, 1 Sep 2024 22:57:38 +0000 https://status.opencagedata.com/incident/cm0k69lcc002s106jnhw81tzp https://status.opencagedata.com/incident/cm0k69lcc002s106jnhw81tzp 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. Type: Incident

Duration: 36 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>12:31:45</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>12:43:14</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>13:08:12</var> GMT+0</small><br><strong>Resolved</strong> - We can no longer reproduce the issue..</p> ]]> Wed, 21 Aug 2024 12:31:45 +0000 https://status.opencagedata.com/incident/cm03u2bw9000a5qzcbmzf5kas https://status.opencagedata.com/incident/cm03u2bw9000a5qzcbmzf5kas 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) Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>21:52:32</var> GMT+0</small><br><strong>Identified</strong> - To avoid writing to the database during the upgrade we put the website into maintainance mode. API/Geocoding/Geosearch are unaffected..</p> <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>22:02:14</var> GMT+0</small><br><strong>Resolved</strong> - User database upgrade was a success (postgresql 14->16).</p> ]]> Sun, 28 Jul 2024 21:52:32 +0000 https://status.opencagedata.com/incident/clz63j2u6320711heodkp93yrs7 https://status.opencagedata.com/incident/clz63j2u6320711heodkp93yrs7 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. Type: Incident

Duration: 58 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>00:10:57</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>00:45:21</var> GMT+0</small><br><strong>Monitoring</strong> - Resolved but we're testing a couple of signup scenarios..</p> <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>01:09:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>00:39:18</var> GMT+0</small><br><strong>Identified</strong> - Earlier user database change ran out of RAM without error message. We're in the process of running the steps in smaller chunks now..</p> ]]> Tue, 11 Jun 2024 00:10:57 +0000 https://status.opencagedata.com/incident/clx9nc6jw15745bomv269ux1qj https://status.opencagedata.com/incident/clx9nc6jw15745bomv269ux1qj 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>) Type: Incident

Affected Components: ,

<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>13:29:24</var> GMT+0</small><br><strong>Resolved</strong> - Network issue at one datacenter. Elevated number of API timeouts. (<https://status.hetzner.com/incident/b399a6d3-eac9-4ebb-b08b-7de35a70a030>).</p> ]]> Fri, 7 Jun 2024 13:29:24 +0000 https://status.opencagedata.com/incident/clx4q3l961419bbojrdohq520 https://status.opencagedata.com/incident/clx4q3l961419bbojrdohq520 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. Type: Incident

Duration: 17 hours and 59 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>17:09:00</var> GMT+0</small><br><strong>Investigating</strong> - 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.</p> <p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>23:15:04</var> GMT+0</small><br><strong>Identified</strong> - We started backfilling the missing data. Currently at 30% (the world has lots of road).</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>05:01:20</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>11:07:35</var> GMT+0</small><br><strong>Resolved</strong> - All remaining clusters are now up-to-date again..</p> ]]> Thu, 9 Nov 2023 17:09:00 +0000 https://status.opencagedata.com/incident/cloribfzw16673bhoo0dcop13e https://status.opencagedata.com/incident/cloribfzw16673bhoo0dcop13e 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. Type: Incident

Duration: 16 hours

Affected Components: , ,

<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>22:10:00</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>14:09:45</var> GMT+0</small><br><strong>Resolved</strong> - It's isolated to the Nuremberg, Germany, data center. We're directing all traffic to other data centers now..</p> ]]> Tue, 12 Sep 2023 22:10:00 +0000 https://status.opencagedata.com/incident/clmhq7y3o3777bcn6193xducx https://status.opencagedata.com/incident/clmhq7y3o3777bcn6193xducx 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. Type: Incident

Duration: 15 hours and 12 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>22:22:16</var> GMT+0</small><br><strong>Investigating</strong> - Website cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>22:37:28</var> GMT+0</small><br><strong>Resolved</strong> - Website is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 4 Aug 2023 22:22:16 +0000 https://status.opencagedata.com/incident/clkx5igyf1358308iimy0blsutae https://status.opencagedata.com/incident/clkx5igyf1358308iimy0blsutae 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. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 31</var>, <var data-var='time'>15:05:30</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Wed, 31 May 2023 15:05:30 +0000 https://status.opencagedata.com/incident/clibuaff6259413bgoi60cvnmoo https://status.opencagedata.com/incident/clibuaff6259413bgoi60cvnmoo 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. Type: Incident

Affected Components: ,

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:34:09</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Fri, 26 May 2023 15:34:09 +0000 https://status.opencagedata.com/incident/cli4q40rg166548b3mwha26s5dz https://status.opencagedata.com/incident/cli4q40rg166548b3mwha26s5dz 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. Type: Incident

Duration: 1 hour and 8 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>19:00:58</var> GMT+0</small><br><strong>Investigating</strong> - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>19:02:05</var> GMT+0</small><br><strong>Resolved</strong> - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 2 Dec 2022 19:00:58 +0000 https://status.opencagedata.com/incident/clb6vfvw2158296tun17u51qy2g https://status.opencagedata.com/incident/clb6vfvw2158296tun17u51qy2g 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). Type: Incident

Affected Components: ,

<p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Resolved</strong> - System mis-configuration lead to 3-4% of queries being partially empty for 18 hours. [Details](https://blog.opencagedata.com/post/bad-data-incident)..</p> ]]> Tue, 22 Nov 2022 23:00:00 +0000 https://status.opencagedata.com/incident/clau7kz6p13669humxsy2k8y00 https://status.opencagedata.com/incident/clau7kz6p13669humxsy2k8y00 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. Type: Incident

Duration: 1 hour and 12 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>10:26:51</var> GMT+0</small><br><strong>Investigating</strong> - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>10:28:02</var> GMT+0</small><br><strong>Resolved</strong> - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 12 Oct 2022 10:26:51 +0000 https://status.opencagedata.com/incident/cl95hma7n123312dcmyqaaf4q1l https://status.opencagedata.com/incident/cl95hma7n123312dcmyqaaf4q1l 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. Type: Incident

Duration: 1 hour and 12 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>08:24:33</var> GMT+0</small><br><strong>Investigating</strong> - Geosearch cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>08:25:45</var> GMT+0</small><br><strong>Resolved</strong> - Geosearch is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 28 Sep 2022 08:24:33 +0000 https://status.opencagedata.com/incident/cl8ld33bd553037wfofbb4nx95z https://status.opencagedata.com/incident/cl8ld33bd553037wfofbb4nx95z 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. Type: Incident

Duration: 14 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>00:03:52</var> GMT+0</small><br><strong>Monitoring</strong> - 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. .</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>00:17:49</var> GMT+0</small><br><strong>Resolved</strong> - We added a work-around, website is back up again..</p> ]]> Wed, 24 Aug 2022 00:03:52 +0000 https://status.opencagedata.com/incident/cl76use6m17203jpoo7m0v6gxj https://status.opencagedata.com/incident/cl76use6m17203jpoo7m0v6gxj