Namespace incident

Increased error rate in a single compute shard

Resolved after 7 minutes, affecting Artifacts and Container Registry and 1 more, on August 7, 2026.

monitoring Aug 07, 2026, 06:42 AM UTC

The mitigation is applied and errors rates have dropped.

Started
Aug 07, 2026, 06:35 AM UTC
Resolved
Aug 07, 2026, 06:42 AM UTC
Duration
7m
Detected by Pingoru
Aug 07, 2026, 06:35 AM UTC

Affected components

ArtifactsContainer RegistryGitHub RunnersPreviewsRemote BuildersDevboxesLinux amd64Linux arm64Linux arm64 on Apple SiliconMacOS arm64

Update timeline

  1. investigating Aug 07, 2026, 06:35 AM UTC

    We were alerted to an elevated error rate to one of our compute shard. This impacts instance creation for a subset of requests and communication with running instances in this shard.

  2. identified Aug 07, 2026, 06:40 AM UTC

    We identified the source of the problem and implemented a mitigation

  3. monitoring Aug 07, 2026, 06:42 AM UTC

    The mitigation is applied and errors rates have dropped.

  4. resolved Aug 07, 2026, 06:42 AM UTC

    All systems are operational.

Your product runs on more than Namespace

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →