Disruption with GitHub notifications

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 15m it lasted.

  Anything that failed between 2026-04-09 04:42 UTC and 2026-04-09 04:57 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 3

1. investigatingApr 9, 2026, 4:42 AM UTC

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

   provider

2. monitoringApr 9, 2026, 4:57 AM UTC

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

   provider

3. resolvedApr 9, 2026, 4:57 AM UTC

   On April 9, 2026, between 03:22 UTC and 04:49 UTC, GitHub Notifications experienced degraded availability. During this time, approximately 45% of requests to the notifications service returned errors, with a peak error rate of approximately 54%, preventing affected users from successfully viewing or interacting with their notifications service. The issue was identified and resolved, restoring the service to full availability. We are working to improve our metrics to reduce time to detection and mitigation for similar issues 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.