Disruption with projects service

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10h 21m it lasted.

  Anything that failed between 2026-04-21 15:03 UTC and 2026-04-22 01:24 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 11

1. investigatingApr 21, 2026, 3:03 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. investigatingApr 21, 2026, 3:07 PM UTC

   We are investigating reports of delays with GitHub Projects. Users may notice that changes made to projects are not reflected immediately. Our team has identified the source of the delays and is actively working to resolve the issue.

   provider

3. investigatingApr 21, 2026, 3:42 PM UTC

   We continue to investigate delays with GitHub Projects where changes may not be reflected immediately. Our team has identified the cause and applied mitigations to address the issue. We are seeing initial signs of recovery, though some delays may persist as the system works through a backlog of pending updates.

   provider

4. investigatingApr 21, 2026, 4:18 PM UTC

   We are deploying a fix to relieve the queue of delayed data. Some users may still experience delays with GitHub Projects where changes are not reflected immediately as remaining backlogs are processed.

   provider

5. investigatingApr 21, 2026, 4:45 PM UTC

   The mitigation is deployed and we are seeing recorvery in the queues and will provide an update as to when full recovery will be realized.

   provider

6. investigatingApr 21, 2026, 5:21 PM UTC

   The queues are continuing to decrease and we are working to accelerate the rate of processing through the queues.

   provider

7. investigatingApr 21, 2026, 7:41 PM UTC

   Recovery from the delays affecting GitHub Projects continues to progress. We have deployed additional mitigations that are accelerating processing of the backlog. Users may still experience delays where changes to projects are not reflected immediately. We expect full recovery within approximately six hours.

   provider

8. monitoringApr 21, 2026, 9:15 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

   provider

9. monitoringApr 21, 2026, 10:49 PM UTC

   The issue remains mitigated. Users may still experience delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately three hours.

   provider

10. monitoringApr 22, 2026, 12:00 AM UTC

    The issue remains mitigated. Users may still experience small delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately two hours.

    provider

11. resolvedApr 22, 2026, 1:24 AM UTC

    On April 21, 2026, between 13:35 UTC and 01:24 UTC the following day the projects service was degraded. During this time period, projects may have been out of sync and users may have experienced delays in changes to projects and their items. Delays in reflected changes peaked at approximately 45 minutes. The delays were caused by serialization errors that failed events and triggered a flood of resyncs, overloading our event processing layers. We mitigated the incident by speeding up processing time for incoming changes and otherwise waiting for all changes to be processed. We are working to increase our capacity for processing updates to projects to reduce our time to mitigation of issues like this one in the future.

    provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.