Is Client Challenge down right now?
statesman.com
Checking statesman.com…
Asking our locations to reach the site. This takes a few seconds.
- Uptime, 24 hours
- 100 %
- Uptime, 7 days
- 100 %
- Uptime, 30 days
- 100 %
Based on 1 day of checks so far. Checks that failed because of how we test, not because of the site, are left out.
Response time per hour, last 24 hours
Response time by location, last 24 hours
| Location | Average response | Reached |
|---|---|---|
| Berlin 1, Germany | 20 ms | 2 of 2 checks |
| Falkenstein, Germany | 56 ms | 3 of 3 checks |
Each check runs from all locations at once. A location far from the site’s servers answers later; that says nothing about the site being slow.
Outage history
No confirmed outage on record. An outage is listed once Client Challenge could not be reached from at least two locations in two checks in a row.
Recent checks
| Time | Status | Locations | Response |
|---|---|---|---|
| 2026-10-10 07:12 UTC | Up | 1 of 1 | 70 ms |
| 2026-10-10 06:09 UTC | Up | 1 of 1 | 19 ms |
| 2026-10-10 05:06 UTC | Up | 1 of 1 | 51 ms |
| 2026-10-10 04:01 UTC | Up | 1 of 1 | 20 ms |
| 2026-10-10 03:21 UTC | Up | 1 of 1 | 46 ms |
Comments
No comments yet. Be the first to say what you are seeing.
About Client Challenge
Client Challenge
Visit statesman.comTitle and description as published by the site.
We can reach it, but you cannot?
- Reload the page without the cache: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
- Open the site in a private window. If it works there, clear the cookies and cache for statesman.com.
- Try another network, such as mobile data. If that works, the problem is with your provider or router.
- Switch to a public DNS resolver such as 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
- Turn off VPNs, proxies and ad blockers for a moment. Some sites refuse those connections.
Embed a status badge
Show the current status of Client Challenge on your own page or in a README. The badge updates by itself.