Is Namespace down?

Last checked 2h ago
Current status
Namespace is up

No incidents right now.

Namespace is operational right now. Last checked 2h ago; the most recent incident resolved 9h ago.

Real-time Namespace status, recent outages, and incident history: pulled directly from Namespace's official status page at namespace-status.com every 5 minutes. Pingoru tracks 26 Namespace services and has captured 49 incidents in the last 90 days (95.98% uptime). Get email, Slack, Discord, or webhook alerts the moment Namespace reports a new incident, free for 3 monitors, no credit card.

Users who monitor Namespace also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 8,000+ providers
Namespace uptime 95.98% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 14m
    Started Oct 21, 2026, 06:21 PM UTC · Resolved Oct 21, 2026, 06:35 PM UTC
    Remote BuildersDevboxesBazel
    Timeline · 3 updates
    • investigating · Oct 21, 2026, 06:21 PM UTC

      Status: Investigating We see an increased error rate when starting compute for Remote Builder, Bazel Clusters and Devboxes. Affected components Devboxes (Partial outage) Remote Builders (Partial outage) Bazel (Partial outage)

    • investigating · Oct 21, 2026, 06:31 PM UTC

      Status: Investigating We identified a change causing the issue and are rolling it back. Affected components Remote Builders (Partial outage) Bazel (Partial outage) Devboxes (Partial outage)

    • resolved · Oct 21, 2026, 06:35 PM UTC

      Status: Resolved The rollback is complete, and the error rate fully recovered. Affected components Remote Builders (Operational) Bazel (Operational) Devboxes (Operational)

    Latest: Status: Resolved The rollback is complete, and the error rate fully recovered. Affected components Remote Builders (Operational) Bazel (Operational) Devboxes (Operational)

  2. Resolved 6h 25m
    Started Oct 21, 2026, 02:32 PM UTC · Resolved Oct 21, 2026, 08:58 PM UTC
    GitHub Runners
    Timeline · 3 updates
    • investigating · Oct 21, 2026, 02:32 PM UTC

      Status: Investigating Our telemetry has alerted us of extended queue time for GitHub jobs. An initial investigation shows that we are correctly provisioning runners to pick up the jobs but GitHub is not assigning them to us. The team is monitoring the situation. Affected components GitHub Runners (Partial outage)

    • identified · Oct 21, 2026, 02:58 PM UTC

      Status: Identified GitHub is tracking this upstream at https://www.githubstatus.com/incidents/nms1dpzmh9d9. Affected components GitHub Runners (Partial outage)

    • resolved · Oct 21, 2026, 08:58 PM UTC

      Status: Resolved All systems have recovered, and jobs are being picked up normally again. The influx of jobs once GitHub events recovered lead to increased pressure on our systems and fleet, resulting in a longer impact time than expected. Affected components GitHub Runners (Operational)

    Latest: Status: Resolved All systems have recovered, and jobs are being picked up normally again. The influx of jobs once GitHub events recovered lead to increased pressure on our systems …

  3. Resolved 15m
    Started Oct 20, 2026, 10:32 AM UTC · Resolved Oct 20, 2026, 10:47 AM UTC
    MacOS arm64
    Timeline · 3 updates
    • investigating · Oct 20, 2026, 10:32 AM UTC

      Status: Investigating We're investigating increased queue time for macOS jobs and are investigating. Affected components MacOS arm64 (Degraded performance)

    • monitoring · Oct 20, 2026, 10:36 AM UTC

      Status: Monitoring A mitigation was applied and we're seeing recovery. Affected components MacOS arm64 (Operational)

    • resolved · Oct 20, 2026, 10:47 AM UTC

      Status: Resolved We confirm seeing full recovery. Affected components MacOS arm64 (Operational)

    Latest: Status: Resolved We confirm seeing full recovery. Affected components MacOS arm64 (Operational)

  4. Resolved 1h 45m
    Started Oct 19, 2026, 03:44 PM UTC · Resolved Oct 19, 2026, 05:29 PM UTC
    Timeline · 4 updates
    • investigating · Oct 19, 2026, 03:44 PM UTC

      Status: Investigating We're seeing delayed event delivery from GitHub, which is leading to increased queue time for some jobs.

    • identified · Oct 19, 2026, 03:51 PM UTC

      Status: Identified GitHub is tracking this at https://www.githubstatus.com/incidents/8tzbpcnl75jp.

    • monitoring · Oct 19, 2026, 05:02 PM UTC

      Status: Monitoring GitHub reports recovery and after working through a backlog of jobs we're seeing queue time recovering.

    • resolved · Oct 19, 2026, 05:29 PM UTC

      Status: Resolved We confirm seeing full recovery.

    Latest: Status: Resolved We confirm seeing full recovery.

  5. Resolved 4m
    Started Oct 19, 2026, 02:16 PM UTC · Resolved Oct 19, 2026, 02:21 PM UTC
    ArtifactsContainer RegistryWestern Europe
    Timeline · 2 updates
    • identified · Oct 19, 2026, 02:16 PM UTC

      Status: Identified We're investigating degraded performance of registry operations in our Western Europe region. Affected components Western Europe (Degraded performance) Container Registry (Degraded performance)

    • resolved · Oct 19, 2026, 02:21 PM UTC

      Status: Resolved We've applied a mitigation and are seeing full recovery. Affected components Artifacts (Operational) Western Europe (Operational) Container Registry (Operational)

    Latest: Status: Resolved We've applied a mitigation and are seeing full recovery. Affected components Artifacts (Operational) Western Europe (Operational) Container Registry (Operational)

See the full Namespace outage history

44 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Namespace outage history →

Or sign up free to get alerts when Namespace breaks · 10 free monitors · No credit card

Incident record

Since October 2026 · incident.io · 26 components checked every 5 minutes
51incidents recorded
51last 12 months
49last 90 days
108 minutestypical duration, 12 months

The longest incident in the last year, Increased error rate from GitHub on August 6, 2026, ran for 15 hours.

Most affected components, last 12 months

  • GitHub Runners15
  • Devboxes10
  • Northern Virginia, US8
  • Artifacts7
  • Container Registry7

Latest incidents

Outage history

Past 90 days · 49 incidents View full outage history →