User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
cloudsigma.com · 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 102 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:00 | 0 | 0.0 | 203 ms | 0 |
| 07:15 | 0 | 0.0 | 115 ms | 0 |
| 07:30 | 0 | 0.0 | 209 ms | 0 |
| 07:45 | 0 | 0.0 | 179 ms | 0 |
| 08:00 | 0 | 0.0 | 142 ms | 0 |
| 08:15 | 0 | 0.0 | 473 ms | 0 |
| 08:30 | 0 | 0.0 | 188 ms | 0 |
| 08:45 | 0 | 0.0 | 165 ms | 0 |
| 09:00 | 0 | 0.0 | 186 ms | 0 |
| 09:15 | 0 | 0.0 | 234 ms | 0 |
| 09:30 | 0 | 0.0 | 579 ms | 0 |
| 09:45 | 0 | 0.0 | 140 ms | 0 |
| 10:00 | 0 | 0.0 | 363 ms | 0 |
| 10:15 | 0 | 0.0 | 110 ms | 0 |
| 10:30 | 0 | 0.0 | 306 ms | 0 |
| 10:45 | 0 | 0.0 | 268 ms | 0 |
| 11:00 | 0 | 0.0 | 411 ms | 0 |
| 11:15 | 0 | 0.0 | 162 ms | 0 |
| 11:30 | 0 | 0.0 | 391 ms | 0 |
| 11:45 | 0 | 0.0 | 170 ms | 0 |
| 12:00 | 0 | 0.0 | 482 ms | 0 |
| 12:15 | 0 | 0.0 | 126 ms | 0 |
| 12:30 | 0 | 0.0 | 385 ms | 0 |
| 12:45 | 0 | 0.0 | 363 ms | 0 |
| 13:00 | 0 | 0.0 | 491 ms | 0 |
| 13:15 | 0 | 0.0 | 149 ms | 0 |
| 13:30 | 0 | 0.0 | 348 ms | 0 |
| 13:45 | 0 | 0.0 | 869 ms | 0 |
| 14:00 | 0 | 0.0 | 319 ms | 0 |
| 14:15 | 0 | 0.0 | 177 ms | 0 |
| 14:30 | 0 | 0.0 | 358 ms | 0 |
| 14:45 | 0 | 0.0 | 184 ms | 0 |
| 15:00 | 0 | 0.0 | 362 ms | 0 |
| 15:15 | 0 | 0.0 | 171 ms | 0 |
| 15:30 | 0 | 0.0 | 294 ms | 0 |
| 15:45 | 0 | 0.0 | 225 ms | 0 |
| 16:00 | 0 | 0.0 | 320 ms | 0 |
| 16:15 | 0 | 0.0 | 254 ms | 0 |
| 16:30 | 0 | 0.0 | 310 ms | 0 |
| 16:45 | 0 | 0.0 | 342 ms | 0 |
| 17:00 | 0 | 0.0 | 263 ms | 0 |
| 17:15 | 0 | 0.0 | 173 ms | 0 |
| 17:30 | 0 | 0.0 | 188 ms | 0 |
| 17:45 | 0 | 0.0 | 150 ms | 0 |
| 18:00 | 0 | 0.0 | 234 ms | 0 |
| 18:15 | 0 | 0.0 | 168 ms | 0 |
| 18:30 | 0 | 0.0 | 129 ms | 0 |
| 18:45 | 0 | 0.0 | 173 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 Cloudsigma 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 Cloudsigma goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cloudsigma 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 Cloudsigma 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 Cloudsigma'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.