Engineering applied a forward correction and as of 14:45 UTC we are observing nominal behavior across all clusters. Instances should now initialize as expected. As such, we are considering this incident resolved.
No further updates.
Posted Jun 21, 2023 - 14:56 UTC
Investigating
As of 13:03 UTC, we were alerted to an issue impacting all instances that are attempting to initialize across all available clusters. Engineering is aware, and actively working towards remediation and correction. The scope extends to customers who are attempting to initialize their instances; those instances will display the loading screen and fail to load.
Customers who have active cloud instances that do not need to be restarted or reinitialized will not experience symptoms. We will continue to provide updates as information is shared.
Posted Jun 21, 2023 - 13:24 UTC
This incident affected: Grafana (AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-4, AWS Singapore - prod-ap-southeast-1, AWS US East - prod-us-east-0, AWS US East - prod-us-east-2, Azure US Central - us-central2, Azure Netherlands - prod-eu-west-3, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Singapore - prod-ap-southeast-0, GCP UK - prod-gb-south-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-3, GCP US Central - prod-us-central-4, GCP US East - prod-us-east-1, play.grafana.org).