User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: E-Mail, Intranet, and 4 other services are down; Publications (external access) is degraded | E-Mail, Intranet, and 4 other services are down; Publications (external access) is ...
Source: the vendor's status page · We are not affiliated with GFZ.
Estimated fix: Not enough GFZ history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
Reachable from all 4 regions we check from.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 1233 ms.
Minor incident
E-Mail, Intranet, and 4 other services are down; Publications (external access) is degraded | E-Mail, Intranet, and 4 other services are down; Publications (external access) is degraded | E-Mail, Intranet, and 4 other services are down; Publications (external access) is degraded | E-Mail, Intranet, Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 794 ms | 0 |
| Mon 23 | 0 | 0.0 | 1281 ms | 0 |
| Tue 01 | 0 | 0.0 | 1448 ms | 0 |
| Tue 03 | 0 | 0.0 | 849 ms | 0 |
| Tue 05 | 0 | 0.0 | 1291 ms | 0 |
| Tue 07 | 0 | 0.0 | 1299 ms | 0 |
| Tue 09 | 0 | 0.0 | 1293 ms | 0 |
| Tue 11 | 0 | 0.0 | 845 ms | 0 |
| Tue 14 | 0 | 0.0 | 1276 ms | 0 |
| Tue 16 | 0 | 0.0 | 1220 ms | 0 |
| Tue 18 | 0 | 0.0 | 1249 ms | 0 |
| Tue 20 | 0 | 0.0 | 1276 ms | 0 |
| Tue 23 | 0 | 0.0 | 1172 ms | 0 |
| Wed 01 | 0 | 0.0 | 1322 ms | 0 |
| Wed 03 | 0 | 0.0 | 816 ms | 0 |
| Wed 05 | 0 | 0.0 | 1368 ms | 0 |
| Wed 08 | 0 | 0.0 | 1400 ms | 0 |
| Wed 10 | 0 | 0.0 | 1345 ms | 0 |
| Wed 12 | 0 | 0.0 | 1352 ms | 0 |
| Wed 14 | 0 | 0.0 | 1330 ms | 0 |
| Wed 16 | 0 | 0.0 | 1240 ms | 0 |
| Wed 18 | 0 | 0.0 | 786 ms | 0 |
| Wed 21 | 0 | 0.0 | 1352 ms | 0 |
| Wed 23 | 0 | 0.0 | 1302 ms | 0 |
| Thu 01 | 0 | 0.0 | 1252 ms | 0 |
| Thu 03 | 0 | 0.0 | 1408 ms | 0 |
| Thu 05 | 0 | 0.0 | 1328 ms | 0 |
| Thu 07 | 0 | 0.0 | 1207 ms | 0 |
| Thu 09 | 0 | 0.0 | 1287 ms | 0 |
| Thu 11 | 0 | 0.0 | 1295 ms | 0 |
| Thu 13 | 0 | 0.0 | 1277 ms | 0 |
| Thu 15 | 0 | 0.0 | 1274 ms | 0 |
| Thu 17 | 0 | 0.0 | 1344 ms | 0 |
| Thu 19 | 0 | 0.0 | 1377 ms | 0 |
| Thu 22 | 0 | 0.0 | 1105 ms | 0 |
| Fri 00 | 0 | 0.0 | 1367 ms | 0 |
| Fri 02 | 0 | 0.0 | 1343 ms | 0 |
| Fri 04 | 0 | 0.0 | 1096 ms | 0 |
| Fri 06 | 0 | 0.0 | 1289 ms | 0 |
| Fri 07 | 0 | 0.0 | 1299 ms | 0 |
| Fri 09 | 0 | 0.0 | 802 ms | 0 |
| Fri 11 | 0 | 0.0 | 1312 ms | 0 |
| Fri 13 | 0 | 0.0 | 1325 ms | 0 |
| Fri 15 | 0 | 0.0 | 1225 ms | 0 |
| Fri 17 | 0 | 0.0 | 1304 ms | 0 |
| Fri 18 | 0 | 0.0 | 1367 ms | 0 |
| Fri 20 | 0 | 0.0 | 1349 ms | 0 |
| Fri 22 | 0 | 0.0 | 1233 ms | 0 |
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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for GFZ yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when GFZ goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GFZ alerts to Slack, Discord or a webhook — free.
GFZ, at gfz.de, is one of the Cloud & developer services we monitor. Das GFZ Helmholtz-Zentrum für Geoforschung ist das nationale Zentrum für die Erforschung der festen Erde. Wir untersuchen die Geosphäre im hochkomplexen System Erde mit den weiteren Teilsystemen und ihren ineinandergreifenden Kreisläufen und weitverzweigten Ursache-Wirkungs-Ketten.
GFZ publishes an official status page at status.gfz.de; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1245 ms average, 802–1367 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: E-Mail, Intranet, and 4 other services are down; Publications (external access) is degraded | E-Mail, Intranet, and 4 other services are down; Publications (external access) is ...
We have not recorded a public GFZ incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1245 ms on average over the last 24 hours (802–1367 ms). Latest regional checks: US East 521 ms, US West 816 ms, Europe 214 ms, Asia-Pacific 1268 ms.
Yes, at https://status.gfz.de.
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 GFZ here at once, the problem is on GFZ'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 GFZ. 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.