Namespace Outage History

Namespace is up right now

Pingoru has recorded 59 incidents for Namespace: 59 in the last 12 months and 50 in the last 90 days.

Source: namespace-status.com

59incidents recorded
59last 12 months
50last 90 days
103 minutestypical duration

Incidents, newest first

Minor September 30, 2026 Delayed runner startup 1h 17m Applications (GitHub Runners)

Started Sep 30, 2026, 12:18 PM UTC· resolved Sep 30, 2026, 01:36 PM UTC

  1. investigating Sep 30, 2026, 12:18 PM UTC

    We are investigating an elevated error rate in our control plane, leading to delayed runner provisioning.

  2. identified Sep 30, 2026, 12:37 PM UTC

    We've applied an initial mitigation and are seeing first signs of recovery. We're processing a large the backlog of jobs.

  3. monitoring Sep 30, 2026, 01:05 PM UTC

    We're seeing full recovery, new jobs are being picked up as normal. We're working through the backlog of jobs.

  4. resolved Sep 30, 2026, 01:36 PM UTC

    All jobs are being processed normally.

  5. resolved Sep 30, 2026, 01:36 PM UTC

    All jobs are being processed normally.

Read the full incident report →

Minor September 24, 2026 Small subset of artifact and cache requests in Illinois region failing 1h 29m Applications (Artifacts), Compute Region (Illinois, US), Caches (Bazel), Caches (Turborepo) and 2 more

Started Sep 24, 2026, 05:16 PM UTC· resolved Sep 24, 2026, 06:45 PM UTC

  1. investigating Sep 24, 2026, 05:16 PM UTC

    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.

  2. identified Sep 24, 2026, 05:38 PM UTC

    We identified and stopped a single replica that was causing the stalls.

  3. identified Sep 24, 2026, 06:00 PM UTC

    The new replica showed the same stalling pattern. We identified a networking misconfiguration that's causing the issue.

  4. monitoring Sep 24, 2026, 06:37 PM UTC

    We disabled all affected replicas.

  5. resolved Sep 24, 2026, 06:45 PM UTC

    Error rates have recovered, all systems operational.

  6. resolved Sep 24, 2026, 06:45 PM UTC

    Error rates have recovered, all systems operational.

Read the full incident report →

Minor September 23, 2026 Elevated instance creation time 38m Applications (Devboxes), Compute Region (Western Europe)

Started Sep 23, 2026, 01:16 PM UTC· resolved Sep 23, 2026, 01:54 PM UTC

  1. investigating Sep 23, 2026, 01:16 PM UTC

    We are seeing elevated instance creation time in our European compute shard. Traffic is being steered to other shards.

  2. identified Sep 23, 2026, 01:38 PM UTC

    We are seeing elevated instance creation time in our European compute shard. Traffic is being steered to other shards.

  3. resolved Sep 23, 2026, 01:54 PM UTC

    All systems are operational.

  4. resolved Sep 23, 2026, 01:54 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 23, 2026 Elevated instance creation time 1h 16m Applications (Devboxes), Compute Region (Western Europe)

Started Sep 23, 2026, 08:13 AM UTC· resolved Sep 23, 2026, 09:30 AM UTC

  1. identified Sep 23, 2026, 08:13 AM UTC

    We are seeing elevated instance creation time in our European compute shard. Traffic is being steered to other shards.

  2. monitoring Sep 23, 2026, 08:29 AM UTC

    A fix has been applied, and we are monitoring the situation.

  3. monitoring Sep 23, 2026, 09:09 AM UTC

    We're seeing signs of partial recovery, and Devboxes in Europe are able to start again. The team is still working on fully bringing the compute shard back.

  4. resolved Sep 23, 2026, 09:30 AM UTC

    We've confirmed applied mitigations have lead to full recovery of the affected compute shard.

  5. resolved Sep 23, 2026, 09:30 AM UTC

    We've confirmed applied mitigations have lead to full recovery of the affected compute shard.

Read the full incident report →

Minor September 22, 2026 Elevated instance creation latency 33m Applications (Devboxes), Compute Region (Western Europe)

Started Sep 22, 2026, 02:50 PM UTC· resolved Sep 22, 2026, 03:23 PM UTC

  1. identified Sep 22, 2026, 02:50 PM UTC

    There is elevated latency on instance creation in our European compute shard. Traffic is being steered to other shards. The team is working on a resolution.

  2. resolved Sep 22, 2026, 03:23 PM UTC

    All systems are operational.

  3. resolved Sep 22, 2026, 03:23 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 16, 2026 Subset of container image pulls from external registries failing 1h

Started Sep 16, 2026, 08:15 PM UTC· resolved Sep 16, 2026, 09:15 PM UTC

  1. investigating Sep 16, 2026, 08:15 PM UTC

    We've received reports of a subset of container image pulls failing, the team is investigating.

  2. identified Sep 16, 2026, 08:30 PM UTC

    Pulls from external registries go through a caching layer in our infrastructure, which is serving incorrect data for a small subset of images. A mitigation has been applied to restore correct behavior for failing images.

  3. identified Sep 16, 2026, 08:52 PM UTC

    There is still a small set of images for which an incorrect response is served, we've identified the cause and are rolling out a fix.

  4. resolved Sep 16, 2026, 09:15 PM UTC

    The fix addressed the root cause and all images are being served correctly.

  5. resolved Sep 16, 2026, 09:15 PM UTC

    The fix addressed the root cause and all images are being served correctly.

Read the full incident report →

Minor September 14, 2026 Ongoing maintenance 1h 20m Dashboards (Dashboard), Dashboards (Partner UI)

Started Sep 14, 2026, 11:32 AM UTC· resolved Sep 14, 2026, 12:52 PM UTC

  1. identified Sep 14, 2026, 11:32 AM UTC

    One of our compute shards is undergoing maintenance. That may affect loading the instance list.

  2. resolved Sep 14, 2026, 12:52 PM UTC

    All systems are operational.

  3. resolved Sep 14, 2026, 12:52 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 10, 2026 Increase in queue time of jobs in Virginia (iad-2 and iad-3) 31m Compute Region (Northern Virginia, US)

Started Sep 10, 2026, 11:26 PM UTC· resolved Sep 10, 2026, 11:57 PM UTC

  1. investigating Sep 10, 2026, 11:26 PM UTC

    Our team has been alerted about increased latency in one of our Virginia compute shards, we're investigating.

  2. resolved Sep 10, 2026, 11:57 PM UTC

    All systems are operational.

  3. resolved Sep 10, 2026, 11:57 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 9, 2026 Extended GitHub queue time 34m Applications (GitHub Runners)

Started Sep 09, 2026, 05:27 AM UTC· resolved Sep 09, 2026, 06:02 AM UTC

  1. investigating Sep 09, 2026, 05:27 AM UTC

    Our telemetry notified us of a subset of customers seeing extended queue time on GitHub jobs. The team is investigating.

  2. identified Sep 09, 2026, 05:38 AM UTC

    We have identified a networking issue and are working on a solution. The affected compute shards have been removed from the scheduling rotation temporarily.

  3. identified Sep 09, 2026, 05:54 AM UTC

    We see recovery for most customers. A subset of MacOS GitHub jobs is still being delayed and the team is root causing the problem.

  4. monitoring Sep 09, 2026, 05:59 AM UTC

    We see recovery across all customers. The team is monitoring the situaton.

  5. resolved Sep 09, 2026, 06:02 AM UTC

    All systems are operational.

  6. resolved Sep 09, 2026, 06:02 AM UTC

    All systems are operational.

Read the full incident report →

Minor September 6, 2026 Instance pages failing to load 10m Dashboards (Dashboard)

Started Sep 06, 2026, 07:10 PM UTC· resolved Sep 06, 2026, 07:20 PM UTC

  1. investigating Sep 06, 2026, 07:10 PM UTC

    You may see error related to a missing iad3-a configuration. Our team is addressing this issue.

  2. resolved Sep 06, 2026, 07:20 PM UTC

    All systems are operational.

  3. resolved Sep 06, 2026, 07:20 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 3, 2026 We're investigating reports of GitHub connectivity issues 1h 6m Compute Region (Northern Virginia, US)

Started Sep 03, 2026, 06:15 PM UTC· resolved Sep 03, 2026, 07:22 PM UTC

  1. investigating Sep 03, 2026, 06:15 PM UTC

    We've received reports of connectivity issues to Github properties, our team is investigating.

  2. investigating Sep 03, 2026, 06:24 PM UTC

    Our team can confirm that a small percentage of connections see losses. We're still root causing.

  3. investigating Sep 03, 2026, 06:36 PM UTC

    Our team is still working to mitigate the connectivity losses to github.com properties.

  4. identified Sep 03, 2026, 06:45 PM UTC

    We have identified the issue and applied mitigation. We continue to observe the performance of traffic to GitHub.

  5. monitoring Sep 03, 2026, 07:09 PM UTC

    We are back operational and observing our telemetry for regressions.

  6. resolved Sep 03, 2026, 07:22 PM UTC

    All systems are operational.

  7. resolved Sep 03, 2026, 07:22 PM UTC

    All systems are operational.

Read the full incident report →

Minor September 3, 2026 Network disruption in iad2 2h 13m Compute Region (Northern Virginia, US)

Started Sep 03, 2026, 04:28 AM UTC· resolved Sep 03, 2026, 06:41 AM UTC

  1. investigating Sep 03, 2026, 04:28 AM UTC

    An upstream network provider saw a network disruption which is affecting workloads in one of our compute regions.

  2. resolved Sep 03, 2026, 06:41 AM UTC

    All systems are operational.

  3. resolved Sep 03, 2026, 06:41 AM UTC

    All systems are operational.

Read the full incident report →

Minor September 2, 2026 A subset of control plane calls were failing, including job starts 54m Applications (Artifacts), Applications (Container Registry), Applications (GitHub Runners), Applications (Previews) and 2 more

Started Sep 02, 2026, 02:27 PM UTC· resolved Sep 02, 2026, 03:21 PM UTC

  1. investigating Sep 02, 2026, 02:27 PM UTC

    Investigating degradation on subset of control plane calls.

  2. identified Sep 02, 2026, 03:09 PM UTC

    A backing database issue was identified that led to degraded behavior.

  3. resolved Sep 02, 2026, 03:21 PM UTC

    All systems are operational.

  4. resolved Sep 02, 2026, 03:21 PM UTC

    All systems are operational.

Read the full incident report →

Minor August 26, 2026 Elevated queue time for GitHub action jobs 2h 51m Applications (GitHub Runners)

Started Aug 26, 2026, 03:28 PM UTC· resolved Aug 26, 2026, 06:20 PM UTC

  1. investigating Aug 26, 2026, 03:28 PM UTC

    Our telemetry alerted us about an increase in queue time for GitHub action jobs. The team is investigating.

  2. identified Aug 26, 2026, 03:29 PM UTC

    Namespace is spawning instances successfully but GitHub is having trouble assigning jobs to them. The upstream incident is being tracked at: https://www.githubstatus.com/incidents/y1t7p9fzrlj2

  3. resolved Aug 26, 2026, 06:20 PM UTC

    All systems are operational.

  4. resolved Aug 26, 2026, 06:20 PM UTC

    All systems are operational.

Read the full incident report →

Minor August 26, 2026 Network availability 29m Compute Region (Northern Virginia, US)

Started Aug 26, 2026, 02:19 PM UTC· resolved Aug 26, 2026, 02:49 PM UTC

  1. investigating Aug 26, 2026, 02:19 PM UTC

    We’re seeing reports of network unavailability in one of our sites, our team is investigating.

  2. identified Aug 26, 2026, 02:27 PM UTC

    Our team has identified the source of the issue, and is working through mitigation. The affected region has been cordoned and is not received new jobs.

  3. monitoring Aug 26, 2026, 02:45 PM UTC

    We're seeing recovery across the board.

  4. resolved Aug 26, 2026, 02:49 PM UTC

    All systems are operational.

  5. resolved Aug 26, 2026, 02:49 PM UTC

    All systems are operational.

Read the full incident report →

Minor August 19, 2026 Elevated queue time for a small set of GitHub Action jobs 8h 26m

Started Aug 19, 2026, 03:33 AM UTC· resolved Aug 19, 2026, 12:00 PM UTC

  1. investigating Aug 19, 2026, 03:33 AM UTC

    We are seeing a very small subset of jobs experiencing elevated queue time. Newer runs of the same workflows are picking up runners with no delay. GitHub is not reporting an incident so far.

  2. monitoring Aug 19, 2026, 04:46 AM UTC

    We're seeing a wider, but still low impact due to this issue. GitHub is not reporting any incident.

  3. monitoring Aug 19, 2026, 09:32 AM UTC

    We are still seeing a low rate of jobs not getting assigned to runners timely by GitHub. Runners are starting timely and register successfully with GitHub. If you encounter that your job is not getting picked up, we recommend retrying it on GitHub, as the overall impact rate of this issue is low.

  4. resolved Aug 19, 2026, 12:00 PM UTC

    All systems are operational.

  5. resolved Aug 19, 2026, 12:00 PM UTC

    All systems are operational.

Read the full incident report →

Minor August 17, 2026 Elevated error rate from GitHub API 6h 50m

Started Aug 17, 2026, 01:47 PM UTC· resolved Aug 17, 2026, 08:38 PM UTC

  1. investigating Aug 17, 2026, 01:47 PM UTC

    Upstream incident: https://www.githubstatus.com/incidents/zkxwbgr0cnmx A subset of GitHub Action jobs are seeing elevated queue times as a consequence.

  2. resolved Aug 17, 2026, 05:08 PM UTC

    GitHub has closed their incident and we confirm seeing recovery across the board.

  3. monitoring Aug 17, 2026, 05:50 PM UTC

    A small set of jobs are still seeing elevated queue times due to ongoing impact from https://www.githubstatus.com/incidents/zkxwbgr0cnmx

  4. resolved Aug 17, 2026, 08:38 PM UTC

    All systems are operational.

  5. resolved Aug 17, 2026, 08:38 PM UTC

    All systems are operational.

Read the full incident report →

Minor August 17, 2026 Some IAM calls are failing 21m IAM (SAML SSO), IAM (Social SSO)

Started Aug 17, 2026, 01:17 AM UTC· resolved Aug 17, 2026, 01:38 AM UTC

  1. identified Aug 17, 2026, 01:17 AM UTC

    We've identified the issue and are working through deploying a mitigation.

  2. identified Aug 17, 2026, 01:28 AM UTC

    Our team is still working through applying mitigation.

  3. monitoring Aug 17, 2026, 01:32 AM UTC

    Mitigation has been applied. We continue to monitor.

  4. resolved Aug 17, 2026, 01:38 AM UTC

    All systems are operational.

  5. resolved Aug 17, 2026, 01:38 AM UTC

    All systems are operational.

Read the full incident report →

Minor August 12, 2026 Increased queue time for subset of GitHub jobs 1h 56m Applications (GitHub Runners)

Started Aug 12, 2026, 05:04 PM UTC· resolved Aug 12, 2026, 07:01 PM UTC

  1. identified Aug 12, 2026, 05:04 PM UTC

    There was a brief interruption on event ingestion leading to some jobs seeing increased queue time. We're catching up on any missed jobs and new jobs are being processed as normal.

  2. monitoring Aug 12, 2026, 05:32 PM UTC

    Most of the backlog of jobs has been processed, any new jobs continue being processed as normal. We continue to monitor for complete processing of the backlog.

  3. resolved Aug 12, 2026, 07:01 PM UTC

    We've processed the backlog of jobs. All systems are operational.

  4. resolved Aug 12, 2026, 07:01 PM UTC

    We've processed the backlog of jobs. All systems are operational.

Read the full incident report →

Minor August 12, 2026 Elevated error rate in our control plane 49m Applications (Artifacts), Applications (Container Registry), Applications (GitHub Runners), Applications (Devboxes) and 2 more

Started Aug 12, 2026, 03:25 PM UTC· resolved Aug 12, 2026, 04:15 PM UTC

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

    We're seeing an elevated error rate in our control plane. The team is investigating.

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

    We have identified the issue, and it is focused on IAM, our team is working on mitigation.

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

    Our fix has rolled out and we are seeing signs of recovery. The team continues to monitor the situation.

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

    We've confirmed the fix resolves the root cause and we're seeing full recovery.

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

    We've confirmed the fix resolves the root cause and we're seeing full recovery.

Read the full incident report →

Minor August 10, 2026 Elevated errors during logs serving 3h 50m Dashboards (Dashboard), Infrastructure (Logging)

Started Aug 10, 2026, 08:23 PM UTC· resolved Aug 11, 2026, 12:14 AM UTC

  1. investigating Aug 10, 2026, 08:23 PM UTC

    We are seeing an elevated error rate on our log serving endpoints. The team is investigating.

  2. monitoring Aug 10, 2026, 09:42 PM UTC

    We have applied a mitigation and see first signs of recovery. We are monitoring the situation.

  3. resolved Aug 11, 2026, 12:14 AM UTC

    All systems are operational.

  4. resolved Aug 11, 2026, 12:14 AM UTC

    All systems are operational.

Read the full incident report →

Minor August 7, 2026 Delayed startup for macOS instance 10m Compute Platform (MacOS arm64)

Started Aug 07, 2026, 10:26 AM UTC· resolved Aug 07, 2026, 10:37 AM UTC

  1. investigating Aug 07, 2026, 10:26 AM UTC

    We're seeing increased startup times for a subset of macOS instances, the team is rolling out a fix.

  2. monitoring Aug 07, 2026, 10:32 AM UTC

    The fix has been rolled out and startup times have recovered.

  3. resolved Aug 07, 2026, 10:37 AM UTC

    All systems are operational.

  4. resolved Aug 07, 2026, 10:37 AM UTC

    All systems are operational.

Read the full incident report →

Minor August 7, 2026 Increased error rate in a single compute shard 7m Applications (Artifacts), Applications (Container Registry), Applications (GitHub Runners), Applications (Previews) and 21 more

Started Aug 07, 2026, 06:35 AM UTC· resolved Aug 07, 2026, 06:42 AM UTC

  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.

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

    All systems are operational.

Read the full incident report →

Minor August 6, 2026 Increased error rate from GitHub 14h 46m

Started Aug 06, 2026, 03:34 PM UTC· resolved Aug 07, 2026, 06:20 AM UTC

  1. investigating Aug 06, 2026, 03:34 PM UTC

    Upstream incident: https://www.githubstatus.com/incidents/qcvjkzcs7j74

  2. identified Aug 06, 2026, 03:55 PM UTC

    We're seeing more widespread impact, with runners unable to acquire jobs. This is leading to increased queue times for a subset of jobs. GitHub is tracking this at https://www.githubstatus.com/incidents/qcvjkzcs7j74

  3. monitoring Aug 06, 2026, 10:06 PM UTC

    We are seeing first signs of partial recovery but the incident is still ongoing and many jobs are still seeing elevated queue times. GitHub is tracking their updates in https://www.githubstatus.com/incidents/qcvjkzcs7j74

  4. monitoring Aug 07, 2026, 01:03 AM UTC

    We believe that this incident is largely mitigated. We still see an elevated job assignment latency for a small subset of jobs, but other symptoms have resolved meanwhile. GitHub is reporting their updates in https://www.githubstatus.com/incidents/qcvjkzcs7j74

  5. resolved Aug 07, 2026, 06:20 AM UTC

    All systems are operational.

  6. resolved Aug 07, 2026, 06:20 AM UTC

    All systems are operational.

Read the full incident report →

Minor August 5, 2026 Elevated error rate from Dockerhub 1h 44m

Started Aug 05, 2026, 03:13 PM UTC· resolved Aug 05, 2026, 04:57 PM UTC

  1. investigating Aug 05, 2026, 03:13 PM UTC

    We see a low, but elevated error rate from Dockerhub. The team is investigating.

  2. resolved Aug 05, 2026, 04:57 PM UTC

    All systems are operational.

  3. resolved Aug 05, 2026, 04:57 PM UTC

    All systems are operational.

Read the full incident report →