Degraded performance for various services

What to do

• Check whether you use GitHub Actions Issues, Actions, Packages. 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 1h 3m it lasted.

  Anything that failed between 2026-03-13 15:12 UTC and 2026-03-13 16:15 UTC may need a replay.

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

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

Updates from GitHub Actions 6

1. investigatingMar 13, 2026, 3:12 PM UTC

   We are investigating reports of degraded performance for Actions and Issues

   provider

2. investigatingMar 13, 2026, 3:14 PM UTC

   We are investigating reports of issues with service(s): Actions, Feeds, Issues, Profiles, Registry Metadata, Star, User Dashboard. We will continue to keep users updated on progress towards mitigation.

   provider

3. investigatingMar 13, 2026, 3:20 PM UTC

   Packages is experiencing degraded performance. We are continuing to investigate.

   provider

4. investigatingMar 13, 2026, 3:47 PM UTC

   We are investigating intermittent performance degradation affecting Actions, Feeds, Issues, Package Registry, Profiles, Registry Metadata, Star, and User Dashboard. Users may experience elevated error rates and slower response times when accessing these services. We have identified a potential cause and are implementing mitigations to restore normal service. We'll post another update by 16:15 UTC.

   provider

5. investigatingMar 13, 2026, 4:02 PM UTC

   We have deployed mitigations and are actively monitoring for recovery. We'll post another update by 17:00 UTC.

   provider

6. resolvedMar 13, 2026, 4:15 PM UTC

   On March 13, 2026, between 13:35 UTC and 16:02 UTC, a configuration change to an internal authorization service reduced its processing capacity below what was needed during peak traffic. This caused intermittent timeouts when other GitHub services checked user permissions, resulting in four to five waves of errors over roughly two hours and forty minutes. In total, 0.4% of users were denied access to actions they were authorized to perform. The root cause was a resource right-sizing change deployed to the authorization service the previous day. It reduced CPU allocation below what was required at peak, causing the service's network gateway to throttle under load. Because the change was deployed after peak traffic on March 12, the reduced capacity wasn't surfaced until the next day's peak. The incident was mitigated by manually scaling up the authorization service and reverting the configuration change. To prevent recurrence, we are adding further resource utilization monitors across our entire stack to detect throttling and improving error handling so transient infrastructure timeouts are distinguished from authorization failures, enabling quicker detection of the root issue.

   provider

Corrections

None so far.

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