New and recently unpaused/unarchived Grafana Cloud instances unable to start.

Resolved

The incident has been resolved. We applied an update to all Grafana Cloud instances, which inadvertently restarted instances regardless of whether they were active or not. This caused heavy load on our control plane, causing slower startup times.

Update

We identified the issue and applied the fix. We're currently monitoring the situation - there should be no issue with creating and unpausing/unarchiving instances anymore.

Investigating

Users may see slower startup times for new, or previously inactive Grafana Cloud instances in all clusters. We're currently investigating the issue.