Namespace incident

Failing instance lists and a subset of RPCs

Resolved after 41 minutes, affecting Compute Region (Silicon Valley, US), on October 17, 2026.

resolved Oct 17, 2026, 07:26 AM UTC

All systems are operational. The orchestrator in affected regions was not able to retrieve update configuration from our configuration sub-system, leading to failures.

Started
Oct 17, 2026, 06:45 AM UTC
Resolved
Oct 17, 2026, 07:26 AM UTC
Duration
41m
Detected by Pingoru
Oct 17, 2026, 06:45 AM UTC

Affected components

Compute Region (Silicon Valley, US)

Update timeline

  1. investigating Oct 17, 2026, 06:45 AM UTC

    All systems are operational.

  2. resolved Oct 17, 2026, 07:26 AM UTC

    All systems are operational. The orchestrator in affected regions was not able to retrieve update configuration from our configuration sub-system, leading to failures.

  3. resolved Oct 17, 2026, 07:26 AM UTC

    All systems are operational. The orchestrator in affected regions was not able to retrieve update configuration from our configuration sub-system, leading to failures.

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 →