GitHub incident: Incident with Actions and Pull Requests

Affected components

• Actions
• Pull Requests

1. resolvedAug 27, 2026, 00:26 UTC

   On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. <br /><br />We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. <br /><br />We are wo

2. monitoringAug 27, 2026, 00:26 UTC

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

3. investigatingAug 27, 2026, 00:25 UTC

   We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.

4. investigatingAug 27, 2026, 00:01 UTC

   We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.

5. investigatingAug 26, 2026, 22:57 UTC

   We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.

6. investigatingAug 26, 2026, 22:56 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [GLOBAL][Data & Analytics] - Cloud Database Incident NotificationMajor · Aug 25, 2026, 21:25 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• ElevenLabs: Elevated latency on Text-to-Speech and Speech-to-Text RequestsMinor · Aug 26, 2026, 17:16 UTC
• Supabase: pgBouncer issues on some older projectsMinor · Aug 26, 2026, 19:49 UTC

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history