← Back to GitHub History
minor✓ Resolved

Incident with Actions

GitHubWed, May 20, 2026, 04:58 PM
Status
resolved
Duration
3h 16m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, May 20, 2026, 08:15 PM
This incident has been resolved.
monitoringWed, May 20, 2026, 07:41 PM
Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.
monitoringWed, May 20, 2026, 06:17 PM
We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
monitoringWed, May 20, 2026, 05:52 PM
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigatingWed, May 20, 2026, 05:46 PM
A subset of runners are taking longer than expected to connect, which may delay some jobs from beginning execution. We are actively working to mitigate the issue.
investigatingWed, May 20, 2026, 04:58 PM
We are investigating reports of degraded performance for Actions

📊 TECHNICAL DETAILS

Internal ID
818cffe7-d5db-402f-8e49-1b520c39596e
External ID
g6ffrm0rfvz9
🕐 Started
Wed, May 20, 2026, 04:58 PM
🔄 Last Updated
Wed, May 20, 2026, 08:15 PM
✓ Resolved
Wed, May 20, 2026, 08:15 PM
MINOR
Impact Level
3h 16m
Total Duration
5
Status Updates
Affected Components
Actions
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed