User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
cloudfanatic.net · Cloud & developer
Is Cloudfanatic down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → cloudfanatic.net—
Your browser → us—
Our checksReaching it
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
Reaching it
Last check reached it in 403 ms · 4 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 |
|---|---|---|---|---|
| 04:30 | 0 | 0.0 | 474 ms | 0 |
| 04:45 | 0 | 0.0 | 704 ms | 0 |
| 05:00 | 0 | 0.0 | 1298 ms | 0 |
| 05:15 | 0 | 0.0 | 537 ms | 0 |
| 05:30 | 0 | 0.0 | 622 ms | 0 |
| 05:45 | 0 | 0.0 | 448 ms | 0 |
| 06:00 | 0 | 0.0 | 895 ms | 0 |
| 06:15 | 0 | 0.0 | 687 ms | 0 |
| 06:30 | 0 | 0.0 | 311 ms | 0 |
| 06:45 | 0 | 0.0 | 701 ms | 0 |
| 07:00 | 0 | 0.0 | 730 ms | 0 |
| 07:15 | 0 | 0.0 | 638 ms | 0 |
| 07:30 | 0 | 0.0 | 758 ms | 0 |
| 07:45 | 0 | 0.0 | 513 ms | 0 |
| 08:00 | 0 | 0.0 | 798 ms | 0 |
| 08:15 | 0 | 0.0 | 924 ms | 0 |
| 08:30 | 0 | 0.0 | 614 ms | 0 |
| 08:45 | 0 | 0.0 | 642 ms | 0 |
| 09:00 | 0 | 0.0 | 590 ms | 0 |
| 09:15 | 0 | 0.0 | 437 ms | 0 |
| 09:30 | 0 | 0.0 | 522 ms | 0 |
| 09:45 | 0 | 0.0 | 748 ms | 0 |
| 10:00 | 0 | 0.0 | 736 ms | 0 |
| 10:15 | 0 | 0.0 | 525 ms | 0 |
| 10:30 | 0 | 0.0 | 734 ms | 0 |
| 10:45 | 0 | 0.0 | 464 ms | 0 |
| 11:00 | 0 | 0.0 | 894 ms | 0 |
| 11:15 | 0 | 0.0 | 478 ms | 0 |
| 11:30 | 0 | 0.0 | 545 ms | 0 |
| 11:45 | 0 | 0.0 | 405 ms | 0 |
| 12:00 | 0 | 0.0 | 740 ms | 0 |
| 12:15 | 0 | 0.0 | 989 ms | 0 |
| 12:30 | 0 | 0.0 | 1085 ms | 0 |
| 12:45 | 0 | 0.0 | 367 ms | 0 |
| 13:00 | 0 | 0.0 | 648 ms | 0 |
| 13:15 | 0 | 0.0 | 746 ms | 0 |
| 13:30 | 0 | 0.0 | 698 ms | 0 |
| 13:45 | 0 | 0.0 | 530 ms | 0 |
| 14:00 | 0 | 0.0 | 856 ms | 0 |
| 14:15 | 0 | 0.0 | 558 ms | 0 |
| 14:30 | 0 | 0.0 | 539 ms | 0 |
| 14:45 | 0 | 0.0 | 803 ms | 0 |
| 15:00 | 0 | 0.0 | 757 ms | 0 |
| 15:15 | 0 | 0.0 | 720 ms | 0 |
| 15:30 | 0 | 0.0 | 352 ms | 0 |
| 15:45 | 0 | 0.0 | 611 ms | 0 |
| 16:00 | 0 | 0.0 | 933 ms | 0 |
| 16:15 | 0 | 0.0 | 403 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 Cloudfanatic 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 Cloudfanatic yet. Outages of 10 minutes or more get their own page here.
Having trouble with Cloudfanatic?
One report per service every 10 minutes from this network. No account.
Follow Cloudfanatic
Get an email when Cloudfanatic goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cloudfanatic alerts to Slack, Discord or a webhook — free.
Questions
Is Cloudfanatic down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Cloudfanatic not working for me but the status is fine. What now?
If Cloudfanatic 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 Cloudfanatic's side.
How does Damn is it down decide Cloudfanatic'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 Cloudfanatic checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.