Umbraco Cloud status history
Current state: operational — “All Systems Operational” per https://status.umbraco.io (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do Umbraco Cloud incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Heartcore GraphQL and REST API elevated error rates — 23.1 h (2026-03-02 15:07 UTC). Excluded, never estimated: 16 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (24)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 07:28 UTC | Umbraco Cloud Portal Unavailable for a subset of users | resolved | minor | 11 min |
| 2026-08-18 14:46 UTC | CI/CD Deployments Failing on Umbraco Cloud | resolved | major | 5 h 56 min |
| 2026-07-29 10:55 UTC | Increased number of hanging automatic upgrades on Umbraco Cloud | resolved | major | 21 h 50 min |
| 2026-06-03 09:27 UTC | CI/CD delays in the UK South region | resolved | major | 3 h 42 min |
| 2026-04-29 21:38 UTC | Degraded performance for provisioning environments on Umbraco Cloud. | resolved | minor | 13 h 08 min |
| 2026-04-21 13:01 UTC | Umbraco Cloud – Degraded Performance (Slow Loading Times) | resolved | minor | 2 h 16 min |
| 2026-04-21 07:28 UTC | Unable to create new projects, add environments and upgrade plans | resolved | major | 8 h 58 min |
| 2026-03-02 15:07 UTC | Heartcore GraphQL and REST API elevated error rates | resolved | major | 23 h 09 min |
| 2026-02-04 13:04 UTC | Unable to create new Heartcore projects on Umbraco Cloud | resolved | major | — |
| 2026-02-04 13:02 UTC | Degraded Performance on Deployments Between Environments in multiple regions | resolved | major | — |
| 2026-02-04 13:00 UTC | Umbraco Cloud Service Disruption | resolved | major | — |
| 2026-02-04 12:53 UTC | Umbraco Cloud Service Disruption - Unable to Create Baseline Children | resolved | major | — |
| 2026-02-04 12:43 UTC | Unable to delete environments | resolved | major | — |
| 2026-02-04 12:28 UTC | Umbraco Cloud - Unable to create new environments | resolved | major | — |
| 2026-02-04 12:22 UTC | Heartcore Rest API and Preview API not applying create/update/delete content operations | resolved | major | — |
| 2026-02-04 12:13 UTC | Umbraco Heartcore - Notification Emails Not Being Sent on Workflow or Content Updates | resolved | major | — |
| 2026-02-04 12:09 UTC | Umbraco Cloud Service Disruption | resolved | critical | — |
| 2026-02-04 12:06 UTC | Umbraco Heartcore GraphQL Incorrect Responses | resolved | major | — |
| 2026-02-04 12:02 UTC | Unable to view projects in Umbraco Cloud Portal | resolved | major | — |
| 2026-02-04 12:00 UTC | Users unable to activate CI/CD flow in Umbraco Cloud Portal | resolved | major | — |
| 2026-02-04 09:27 UTC | Umbraco ID Disruption | resolved | critical | — |
| 2026-02-04 09:24 UTC | Intermittent Availability Issues on Umbraco Cloud and Cloud Portal | resolved | major | — |
| 2026-02-04 09:19 UTC | Users Unable to Sign In to Umbraco ID | resolved | critical | — |
| 2026-02-04 09:10 UTC | Custom Hostnames, Heartcore GraphQL APIs & umbraco.com returning 500 Errors | resolved | critical | — |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Umbraco Cloud with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"umbraco-cloud"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
