User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
umbraco.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 375 ms · 3 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 654 ms | 0 |
| 03:30 | 0 | 0.0 | 812 ms | 0 |
| 03:45 | 0 | 0.0 | 511 ms | 0 |
| 04:00 | 0 | 0.0 | 972 ms | 0 |
| 04:15 | 0 | 0.0 | 1962 ms | 0 |
| 04:30 | 0 | 0.0 | 1092 ms | 0 |
| 04:45 | 0 | 0.0 | 1169 ms | 0 |
| 05:00 | 0 | 0.0 | 1810 ms | 0 |
| 05:15 | 0 | 0.0 | 415 ms | 0 |
| 05:30 | 0 | 0.0 | 974 ms | 0 |
| 05:45 | 0 | 0.0 | 1216 ms | 0 |
| 06:00 | 0 | 0.0 | 1399 ms | 0 |
| 06:15 | 0 | 0.0 | 1120 ms | 0 |
| 06:30 | 0 | 0.0 | 992 ms | 0 |
| 06:45 | 0 | 0.0 | 1055 ms | 0 |
| 07:00 | 0 | 0.0 | 1585 ms | 0 |
| 07:15 | 0 | 0.0 | 1982 ms | 0 |
| 07:30 | 0 | 0.0 | 645 ms | 0 |
| 07:45 | 0 | 0.0 | 860 ms | 0 |
| 08:00 | 0 | 0.0 | 1119 ms | 0 |
| 08:15 | 0 | 0.0 | 1128 ms | 0 |
| 08:30 | 0 | 0.0 | 560 ms | 0 |
| 08:45 | 0 | 0.0 | 1098 ms | 0 |
| 09:00 | 0 | 0.0 | 559 ms | 0 |
| 09:15 | 0 | 0.0 | 960 ms | 0 |
| 09:30 | 0 | 0.0 | 1566 ms | 0 |
| 09:45 | 0 | 0.0 | 991 ms | 0 |
| 10:00 | 0 | 0.0 | 499 ms | 0 |
| 10:15 | 0 | 0.0 | 1440 ms | 0 |
| 10:30 | 0 | 0.0 | 399 ms | 0 |
| 10:45 | 0 | 0.0 | 1514 ms | 0 |
| 11:00 | 0 | 0.0 | 1541 ms | 0 |
| 11:15 | 0 | 0.0 | 2704 ms | 0 |
| 11:30 | 0 | 0.0 | 1274 ms | 0 |
| 11:45 | 0 | 0.0 | 1233 ms | 0 |
| 12:00 | 0 | 0.0 | 1036 ms | 0 |
| 12:15 | 0 | 0.0 | 1023 ms | 0 |
| 12:30 | 0 | 0.0 | 1799 ms | 0 |
| 12:45 | 0 | 0.0 | 1595 ms | 0 |
| 13:00 | 0 | 0.0 | 568 ms | 0 |
| 13:15 | 0 | 0.0 | 1736 ms | 0 |
| 13:30 | 0 | 0.0 | 946 ms | 0 |
| 13:45 | 0 | 0.0 | 1283 ms | 0 |
| 14:00 | 0 | 0.0 | 1428 ms | 0 |
| 14:15 | 0 | 0.0 | 1366 ms | 0 |
| 14:30 | 0 | 0.0 | 1677 ms | 0 |
| 14:45 | 0 | 0.0 | 1268 ms | 0 |
| 15:00 | 0 | 0.0 | 375 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 Umbraco Cloud 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 Umbraco Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Umbraco Cloud 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 Umbraco Cloud 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 Umbraco Cloud'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.