--- title: GitHub Actions and Pages outage: workflow runs failing... description: GitHub suffered an outage impacting Actions and Pages. Workflow runs were failing to start or dying mid-execution, Actions REST API requests were returning... canonical: https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GitHub Actions and Pages outage: workflow runs failing and API errors | daily.dev og:description: GitHub suffered an outage impacting Actions and Pages. Workflow runs were failing to start or dying mid-execution, Actions REST API requests were returning... og:url: https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl og:image: https://api.daily.dev/og/posts/cjc7ZiYZl.png og:image:alt: GitHub Actions and Pages outage: workflow runs failing and API errors og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # GitHub Actions and Pages outage: workflow runs failing and API errors **[Collections](https://daily.dev/sources/collections)** · 1 min read · 3 upvotes · 1 comments ## Summary GitHub suffered an outage impacting Actions and Pages. Workflow runs were failing to start or dying mid-execution, Actions REST API requests were returning errors, and some users encountered unexpected rate limiting. GitHub Pages experienced intermittent degraded performance during the same window, and GitHub Enterprise Importer migrations were also affected. Engineers identified the root cause and were working on mitigation, with no timeline given for full resolution. ## Content GitHub experienced an outage that took down Actions and Pages for several hours, frustrating developers whose workflows depend on both services. During the incident, workflow runs failed to start or died mid-execution, Actions REST API requests returned errors, and some users hit unexpected rate limiting. GitHub Pages saw intermittent degraded performance alongside the Actions problems. GitHub Enterprise Importer migrations were also affected. Engineers identified the source of the disruption and worked on mitigation, but the fix took long enough that at least one developer noted Actions had been down for five hours before resolution. The aftermath had its own small absurdity: X's algorithm surfaced GitHub's "issue resolved" status post at the top of some users' feeds - except the post was two hours old by then, making it look like a live update when the outage had already been grinding on for a while. ## Questions this post answers ### What was affected during the GitHub Actions outage? The GitHub outage impacted Actions workflow runs (failing to start or dying mid-execution), the Actions REST API (returning errors), GitHub Pages (intermittent degraded performance), and GitHub Enterprise Importer migrations. Some users also hit unexpected rate limiting on top of the other failures. Engineers identified the source and were working on mitigation with no resolution timeline provided. _Teams running CI/CD on GitHub Actions track incidents like this on daily.dev before they derail a release._ ## Community take How the wider developer community reacted, aggregated from 1 discussion and 90 comments across hackernews (as of 2026-08-06). **TL;DR:** The community is overwhelmingly frustrated with GitHub Actions' repeated, multi-hour outages, viewing the frequency and duration as evidence of a systemic reliability problem rather than isolated incidents. Many are actively discussing alternatives or self-hosting. **Sentiment:** 0% positive · 10% mixed · 90% skeptical **The case for** - Self-hosted CI alternatives like Woodpecker CI and GitLab CE are available and relatively easy to set up. - Some commenters note that the scheduling complexity of GHA (evaluating workflow YAML, managing heterogeneous runners) is genuinely non-trivial, offering partial technical sympathy. **The pushback** - GitHub Actions has suffered roughly 8 outage days in the past 4 weeks, with several exceeding 3 hours, putting uptime well below two nines. - Self-hosted runners are also broken during outages because they depend on GitHub's centralized scheduler/API, making the self-hosted option no escape. - There is no paid tier or priority queue to avoid or recover from outages, even for enterprise customers. - Error messages during outages are cryptic and unhelpful (e.g., 'The job was not acquired by Runner of type hosted even after multiple attempts'). - Commenters allege a post-Microsoft-acquisition culture shift toward performative engineering and feature bloat (Copilot integrations, UI gimmicks) at the expense of reliability. - GitHub Pages publishing was also broken because it relies on Actions under the hood, affecting even static-site users. - The status page briefly reported 'Pages is operating normally' only to correct itself 8 minutes later, eroding trust in incident communication. **By community** - hackernews (skeptical): Developers are overwhelmingly critical, citing a pattern of frequent multi-hour outages, poor error messaging, self-hosted runner dependency on the broken scheduler, and a perceived cultural decline under Microsoft ownership — with many actively evaluating alternatives. **Hottest debate:** Whether the scheduling architecture is inherently fragile by design or simply poorly implemented at scale, with some defending the genuine complexity of multi-tenant job scheduling and others insisting the system should be trivially shardable. **Open questions** - What is the actual root cause driving the unusually high frequency of outages over the past month? - Is there any plan to offer a paid SLA or priority queue so enterprise customers have a meaningful reliability option? - Why do self-hosted runners depend on the same centralized scheduler that fails during outages, and will that architecture change? - Has the migration to Azure infrastructure contributed to the degraded reliability? **Highlights** > It's honestly insane how terrible their reliability is. Over the past 4 weeks, 8 days with GitHub Actions outages, many of them multi-hour outages: >3 hours on each of July 9th, July 20th and today, and 1.5 hrs on July 23rd. Outages happen, but this many outages so close together, and so many of them so major/long lasting, something is systematically wrong for sure. It's been seriously hamstringing our ability to ship code at my company. > — [yashap on hackernews · 1 comments](https://news.ycombinator.com/item?id=49200490) > My experience working at LinkedIn was that, after Microsoft took over, they offshored a huge part of their infrastructure and turned the entire culture into one of performative based engineering instead of results based engineering. If you implemented a tool and it worked one time for your presentation to management that's all that mattered. The actual company employees using it downstream in prod basically had to constantly QA the alpha software they were forced to use and the authors of the tool were hard to track down if they even still worked there. And if you did find the author or the team they would be very resistant to admitting there was an issue because it LOOKED bad. So many tools I used were fragile and buggy, it was clear the authors just presented the happy path to management to get the note added to their promotion packet and the rest of the company just had to deal with the fallout. My team implemented this product that the entire company used that was broken and buggy as hell but they kept presenting the product to management as this amazing product and nothing was ever done about how broken it was. If Github is having the same issues I feel for them. > — [the\_real\_cher on hackernews](https://news.ycombinator.com/item?id=49201173) > I love how even self hosted workers don't work during these outages - running jobs on their infrastructure being flakey is marginally acceptable, but the API to simply schedule workflows having this availability is mind boggling. Github just doesn't seem like a serious company anymore. > — [arandomhuman on hackernews · 5 comments](https://news.ycombinator.com/item?id=49199319) > The one thing that falls over is that the webhooks are actually self modifying code since you have an 'on commit' webhook that bootstraps the actions logic from the workflow.yaml file(s) (which are not really config files, they have logic that needs to be evaluated). I don't disagree that it's obvious they've got problems but I'm just saying it's obvious to me the part that falls over (the scheduling of jobs) and why that would impact self hosted runners, which do no scheduling but depend on it to function. As for 'just a message queue with some database updates and sharding that's easy to reason about'... Here's a job scheduling problem as an example: imagine you schedule a job, and there's no runner available. How do you disambiguate between no runners available because you've reached capacity, runners not being available because they're on a real network with faulty connections, and runners not being available because of a faulty rollout of internal updates? A simple message queue for job scheduling is fine if you own everything and can deal with the operational overhead of identifying those cases by hand, but Github can't do that. > — [duped on hackernews · 1 comments](https://news.ycombinator.com/item?id=49200471) > Someone needs to work on improving the way Actions deals with resource exhaustion like this. Today it exploded all the CI jobs with "failed" and an inscrutable message about "The job was not acquired by Runner of type hosted even after multiple attempts" then "Internal server error". It should say "Timed out due to no runner available, our apologies, try again later, or pay $$$ here to get priority for runners". > — [dboreham on hackernews · 1 comments](https://news.ycombinator.com/item?id=49199303) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49198302) · 110 points · 90 comments ## Community discussion Top comments from developers on daily.dev. **@dcorto** · 0 upvotes > GitHub issues the new era xd ## Similar posts on daily.dev - [GitHub Status](https://daily.dev/posts/github-status-rbmhgeg1f) · Hacker News · 6 upvotes · 1 comments --- Tags: [#github](https://daily.dev/tags/github), [#cicd](https://daily.dev/tags/cicd), [#github-actions](https://daily.dev/tags/github-actions), [#github-pages](https://daily.dev/tags/github-pages) [View this post on daily.dev](https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"GitHub Actions and Pages outage: workflow runs failing and API errors","url":"https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl"},"datePublished":"2026-08-06T18:36:25.509Z","dateModified":"2026-08-06T21:40:46.048Z","description":"GitHub suffered an outage impacting Actions and Pages. Workflow runs were failing to start or dying mid-execution, Actions REST API requests were returning...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7978ccfd87a8cbcfb2b7bedc621e2ea6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7978ccfd87a8cbcfb2b7bedc621e2ea6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"github,cicd,github-actions,github-pages","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"GitHub Actions and Pages outage: workflow runs failing and API errors"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl","comment":[{"@type":"Comment","text":"GitHub issues the new era xd","datePublished":"2026-08-07T10:18:26.653Z","url":"https://daily.dev/posts/cjc7ZiYZl#c-l2ZFUkGKB","author":{"@type":"Person","name":"David C.","url":"https://daily.dev/dcorto","image":"https://media.daily.dev/image/upload/s--EPnTZZFw--/f_auto/v1784418453/avatars/avatar_tT4BuvxaHeTxyE5fH41si?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/github-actions-and-pages-outage-workflow-runs-failing-and-api-errors-cjc7ziyzl#faq","mainEntity":[{"@type":"Question","name":"What was affected during the GitHub Actions outage?","acceptedAnswer":{"@type":"Answer","text":"The GitHub outage impacted Actions workflow runs (failing to start or dying mid-execution), the Actions REST API (returning errors), GitHub Pages (intermittent degraded performance), and GitHub Enterprise Importer migrations. Some users also hit unexpected rate limiting on top of the other failures. Engineers identified the source and were working on mitigation with no resolution timeline provided. Teams running CI/CD on GitHub Actions track incidents like this on daily.dev before they derail a release."}}]} ```