Skip to main content
GitHub Actions

Elevated delays in Actions workflow runs and Pull Request status updates

Degraded Lasted 23m · started · GitHub Actions's page

Level
confirmed
Worst impact
Degraded
Components
Pull Requests, Actions
Down Index
35of 100

What to do

  • Check whether you use GitHub Actions Pull Requests, Actions. 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 23m it lasted.

    Anything that failed between 2026-03-30 13:02 UTC and 2026-03-30 13:25 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 4

  1. investigating

    We are investigating reports of degraded performance for Actions and Pull Requests

    provider

  2. monitoring

    The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.

    provider

  3. monitoring

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

    provider

  4. resolved

    On March 30, 2026, between 10:11 UTC and 13:25 UTC, GitHub Actions experienced degraded performance. During this time, approximately 2.65% of workflow jobs triggered by pull request events experienced start delays exceeding 5 minutes. The issue was caused by replication lag on an internal database cluster used by Actions, which triggered write throttling in our database protection layer and slowed job queue processing. The replication lag originated from planned maintenance to scale the internal database. Newly added database hosts triggered guardrails in the throttling layer, restricting write throughput. The incident was mitigated by excluding the new hosts from replication delay calculations. To prevent recurrence, we have updated our maintenance procedures to ensure new hosts are excluded from throttling assessments during scaling operations. Additionally, we are investing in automation to streamline this type of maintenance activity.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-10eeed3f7b

Is GitHub Actions still down?

No, this incident was resolved 2026-03-30 13:25 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.

How long did it last?

23m, from 2026-03-30 13:02 UTC to 2026-03-30 13:25 UTC, by the times GitHub Actions posted.

What was affected?

GitHub Actions named Pull Requests, Actions.

What caused it?

GitHub Actions hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.