User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
graphhopper.com · Cloud & developer
Is GraphHopper down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → graphhopper.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 18 min ago. Last stored result reached it in 1278 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 1029 ms | 0 |
| Mon 15 | 0 | 0.0 | 1133 ms | 0 |
| Mon 17 | 0 | 0.0 | 1282 ms | 0 |
| Mon 19 | 0 | 0.0 | 1410 ms | 0 |
| Mon 21 | 0 | 0.0 | 1184 ms | 0 |
| Mon 23 | 0 | 0.0 | 1196 ms | 0 |
| Tue 01 | 0 | 0.0 | 1209 ms | 0 |
| Tue 03 | 0 | 0.0 | 1197 ms | 0 |
| Tue 06 | 0 | 0.0 | 1310 ms | 0 |
| Tue 08 | 0 | 0.0 | 1328 ms | 0 |
| Tue 10 | 0 | 0.0 | 1257 ms | 0 |
| Tue 12 | 0 | 0.0 | 1493 ms | 0 |
| Tue 14 | 0 | 0.0 | 1203 ms | 0 |
| Tue 16 | 0 | 0.0 | 742 ms | 0 |
| Tue 19 | 0 | 0.0 | 1149 ms | 0 |
| Tue 21 | 0 | 0.0 | 923 ms | 0 |
| Tue 23 | 0 | 0.0 | 1123 ms | 0 |
| Wed 01 | 0 | 0.0 | 1323 ms | 0 |
| Wed 04 | 0 | 0.0 | 1381 ms | 0 |
| Wed 06 | 0 | 0.0 | 1432 ms | 0 |
| Wed 08 | 0 | 0.0 | 1045 ms | 0 |
| Wed 10 | 0 | 0.0 | 1319 ms | 0 |
| Wed 13 | 0 | 0.0 | 1220 ms | 0 |
| Wed 15 | 0 | 0.0 | 1146 ms | 0 |
| Wed 17 | 0 | 0.0 | 1377 ms | 0 |
| Wed 19 | 0 | 0.0 | 583 ms | 0 |
| Wed 21 | 0 | 0.0 | 1186 ms | 0 |
| Wed 23 | 0 | 0.0 | 1209 ms | 0 |
| Thu 01 | 0 | 0.0 | 1036 ms | 0 |
| Thu 03 | 0 | 0.0 | 1214 ms | 0 |
| Thu 06 | 0 | 0.0 | 1019 ms | 0 |
| Thu 08 | 0 | 0.0 | 1093 ms | 0 |
| Thu 10 | 0 | 0.0 | 1394 ms | 0 |
| Thu 12 | 0 | 0.0 | 1102 ms | 0 |
| Thu 14 | 0 | 0.0 | 1206 ms | 0 |
| Thu 16 | 0 | 0.0 | 1306 ms | 0 |
| Thu 18 | 0 | 0.0 | 1008 ms | 0 |
| Thu 20 | 0 | 0.0 | 1126 ms | 0 |
| Thu 22 | 0 | 0.0 | 953 ms | 0 |
| Fri 00 | 0 | 0.0 | 1152 ms | 0 |
| Fri 02 | 0 | 0.0 | 1363 ms | 0 |
| Fri 04 | 0 | 0.0 | 1352 ms | 0 |
| Fri 06 | 0 | 0.0 | 1265 ms | 0 |
| Fri 08 | 0 | 0.0 | 1265 ms | 0 |
| Fri 10 | 0 | 0.0 | 606 ms | 0 |
| Fri 12 | 0 | 0.0 | 1266 ms | 0 |
| Fri 14 | 0 | 0.0 | 1201 ms | 0 |
| Fri 16 | 0 | 0.0 | 1278 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live GraphHopper badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for GraphHopper yet. Outages of 10 minutes or more get their own page here.
Having trouble with GraphHopper?
One report per service every 10 minutes from this network. No account.
Follow GraphHopper
Get an email when GraphHopper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GraphHopper alerts to Slack, Discord or a webhook — free.
About GraphHopper
We track GraphHopper (graphhopper.com) as part of the Cloud & developer group. A fast Directions API with world wide data from OpenStreetMap and route optimization. Stay independent and flexible.
GraphHopper publishes an official status page at status.graphhopper.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1129 ms average, 153–1405 ms range across 14 successful checks.
Questions
Is GraphHopper down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was GraphHopper last down?
We have not recorded a public GraphHopper incident since monitoring began 7 days ago.
What is GraphHopper's uptime?
From our own checks: 100% over 7 days of checks.
How fast does GraphHopper respond?
1129 ms on average over the last 24 hours (153–1405 ms).
Does GraphHopper have an official status page?
Yes, at https://status.graphhopper.com.
GraphHopper not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report GraphHopper here at once, the problem is on GraphHopper's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with GraphHopper. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.