User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
ionos.de · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 528 ms · 1 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 455 ms | 0 |
| 03:15 | 0 | 0.0 | 604 ms | 0 |
| 03:30 | 0 | 0.0 | 722 ms | 0 |
| 03:45 | 0 | 0.0 | 645 ms | 0 |
| 04:00 | 0 | 0.0 | 671 ms | 0 |
| 04:15 | 0 | 0.0 | 2327 ms | 0 |
| 04:30 | 0 | 0.0 | 903 ms | 0 |
| 04:45 | 0 | 0.0 | 687 ms | 0 |
| 05:00 | 0 | 0.0 | 425 ms | 0 |
| 05:15 | 0 | 0.0 | 476 ms | 0 |
| 05:30 | 0 | 0.0 | 337 ms | 0 |
| 05:45 | 0 | 0.0 | 1111 ms | 0 |
| 06:00 | 0 | 0.0 | 560 ms | 0 |
| 06:15 | 0 | 0.0 | 850 ms | 0 |
| 06:30 | 0 | 0.0 | 556 ms | 0 |
| 06:45 | 0 | 0.0 | 469 ms | 0 |
| 07:00 | 0 | 0.0 | 797 ms | 0 |
| 07:15 | 0 | 0.0 | 854 ms | 0 |
| 07:30 | 0 | 0.0 | 734 ms | 0 |
| 07:45 | 0 | 0.0 | 545 ms | 0 |
| 08:00 | 0 | 0.0 | 473 ms | 0 |
| 08:15 | 0 | 0.0 | 570 ms | 0 |
| 08:30 | 0 | 0.0 | 450 ms | 0 |
| 08:45 | 0 | 0.0 | 1170 ms | 0 |
| 09:00 | 0 | 0.0 | 700 ms | 0 |
| 09:15 | 0 | 0.0 | 482 ms | 0 |
| 09:30 | 0 | 0.0 | 624 ms | 0 |
| 09:45 | 0 | 0.0 | 552 ms | 0 |
| 10:00 | 0 | 0.0 | 680 ms | 0 |
| 10:15 | 0 | 0.0 | 534 ms | 0 |
| 10:30 | 0 | 0.0 | 702 ms | 0 |
| 10:45 | 0 | 0.0 | 178 ms | 0 |
| 11:00 | 0 | 0.0 | 657 ms | 0 |
| 11:15 | 0 | 0.0 | 762 ms | 0 |
| 11:30 | 0 | 0.0 | 955 ms | 0 |
| 11:45 | 0 | 0.0 | 1262 ms | 0 |
| 12:00 | 0 | 0.0 | 844 ms | 0 |
| 12:15 | 0 | 0.0 | 409 ms | 0 |
| 12:30 | 0 | 0.0 | 556 ms | 0 |
| 12:45 | 0 | 0.0 | 1787 ms | 0 |
| 13:00 | 0 | 0.0 | 363 ms | 0 |
| 13:15 | 0 | 0.0 | 1598 ms | 0 |
| 13:30 | 0 | 0.0 | 584 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for IONOS 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 IONOS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IONOS alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If IONOS is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on IONOS's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.