Previous incidents
Sandbox Provisioning - europe-west1 Region Temporarily Disabled
Resolved May 26, 2026 at 11:30am UTC
europe-west1 Sandbox Provisioning Restored
We are happy to inform you that the issue affecting sandbox provisioning in the europe-west1 region has been resolved. The region is now fully operational and sandboxes will resume provisioning in europe-west1 as expected for both manual and hot start plays.
We apologize for any inconvenience this may have caused and thank you for your patience.
1 previous update
Sandbox Provisioning - europe-west1 Region Temporarily Disabled
Resolved May 20, 2026 at 2:16pm UTC
europe-west1 Sandbox Provisioning Restored
We are happy to inform you that the issue affecting sandbox provisioning in the europe-west1 region has been resolved. The region is now fully operational and sandboxes will resume provisioning in europe-west1 as expected for both manual and hot start plays.
We apologize for any inconvenience this may have caused and thank you for your patience.
1 previous update
Degraded Performance
Resolved May 6, 2026 at 8:23pm UTC
The performance issue affecting lab start times has been resolved. All services are operating normally. Thank you for your patience.
1 previous update
Error in track provisioning in europe-west1
Resolved Mar 24, 2026 at 2:53pm UTC
We're seeing that GCP Cloud DNS response latencies in europe-west1 have returned to normal levels, and sandbox provisioning in the region has been re-enabled.
We will continue to monitor the situation closely and take appropriate action if the issue reoccurs.
We sincerely apologize for the inconvenience and appreciate your patience while we worked to resolve this issue.
2 previous updates
Elevated error rate in VM creation requests (us-central1)
Resolved Mar 6, 2026 at 7:28am UTC
The issue was confirmed and resolved by Google Engineering team at 2026-03-05 22:30 UTC. The last errors we received were one hour prior at 21:30 UTC. To confirm, less than 0.1% of plays were affected.
The root cause according to the Google Engineers was due to an internal operation reaching an internal quota in the us-central1-a zone. The issue was mitigated by increasing the internal quota.
We will continue to monitor for these specific issues going forward.
2 previous updates