GitHub status

Components

What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.

Recent GitHub incidents

• Grok 4.6 and Grok 4.7 Service Issues · Oct 23, 2026, 23:41 UTC · resolved, minor impact, lasted 42 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Disruption with Dependabot Alerts · Oct 23, 2026, 14:58 UTC · resolved, minor impact, lasted 3 h 53 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Delayed Actions status check results · Oct 23, 2026, 07:29 UTC · resolved, minor impact, lasted 36 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Project updates delayed · Oct 22, 2026, 15:28 UTC · resolved, minor impact, lasted 11 h 2 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Incident with Actions Results · Oct 22, 2026, 14:18 UTC · resolved, minor impact, lasted 1 h 1 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Delays for Pull Requests and Webhook deliveries · Oct 21, 2026, 14:52 UTC · resolved, critical impact, lasted 4 h 30 min

  This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

• Degraded availability for GitHub Actions, GitHub Pages and Webhooks · Oct 19, 2026, 15:49 UTC · resolved, critical impact, lasted 1 h 8 min

  On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. <br /><br />Impact <br /><br /> - Workflow…

• CCA Automations are delayed when starting an Automation · Oct 15, 2026, 18:31 UTC · resolved, minor impact, lasted 24 min

  We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.<br />

• [Retroactive] Actions workflow run logs delayed · Oct 13, 2026, 20:30 UTC · resolved, minor impact, lasted 0 min

  On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and…

• Incident with Actions, Pull Requests and Issues · Oct 12, 2026, 12:21 UTC · resolved, minor impact, lasted 7 h 54 min

  On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br…

• Incident with Git Operations, Issues, Actions and Pull Requests · Oct 7, 2026, 17:17 UTC · resolved, critical impact, lasted 48 min

  On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures:…

• Incident with Git Operations, Pull Requests and Actions · Oct 7, 2026, 15:14 UTC · resolved, critical impact, lasted 1 h 10 min

  On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data…

• Several services are degraded · Oct 6, 2026, 19:57 UTC · resolved, critical impact, lasted 3 h 43 min

  On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos,…

• Disruption with some GitHub services · Oct 5, 2026, 23:47 UTC · resolved, major impact, lasted 1 h 45 min

  On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests…

• Incident with Actions · Oct 5, 2026, 19:11 UTC · resolved, critical impact, lasted 3 h 38 min

  On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br…

Source: GitHub, GitHub’s public status page, read Oct 24, 2026, 18:02 UTC. Uptimely is not affiliated with GitHub; incident text is GitHub’s own.

Status of similar services

• Bitbucket status
• npm status
• Docker status
• Twilio status
• Datadog status
• Sentry status
• Supabase status
• PlanetScale status
• MongoDB Atlas status
• Elastic Cloud status
• Snowflake status
• Grafana Cloud status
• CircleCI status
• Mailgun status
• Resend status
• Clerk status
• Segment status
• Cloudinary status

Every service status we track