Vendor Status Watch

← all vendors

Umbraco Cloud status history

Current state: operational — “All Systems Operational” per https://status.umbraco.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
3incidents, last 90 days
24incidents on record
Incidents per week, last 12 weeks:

How long do Umbraco Cloud incidents last?

7.5 hmedian incident duration8 measured
21.8 h90th percentile1 in 10 ran longer
9.0 hmedian, major/critical only5 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-16 07:28 UTCUmbraco Cloud Portal Unavailable for a subset of usersresolvedminor11 min
2026-08-18 14:46 UTCCI/CD Deployments Failing on Umbraco Cloudresolvedmajor5 h 56 min
2026-07-29 10:55 UTCIncreased number of hanging automatic upgrades on Umbraco Cloudresolvedmajor21 h 50 min
2026-06-03 09:27 UTCCI/CD delays in the UK South regionresolvedmajor3 h 42 min
2026-04-29 21:38 UTCDegraded performance for provisioning environments on Umbraco Cloud.resolvedminor13 h 08 min
2026-04-21 13:01 UTCUmbraco Cloud – Degraded Performance (Slow Loading Times)resolvedminor2 h 16 min
2026-04-21 07:28 UTCUnable to create new projects, add environments and upgrade plansresolvedmajor8 h 58 min
2026-03-02 15:07 UTCHeartcore GraphQL and REST API elevated error ratesresolvedmajor23 h 09 min
2026-02-04 13:04 UTCUnable to create new Heartcore projects on Umbraco Cloudresolvedmajor
2026-02-04 13:02 UTCDegraded Performance on Deployments Between Environments in multiple regionsresolvedmajor
2026-02-04 13:00 UTCUmbraco Cloud Service Disruptionresolvedmajor
2026-02-04 12:53 UTCUmbraco Cloud Service Disruption - Unable to Create Baseline Childrenresolvedmajor
2026-02-04 12:43 UTCUnable to delete environmentsresolvedmajor
2026-02-04 12:28 UTCUmbraco Cloud - Unable to create new environmentsresolvedmajor
2026-02-04 12:22 UTCHeartcore Rest API and Preview API not applying create/update/delete content operationsresolvedmajor
2026-02-04 12:13 UTCUmbraco Heartcore - Notification Emails Not Being Sent on Workflow or Content Updatesresolvedmajor
2026-02-04 12:09 UTCUmbraco Cloud Service Disruptionresolvedcritical
2026-02-04 12:06 UTCUmbraco Heartcore GraphQL Incorrect Responsesresolvedmajor
2026-02-04 12:02 UTCUnable to view projects in Umbraco Cloud Portalresolvedmajor
2026-02-04 12:00 UTCUsers unable to activate CI/CD flow in Umbraco Cloud Portalresolvedmajor
2026-02-04 09:27 UTCUmbraco ID Disruptionresolvedcritical
2026-02-04 09:24 UTCIntermittent Availability Issues on Umbraco Cloud and Cloud Portalresolvedmajor
2026-02-04 09:19 UTCUsers Unable to Sign In to Umbraco IDresolvedcritical
2026-02-04 09:10 UTCCustom Hostnames, Heartcore GraphQL APIs & umbraco.com returning 500 Errorsresolvedcritical

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
}