{"slug": "github-actions-was-down", "title": "GitHub Actions was down", "summary": "On May 15, 2026, from 07:43 to 08:48 UTC, GitHub Actions suffered a degradation that caused workflow runs to fail or start late for some customers, triggered by a planned failover where an automated service discovery update did not propagate correctly. At peak impact, 42% of Actions runs failed, also affecting downstream services like GitHub Pages and Copilot cloud services. Responders manually corrected the routing issue at 08:12 UTC, and the incident was resolved by 08:48 UTC.", "body_md": "**Resolved** -\nOn May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration.\n\nAt peak impact, 42% of Actions runs failed. Downstream services that depend on Actions workflow execution were also impacted, including GitHub Pages and Copilot cloud services. At 08:12 UTC, responders manually corrected the service discovery routing issue. Timeout and failure rates recovered shortly after, and we continued monitoring until full stabilization was confirmed across all affected services. The incident was marked resolved at 08:48 UTC.\n\nTo prevent recurrence, we are implementing failover guardrails that validate service discovery state before completing failover operations, strengthening pre-flight and post-flight verification checks, and improving dependency resilience to reduce timeout cascades during infrastructure events.\n\nMay `15`, `08:48` UTC\n\n**Monitoring** -\nThe degradation has been mitigated. We are monitoring to ensure stability.\n\nMay `15`, `08:41` UTC\n\n**Update** -\nWe are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.\n\nMay `15`, `08:29` UTC\n\n**Update** -\nThe degradation affecting Pages has been mitigated. We are monitoring to ensure stability.\n\nMay `15`, `08:27` UTC\n\n**Update** -\nThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n\nMay `15`, `08:26` UTC\n\n**Update** -\nPages is experiencing degraded availability. We are continuing to investigate.\n\nMay `15`, `08:14` UTC\n\n**Investigating** -\nWe are investigating reports of degraded availability for Actions\n\nMay `15`, `08:13` UTC", "url": "https://wpnews.pro/news/github-actions-was-down", "canonical_source": "https://www.githubstatus.com/?today", "published_at": "2026-05-26 11:42:58+00:00", "updated_at": "2026-05-27 00:34:17.567468+00:00", "lang": "en", "topics": ["ai-infrastructure"], "entities": ["GitHub Actions", "GitHub Pages", "Copilot"], "alternates": {"html": "https://wpnews.pro/news/github-actions-was-down", "markdown": "https://wpnews.pro/news/github-actions-was-down.md", "text": "https://wpnews.pro/news/github-actions-was-down.txt", "jsonld": "https://wpnews.pro/news/github-actions-was-down.jsonld"}}