Blank
Umbraco Status page
Umbraco Status page
Welcome to the Umbraco status page. On this page, you can see the current operational status as well as plans for scheduled maintenance and automatic upgrades for our cloud offerings (Umbraco Cloud and Umbraco Heartcore) as well as related services and websites.
Subscribe to updates above to get the latest status send straight to your inbox.
If you’re experience issues with your cloud project which does not seem to relate to the current operational status, please go to Our Umbraco and search for the issue or reach out to the Umbraco Support in the portal chat.
Deploy, Workflow, Engage, UI Builder, Commerce licenses unable to validate
Incident
Report for Umbraco Statuspage
Resolved
Incident Summary – July 3, 2025
On July 3, 2025, between 1:15 PM and 1:35 PM UTC, a configuration change to the licensing service caused it to return invalid responses during license revalidation.
Impact:
During this period, affected products behaved as if unlicensed:
- Commerce – Unable to process new orders
- Engage – Stopped tracking, personalizing, and A/B testing
- UI Builder, Workflow, Deploy – Minimal impact; related CMS features were unavailable
Resolution:
Engineering identified and resolved the misconfiguration at 1:35 PM UTC, shortly after customer reports surfaced. Functionality was restored without further intervention.
We apologize for the disruption and are reviewing safeguards to prevent similar incidents.
On July 3, 2025, between 1:15 PM and 1:35 PM UTC, a configuration change to the licensing service caused it to return invalid responses during license revalidation.
Impact:
During this period, affected products behaved as if unlicensed:
- Commerce – Unable to process new orders
- Engage – Stopped tracking, personalizing, and A/B testing
- UI Builder, Workflow, Deploy – Minimal impact; related CMS features were unavailable
Resolution:
Engineering identified and resolved the misconfiguration at 1:35 PM UTC, shortly after customer reports surfaced. Functionality was restored without further intervention.
We apologize for the disruption and are reviewing safeguards to prevent similar incidents.