Namespace incident

Elevated error rate in our control plane

Minor Resolved View vendor source →

Namespace experienced a minor incident on August 12, 2026 affecting Artifacts and Container Registry and 1 more component, lasting 49m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 03:25 PM UTC
Resolved
Aug 12, 2026, 04:15 PM UTC
Duration
49m
Detected by Pingoru
Aug 12, 2026, 03:25 PM UTC

Affected components

ArtifactsContainer RegistryGitHub RunnersDevboxesSAML SSOSocial SSO

Update timeline

  1. investigating Aug 12, 2026, 03:25 PM UTC

    Status: Investigating We're seeing an elevated error rate in our control plane. The team is investigating. Affected components Social SSO (Degraded performance) GitHub Runners (Degraded performance) Container Registry (Degraded performance) Artifacts (Degraded performance) SAML SSO (Degraded performance)

  2. identified Aug 12, 2026, 03:51 PM UTC

    Status: Identified We have identified the issue, and it is focused on IAM, our team is working on mitigation. Affected components Container Registry (Operational) Artifacts (Operational) SAML SSO (Partial outage) Devboxes (Operational) Social SSO (Partial outage) GitHub Runners (Operational)

  3. monitoring Aug 12, 2026, 04:01 PM UTC

    Status: Monitoring Our fix has rolled out and we are seeing signs of recovery. The team continues to monitor the situation. Affected components Container Registry (Operational) Artifacts (Operational) SAML SSO (Operational) Devboxes (Operational) Social SSO (Operational) GitHub Runners (Operational)

  4. resolved Aug 12, 2026, 04:15 PM UTC

    Status: Resolved We've confirmed the fix resolves the root cause and we're seeing full recovery. Affected components Social SSO (Operational) GitHub Runners (Operational) Container Registry (Operational) Artifacts (Operational) SAML SSO (Operational) Devboxes (Operational)