User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
castle.io · Cloud & developer
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 424 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 232 ms | 0 |
| 03:45 | 0 | 0.0 | 224 ms | 0 |
| 04:00 | 0 | 0.0 | 668 ms | 0 |
| 04:15 | 0 | 0.0 | 1041 ms | 0 |
| 04:30 | 0 | 0.0 | 334 ms | 0 |
| 04:45 | 0 | 0.0 | 433 ms | 0 |
| 05:00 | 0 | 0.0 | 1166 ms | 0 |
| 05:15 | 0 | 0.0 | 196 ms | 0 |
| 05:30 | 0 | 0.0 | 406 ms | 0 |
| 05:45 | 0 | 0.0 | 434 ms | 0 |
| 06:00 | 0 | 0.0 | 513 ms | 0 |
| 06:15 | 0 | 0.0 | 575 ms | 0 |
| 06:30 | 0 | 0.0 | 346 ms | 0 |
| 06:45 | 0 | 0.0 | 296 ms | 0 |
| 07:00 | 0 | 0.0 | 394 ms | 0 |
| 07:15 | 0 | 0.0 | 369 ms | 0 |
| 07:30 | 0 | 0.0 | 413 ms | 0 |
| 07:45 | 0 | 0.0 | 453 ms | 0 |
| 08:00 | 0 | 0.0 | 419 ms | 0 |
| 08:15 | 0 | 0.0 | 468 ms | 0 |
| 08:30 | 0 | 0.0 | 415 ms | 0 |
| 08:45 | 0 | 0.0 | 473 ms | 0 |
| 09:00 | 0 | 0.0 | 368 ms | 0 |
| 09:15 | 0 | 0.0 | 360 ms | 0 |
| 09:30 | 0 | 0.0 | 227 ms | 0 |
| 09:45 | 0 | 0.0 | 418 ms | 0 |
| 10:00 | 0 | 0.0 | 310 ms | 0 |
| 10:15 | 0 | 0.0 | 383 ms | 0 |
| 10:30 | 0 | 0.0 | 665 ms | 0 |
| 10:45 | 0 | 0.0 | 491 ms | 0 |
| 11:00 | 0 | 0.0 | 667 ms | 0 |
| 11:15 | 0 | 0.0 | 344 ms | 0 |
| 11:30 | 0 | 0.0 | 370 ms | 0 |
| 11:45 | 0 | 0.0 | 289 ms | 0 |
| 12:00 | 0 | 0.0 | 688 ms | 0 |
| 12:15 | 0 | 0.0 | 415 ms | 0 |
| 12:30 | 0 | 0.0 | 539 ms | 0 |
| 12:45 | 0 | 0.0 | 292 ms | 0 |
| 13:00 | 0 | 0.0 | 624 ms | 0 |
| 13:15 | 0 | 0.0 | 335 ms | 0 |
| 13:30 | 0 | 0.0 | 406 ms | 0 |
| 13:45 | 0 | 0.0 | 551 ms | 0 |
| 14:00 | 0 | 0.0 | 381 ms | 0 |
| 14:15 | 0 | 0.0 | 401 ms | 0 |
| 14:30 | 0 | 0.0 | 335 ms | 0 |
| 14:45 | 0 | 0.0 | 430 ms | 0 |
| 15:00 | 0 | 0.0 | 464 ms | 0 |
| 15:15 | 0 | 0.0 | 424 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 Castle 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 Castle goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Castle 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 Castle 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 Castle'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.