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 July 30, 2026 Registry upload failures in Virginia 25m Applications (Container Registry)

Started Jul 30, 2026, 12:51 AM UTC· resolved Jul 30, 2026, 01:16 AM UTC

  1. investigating Jul 30, 2026, 12:51 AM UTC

    We are seeing upload errors to the registry in one of our cells in Virginia.

  2. identified Jul 30, 2026, 01:09 AM UTC

    We've identified the issue and are mitigating it.

  3. resolved Jul 30, 2026, 01:16 AM UTC

    All systems are operational.

Read the full incident report →

Minor July 29, 2026 Elevated GitHub action error rate 36m

Started Jul 29, 2026, 03:00 PM UTC· resolved Jul 29, 2026, 03:36 PM UTC

  1. monitoring Jul 29, 2026, 03:00 PM UTC

    Upstream incident: https://www.githubstatus.com/incidents/75g5xmzptjqb We are seeing an elevated error rate by GitHub, leading to elevated queue time for a subset of jobs.

  2. resolved Jul 29, 2026, 03:36 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 28, 2026 Partial unavailability of instance metrics 12m Infrastructure (Logging), Infrastructure (Metrics)

Started Jul 28, 2026, 02:28 PM UTC· resolved Jul 28, 2026, 02:41 PM UTC

  1. investigating Jul 28, 2026, 02:28 PM UTC

    Our telemetry has alerted us about a metrics not being available in one of our compute shards. The team is root causing.

  2. investigating Jul 28, 2026, 02:34 PM UTC

    We have rerouted traffic from the faulty compute shard whilst the investigation is ongoing.

  3. identified Jul 28, 2026, 02:35 PM UTC

    We understand the root cause and have applied an immediate fix to our metrics system.

  4. monitoring Jul 28, 2026, 02:37 PM UTC

    We see metrics being successfully processed. Traffic is again being routed to the previously affected compute shard and we are monitoring the situation closely.

  5. resolved Jul 28, 2026, 02:41 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 27, 2026 Elevated GitHub actions queue time 22m Applications (GitHub Runners)

Started Jul 27, 2026, 05:34 PM UTC· resolved Jul 27, 2026, 05:57 PM UTC

  1. investigating Jul 27, 2026, 05:34 PM UTC

    Our telemetry alerted us about elevated GitHub actions queue time. The team is investigating.

  2. identified Jul 27, 2026, 05:41 PM UTC

    We understand the cause and are working towards a fix. A subset of jobs is seeing multiple minutes of queue time.

  3. resolved Jul 27, 2026, 05:57 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 27, 2026 Elevated error rate 52m Applications (Artifacts), Applications (Container Registry), Applications (GitHub Runners), Applications (Devboxes) and 2 more

Started Jul 27, 2026, 04:16 PM UTC· resolved Jul 27, 2026, 05:08 PM UTC

  1. investigating Jul 27, 2026, 04:16 PM UTC

    The team is investigating an elevated error rate affecting many subsystems.

  2. monitoring Jul 27, 2026, 04:54 PM UTC

    The root count was found and a fix has been rolled out. We had two points of control plane unavailability, namely: - 18:16:16 - 18:21:49 UTC - 18:32:40 - 18:40:05 UTC The team is monitoring the situation.

  3. resolved Jul 27, 2026, 05:08 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 25, 2026 Elevated queue time for GitHub action jobs 31m Applications (GitHub Runners)

Started Jul 25, 2026, 12:34 PM UTC· resolved Jul 25, 2026, 01:06 PM UTC

  1. investigating Jul 25, 2026, 12:34 PM UTC

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

  2. identified Jul 25, 2026, 12:36 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/pz7g535gbs6p

  3. monitoring Jul 25, 2026, 01:02 PM UTC

    Jobs have been picked up across most tenants and GitHub has posted an update that the issue has been resolved. The team is monitoring the siutation.

  4. resolved Jul 25, 2026, 01:06 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 25, 2026 Elevated queue time for GitHub Actions 22m Applications (GitHub Runners)

Started Jul 25, 2026, 09:00 AM UTC· resolved Jul 25, 2026, 09:22 AM UTC

  1. identified Jul 25, 2026, 09:00 AM UTC

    Our telemetry alerted us about extended queing time on a small subset of GitHub Action jobs. The root cause is an an upstream incident that GitHub is tracking at: https://www.githubstatus.com/incidents/8vfyvq16hzh9

  2. monitoring Jul 25, 2026, 09:17 AM UTC

    GitHub reports the issue as mitigated. We see improvements in queing time for most customers. The team is monitoring the situation.

  3. resolved Jul 25, 2026, 09:22 AM UTC

    All systems are operational.

Read the full incident report →

Minor July 23, 2026 Elevated queue time for a subset of GitHub jobs 1h 16m

Started Jul 23, 2026, 02:15 PM UTC· resolved Jul 23, 2026, 03:31 PM UTC

  1. monitoring Jul 23, 2026, 02:15 PM UTC

    GitHub is sending a subset of webhook events with a delay, leading to elevated queue time for the affected jobs.

  2. resolved Jul 23, 2026, 03:31 PM UTC

    All systems are operational.

Read the full incident report →

Minor July 23, 2026 Elevated queue time for a subset of GitHub actions jobs 2h 26m

Started Jul 23, 2026, 07:17 AM UTC· resolved Jul 23, 2026, 09:43 AM UTC

  1. monitoring Jul 23, 2026, 07:17 AM UTC

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

  2. monitoring Jul 23, 2026, 09:20 AM UTC

    We're seeing signs of improvements here, but still a notable elevated queue time for a subset of jobs.

  3. resolved Jul 23, 2026, 09:43 AM UTC

    All systems are operational.

Read the full incident report →