Namespace incident

Elevated queue time on GitHub jobs

Resolved after 6 hours 25 minutes, affecting Applications (GitHub Runners), on October 21, 2026.

resolved Oct 21, 2026, 08:58 PM UTC

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.

Started
Oct 21, 2026, 02:32 PM UTC
Resolved
Oct 21, 2026, 08:58 PM UTC
Duration
6h 25m
Detected by Pingoru
Oct 21, 2026, 02:32 PM UTC

Affected components

Applications (GitHub Runners)

Update timeline

  1. investigating Oct 21, 2026, 02:32 PM UTC

    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.

  2. identified Oct 21, 2026, 02:58 PM UTC

    GitHub is tracking this upstream at https://www.githubstatus.com/incidents/nms1dpzmh9d9.

  3. resolved Oct 21, 2026, 08:58 PM UTC

    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.

  4. resolved Oct 21, 2026, 08:58 PM UTC

    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.

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 →