GraphHopper Outage History
8 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded GraphHopper Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 8, 2026 | Latency problems with a subset of requestsThis incident has been resolved. | 3h 38m | Resolved |
| Oct 8, 2026 | Latency problems with a subset of requestsWe are investigating the issue | -35 min | Resolved |
| Sep 20, 2026 | Geocoding with provider=gisgraphy falls now back to provider=defaultThis incident has been resolved. | 4h 30m | Resolved |
| Jun 27, 2026 | Elevated error rate for all services.This incident has been resolved. | 3h 17m | Resolved |
| Jun 9, 2026 | Geocoding Provider "Gisgraphy" Is DownThis incident has been resolved. | 30 min | Resolved |
| Feb 25, 2026 | major outage for all systemsThis incident has been resolved. | 9 min | Resolved |
| Jan 28, 2026 | Sporadic network issuesThis incident has been resolved. | 16 min | Resolved |
| Nov 24, 2025 | Monitoring MistakeWe updated our monitoring capabilities but made a mistake causing a few false alarms. This is fixed. | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next GraphHopper incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This GraphHopper Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GraphHopper acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single GraphHopper outage in this window ran 4h 30m, against a mean recovery of 1h 46m. If you depend on GraphHopper in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.