Namespace incident
Small subset of artifact and cache requests in Illinois region failing
Namespace experienced a minor incident on September 24, 2026 affecting Artifacts and Illinois, US and 1 more component, lasting 1h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 24, 2026, 05:16 PM UTC
Status: Investigating We were alerted to an issue with the system backing storage for Artifacts and Cache storage in our Illinois region. A small number of requests is stalling and timing out. Affected components Bazel (Degraded performance) Artifacts (Degraded performance) Turborepo (Degraded performance) Gradle (Degraded performance) HTTP Cache (Degraded performance) Illinois, US (Degraded performance)
- identified Sep 24, 2026, 05:38 PM UTC
Status: Identified We identified and stopped a single replica that was causing the stalls. Affected components Gradle (Degraded performance) HTTP Cache (Degraded performance) Illinois, US (Operational) Bazel (Degraded performance) Artifacts (Degraded performance) Turborepo (Degraded performance)
- identified Sep 24, 2026, 06:00 PM UTC
Status: Identified The new replica showed the same stalling pattern. We identified a networking misconfiguration that's causing the issue. Affected components Turborepo (Degraded performance) Gradle (Degraded performance) HTTP Cache (Degraded performance) Illinois, US (Operational) Bazel (Degraded performance) Artifacts (Degraded performance)
- monitoring Sep 24, 2026, 06:37 PM UTC
Status: Monitoring We disabled all affected replicas. Affected components Illinois, US (Operational) Bazel (Operational) Artifacts (Operational) Turborepo (Operational) Gradle (Operational) HTTP Cache (Operational)
- resolved Sep 24, 2026, 06:45 PM UTC
Status: Resolved Error rates have recovered, all systems operational. Affected components HTTP Cache (Operational) Illinois, US (Operational) Bazel (Operational) Artifacts (Operational) Turborepo (Operational) Gradle (Operational)