Google Cloud has confirmed an incident affecting Artifact Registry in the US multiregion, which is where some of the container images used by Instruqt sandboxes are hosted. Google reports the issue was resolved for all affected users at 11:21 UTC on 31 August 2026.

The sandbox start failures we observed earlier today are consistent with this incident. During the affected period, some tracks and labs failed to start when a sandbox host referenced a container image hosted on gcr.io, including Instruqt-provided images such as gcr.io/instruqt/cloud-client. Our last observed failure was at 11:17 UTC.

Image lookups have been operating normally since. No action is needed on your side, and tracks that failed to start can be started again.

Since roughly 08:30 UTC, some tracks and labs have failed to start when a sandbox host references a container image hosted on Google Container Registry (gcr.io), including Instruqt-provided images such as gcr.io/instruqt/cloud-client. Affected sessions fail during sandbox creation rather than partway through.

The failures are intermittent. Retrying a track start will often succeed, and no configuration change is needed on your side. Tracks referencing images from other registries do not appear to be affected.

We have raised the issue with Google Cloud support and are working with them to identify the cause. We will update this notice as we learn more.