tag:status.graphhopper.com,2005:/historyGraphHopper Status - Incident History2024-03-28T03:50:42+01:00GraphHoppertag:status.graphhopper.com,2005:Incident/202260062024-03-12T17:07:07+01:002024-03-12T17:07:07+01:00Outage<p><small>Mar <var data-var='date'>12</var>, <var data-var='time'>17:07</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>12</var>, <var data-var='time'>16:35</var> CET</small><br><strong>Monitoring</strong> - The network problems were fixed. We are monitoring the system closely.</p><p><small>Mar <var data-var='date'>12</var>, <var data-var='time'>16:30</var> CET</small><br><strong>Investigating</strong> - We are investigating the issue. It seems that our hosting provider has internal network issue.</p>tag:status.graphhopper.com,2005:Incident/185660612023-09-21T14:30:00+02:002023-09-21T15:33:07+02:00Response delay for delivery and avoid profiles<p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>14:30</var> CEST</small><br><strong>Resolved</strong> - For 15-20 minutes requests with profiles like car_delivery took longer than usually or even timed out.</p>tag:status.graphhopper.com,2005:Incident/157661882023-01-03T21:50:01+01:002023-01-03T22:15:23+01:00External geocoding provider nettoolkit has high error count<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>21:50</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>21:15</var> CET</small><br><strong>Identified</strong> - The issue has been identified and we've reached out to nettoolkit.</p>tag:status.graphhopper.com,2005:Incident/127073182022-11-03T17:21:52+01:002022-11-03T17:21:52+01:00Partial Outage of Isochrone and Routing API<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:21</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:04</var> CET</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:04</var> CET</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:00</var> CET</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.graphhopper.com,2005:Incident/107530442022-08-03T16:41:53+02:002022-08-03T16:48:34+02:00Partial downtime for outdoor vehicle profiles<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:41</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p>tag:status.graphhopper.com,2005:Incident/106553732022-07-21T08:47:51+02:002022-07-21T10:28:10+02:00Internal network issues leading to rare failures<p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>08:47</var> CEST</small><br><strong>Resolved</strong> - No further network problems occurred for us.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>21:20</var> CEST</small><br><strong>Monitoring</strong> - Due to attacks on our hosting provider, there may be isolated network problems. Until this moment we observed two short (30sec) periods with internal connection issues.</p>tag:status.graphhopper.com,2005:Incident/106344392022-07-14T04:21:00+02:002022-07-19T09:13:03+02:00TomTom add-on: Routing API partially down<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>04:21</var> CEST</small><br><strong>Resolved</strong> - There was a period of 13 minutes where not all requests succeeded</p>tag:status.graphhopper.com,2005:Incident/100506532022-05-22T20:08:07+02:002022-05-22T20:08:07+02:00Geocoding API affected<p><small>May <var data-var='date'>22</var>, <var data-var='time'>20:08</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'>22</var>, <var data-var='time'>20:03</var> CEST</small><br><strong>Identified</strong> - Geocoding API is partially down for selected providers nominatim and opencagedata.</p>tag:status.graphhopper.com,2005:Incident/99326302022-05-06T22:55:39+02:002022-05-06T22:55:39+02:00Network Instability<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>22:55</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'> 6</var>, <var data-var='time'>21:30</var> CEST</small><br><strong>Monitoring</strong> - Due to attacks towards our hosting provider we experienced rare connection problems to some of our backend servers for a few minutes. We are monitoring the situation closely and re-route the traffic accordingly.</p>tag:status.graphhopper.com,2005:Incident/93377272022-02-17T04:57:40+01:002022-02-17T04:57:45+01:00Statistics are currently unavailable<p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>04:57</var> CET</small><br><strong>Resolved</strong> - The problem has been resolved. Unfortunately only new data can be accessed.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>00:00</var> CET</small><br><strong>Identified</strong> - A major incident happened in our statistic cluster. We are working on restoring the cluster.</p>tag:status.graphhopper.com,2005:Incident/91693322022-01-26T18:53:27+01:002022-01-26T18:53:27+01:00Errors for new profiles<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>18:53</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>18:09</var> CET</small><br><strong>Monitoring</strong> - The new profiles should work again.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>17:46</var> CET</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p>tag:status.graphhopper.com,2005:Incident/91680282022-01-26T15:18:58+01:002022-01-26T15:43:25+01:00Route Optimization Slow Down<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>15:18</var> CET</small><br><strong>Resolved</strong> - We have resolved the temporary issue. We are sorry for the inconveniences we caused.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>15:14</var> CET</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.graphhopper.com,2005:Incident/91468612022-01-23T16:42:17+01:002022-01-23T16:43:51+01:00Downtime<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>16:42</var> CET</small><br><strong>Resolved</strong> - We have many internal clusters that do certain tasks. One of those clusters is responsible for some of the new profiles we introduced a few weeks ago. All these clusters get automated and frequent but usually safe data updates at certain times.<br /><br />The popularity of those new profiles caused degraded performance at this cluster which stacked up in the route optimization cluster. This made it complicated to identify the root cause. Additionally the automated data update happening at the time of our investigation caused further confusion and costs us time to identify and fix the issue.<br /><br />As soon as we understood the problem in the cluster with the new profiles the route optimization cluster usually stabilizes itself, which wasn't the case this time and costed us further time as we didn't get the cluster stable.<br /><br />We now need to fix those two underlying problems that caused this unacceptable long downtime.<br /><br />We very sorry for the inconveniences we caused. Please let us know if you need further clarification and support from us.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:00</var> CET</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p>tag:status.graphhopper.com,2005:Incident/89021702021-12-21T11:34:38+01:002021-12-21T11:34:38+01:00Geocoding API sometimes returns errors<p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>11:34</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>11:25</var> CET</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>11:18</var> CET</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.graphhopper.com,2005:Incident/88752522021-12-17T18:14:54+01:002021-12-17T18:14:54+01:00monitoring issue<p><small>Dec <var data-var='date'>17</var>, <var data-var='time'>18:14</var> CET</small><br><strong>Resolved</strong> - Our monitoring tool has latency issues. Our systems are not affected.</p>tag:status.graphhopper.com,2005:Incident/88586542021-12-16T08:25:29+01:002021-12-16T11:29:51+01:00High latency for certain locations<p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>08:25</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>08:20</var> CET</small><br><strong>Monitoring</strong> - We were able to improve the issues for the Route Optimization and Matrix API.<br />Additionally latencies should be now back to normal for external systems too.</p><p><small>Dec <var data-var='date'>16</var>, <var data-var='time'>07:05</var> CET</small><br><strong>Identified</strong> - There are still issues (especially for the Route Optimization and Matrix API) degrading the latency for some of our customers.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>21:45</var> CET</small><br><strong>Monitoring</strong> - The latency problems stopped and we are monitoring our system.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>21:13</var> CET</small><br><strong>Identified</strong> - Our service provider works on the backbone connection between them and Frankfurt leading to degraded performance for customers requesting from or via Frankfurt. They currently try to re-route traffic.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>21:11</var> CET</small><br><strong>Investigating</strong> - Our API has an unusual high latency for certain geographical locations.</p>tag:status.graphhopper.com,2005:Incident/88254752021-12-12T13:57:20+01:002021-12-12T14:01:08+01:00Connection problems to APIs<p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>13:57</var> CET</small><br><strong>Resolved</strong> - A part of all requests against our APIs lead to timeouts or connection problems. This was fixed. Only some customers were affected.</p>tag:status.graphhopper.com,2005:Incident/84207252021-11-08T10:55:19+01:002021-11-08T10:55:19+01:00The statistics shown in the dashboard are wrong<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>10:55</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>10:38</var> CET</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>09:57</var> CET</small><br><strong>Investigating</strong> - We are investigating. The routing itself is not affected.</p>tag:status.graphhopper.com,2005:Incident/84032352021-11-05T13:48:00+01:002021-11-05T17:48:16+01:00Outage<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>13:48</var> CET</small><br><strong>Resolved</strong> - A network problem of our hosting provider caused problems in our Route Optimization API clusters.</p>tag:status.graphhopper.com,2005:Incident/81243732021-09-30T22:16:06+02:002021-09-30T22:16:06+02:00Downtime<p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>22:16</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>22:11</var> CEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>22:10</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>22:10</var> CEST</small><br><strong>Investigating</strong> - Our hosting provider experienced a network outage</p>tag:status.graphhopper.com,2005:Incident/81185072021-09-30T08:48:28+02:002021-09-30T08:48:28+02:00No login possible to Dashboard<p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>08:48</var> CEST</small><br><strong>Resolved</strong> - Billwerk is up again and additionally we will develop a fix to avoid this.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>08:24</var> CEST</small><br><strong>Identified</strong> - The dependent payment provider billwerk is down. We will investigate why this is currently required for our dashboard login.</p>tag:status.graphhopper.com,2005:Incident/75056932021-07-14T19:12:03+02:002021-07-14T20:25:20+02:00services are not available<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>19:12</var> CEST</small><br><strong>Resolved</strong> - The problem seems to be fixed, but we are still investigating the causes.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>19:09</var> CEST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.graphhopper.com,2005:Incident/74831872021-07-12T14:28:59+02:002021-07-12T14:28:59+02:00Outage of the async endpoint for some APIs<p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>14:28</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>14:28</var> CEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>14:28</var> CEST</small><br><strong>Monitoring</strong> - Outage of the async endpoint for the Route Optimization and Matrix API.</p>tag:status.graphhopper.com,2005:Incident/72697912021-07-01T15:54:45+02:002021-07-01T15:54:46+02:00Payment fails<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:54</var> CEST</small><br><strong>Resolved</strong> - Has been fixed by the payment provider Unzer.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>14:55</var> CEST</small><br><strong>Update</strong> - The problem persists but you can still just re-enter your credit card information like described before.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>11:03</var> CEST</small><br><strong>Investigating</strong> - We are experiencing issues with one of our payment providers. In case you get a message that your recurring credit card payment failed, we kindly ask you to just re-enter your credit card information in your API dashboard. This should resolve the problem. We apologize for the inconvenience.</p>tag:status.graphhopper.com,2005:Incident/73609822021-06-29T15:43:31+02:002021-06-29T22:41:10+02:00high network latency<p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>15:43</var> CEST</small><br><strong>Resolved</strong> - We experienced a latency increase for a few of our customers. We apologize for the caused inconveniences.</p>