User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
calm.com · Cloud & developer
Is Calm down?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → calm.com—
Your browser → us—
Our checksNot enough checks
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, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Not enough checks
Last check reached it in 450 ms · 6 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 604 ms | 0 |
| 03:15 | 0 | 0.0 | 309 ms | 0 |
| 03:30 | 0 | 0.0 | 1053 ms | 0 |
| 03:45 | 0 | 0.0 | 277 ms | 0 |
| 04:00 | 0 | 0.0 | 681 ms | 0 |
| 04:15 | 0 | 0.0 | 850 ms | 0 |
| 04:30 | 0 | 0.0 | 350 ms | 0 |
| 04:45 | 0 | 0.0 | 499 ms | 0 |
| 05:00 | 0 | 0.0 | 1050 ms | 0 |
| 05:15 | 0 | 0.0 | 506 ms | 0 |
| 05:30 | 0 | 0.0 | 575 ms | 0 |
| 05:45 | 0 | 0.0 | 439 ms | 0 |
| 06:00 | 0 | 0.0 | 822 ms | 0 |
| 06:15 | 0 | 0.0 | 420 ms | 0 |
| 06:30 | 0 | 0.0 | 180 ms | 0 |
| 06:45 | 0 | 0.0 | 372 ms | 0 |
| 07:00 | 0 | 0.0 | 395 ms | 0 |
| 07:15 | 0 | 0.0 | 456 ms | 0 |
| 07:30 | 0 | 0.0 | 507 ms | 0 |
| 07:45 | 0 | 0.0 | 463 ms | 0 |
| 08:00 | 0 | 0.0 | 342 ms | 0 |
| 08:15 | 0 | 0.0 | 886 ms | 0 |
| 08:30 | 0 | 0.0 | 304 ms | 0 |
| 08:45 | 0 | 0.0 | 654 ms | 0 |
| 09:00 | 0 | 0.0 | 454 ms | 0 |
| 09:15 | 0 | 0.0 | 406 ms | 0 |
| 09:30 | 0 | 0.0 | 369 ms | 0 |
| 09:45 | 0 | 0.0 | 400 ms | 0 |
| 10:00 | 0 | 0.0 | 358 ms | 0 |
| 10:15 | 0 | 0.0 | 470 ms | 0 |
| 10:30 | 0 | 0.0 | 658 ms | 0 |
| 10:45 | 0 | 0.0 | 370 ms | 0 |
| 11:00 | 0 | 0.0 | 919 ms | 0 |
| 11:15 | 0 | 0.0 | 277 ms | 0 |
| 11:30 | 0 | 0.0 | 405 ms | 0 |
| 11:45 | 0 | 0.0 | 278 ms | 0 |
| 12:00 | 0 | 0.0 | 638 ms | 0 |
| 12:15 | 0 | 0.0 | 440 ms | 0 |
| 12:30 | 0 | 0.0 | 838 ms | 0 |
| 12:45 | 0 | 0.0 | 345 ms | 0 |
| 13:00 | 0 | 0.0 | 469 ms | 0 |
| 13:15 | 0 | 0.0 | 611 ms | 0 |
| 13:30 | 0 | 0.0 | 356 ms | 0 |
| 13:45 | 0 | 0.0 | 420 ms | 0 |
| 14:00 | 0 | 0.0 | 450 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed a live Calm status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Calm yet. Outages of 10 minutes or more get their own page here.
Having trouble with Calm?
One report per service every 10 minutes from this network. No account.
Follow Calm
Get an email when Calm goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Calm alerts to Slack, Discord or a webhook — free.
Questions
Is Calm down right now?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Calm not working for me but the status is fine. What now?
If Calm 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 Calm's side.
How does Damn is it down decide Calm's status?
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.
How often is Calm checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.