Delays for Pull Requests and Webhook deliveries
Update - Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.
Oct 21, 2026 - 16:25 UTC
Update - Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
Oct 21, 2026 - 16:17 UTC
Update - We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
Oct 21, 2026 - 15:58 UTC
Update - We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.
Oct 21, 2026 - 15:36 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 21, 2026 - 15:15 UTC
Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
Oct 21, 2026 - 14:52 UTC

About This Site

Check GitHub Enterprise Cloud status by region:
- Australia: au.githubstatus.com
- EU: eu.githubstatus.com
- Japan: jp.githubstatus.com
- US: us.githubstatus.com

Uptime over the past 90 days. View historical uptime.
Git Operations Operational
Webhooks Degraded Performance
Visit www.githubstatus.com for more information Operational
API Requests Operational
Issues Operational
Pull Requests Degraded Performance
Actions Degraded Performance
Packages Operational
Pages Operational
Copilot Operational
Codespaces Operational
Copilot AI Model Providers Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 21, 2026

Unresolved incident: Delays for Pull Requests and Webhook deliveries.

Oct 20, 2026

No incidents reported.

Oct 19, 2026

Degraded availability for GitHub Actions, GitHub Pages and Webhooks
Resolved - 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.
Oct 19, 16:56 UTC
Monitoring - Actions, Pages and Webhooks are operating normally.
Oct 19, 16:56 UTC
Update - We’re seeing recovery following mitigation and are continuing to monitor.

Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.
Oct 19, 16:30 UTC
Update - We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks.

Customers may experience delays in workflow processing, site builds and webhook delivery.
Oct 19, 15:56 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Oct 19, 15:50 UTC
Investigating - We are investigating reports of degraded performance for Actions and Pages
Oct 19, 15:49 UTC

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

CCA Automations are delayed when starting an Automation
Resolved - 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.
Oct 15, 18:56 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 15, 18:53 UTC
Update - CCA Automations are experiencing delays when users start an Automation
Oct 15, 18:34 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 15, 18:31 UTC

Oct 14, 2026

No incidents reported.

Oct 13, 2026

[Retroactive] Actions workflow run logs delayed
Resolved - 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 ran normally and no run delays or check delays occurred.
Oct 13, 20:30 UTC

Oct 12, 2026

Incident with Actions, Pull Requests and Issues
Resolved - 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.

The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC.

The incident was triggered through a latent condition in our notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions.

We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.
Oct 12, 20:16 UTC
Update - Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
Oct 12, 19:28 UTC
Update - Web and email notifications continue to be delayed as we work through a backlog of notifications.
Oct 12, 17:34 UTC
Update - Notifications have resumed but will continue to be delayed as we work through a backlog.
Oct 12, 15:50 UTC
Update - We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
Oct 12, 15:19 UTC
Update - We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
Oct 12, 14:37 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Oct 12, 14:36 UTC
Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Oct 12, 14:35 UTC
Update - Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
Oct 12, 13:38 UTC
Update - Pull Requests is operating normally.
Oct 12, 13:02 UTC
Update - We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
Oct 12, 12:57 UTC
Update - Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
Oct 12, 12:33 UTC
Investigating - We are investigating reports of degraded performance for Actions, Issues and Pull Requests
Oct 12, 12:21 UTC

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

Incident with Git Operations, Issues, Actions and Pull Requests
Resolved - 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: https://www.githubstatus.com/incidents/djlmxz2zd0j7
Oct 7, 18:04 UTC
Update - All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
Oct 7, 18:00 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 7, 17:27 UTC
Update - We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
Oct 7, 17:25 UTC
Investigating - We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Oct 7, 17:17 UTC
Incident with Git Operations, Pull Requests and Actions
Resolved - 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 failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected.

In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded.

GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers.

Each outage ended when one of our established machines with correct configuration became the leader of the quorum and sent the correct configuration. After the first outage, we identified the new machine as the source and paused automated maintenance to stop it from being leader again. At 16:52 UTC, an automated maintenance task that did not honor the pause put it back in charge, and the outage happened again. We shut that machine down at 17:02 UTC and have since removed it, and the automation now honors the pause, which was a new regression due to an update of our puppet infrastructure.

To prevent recurrence, we are clearing retired database servers from the service's records before any new machine is added, and we are keeping new machines from being elected leader until their records have been checked. We are also changing our systems to reject configuration that point to servers that don't exist and to keep using the last known-good settings instead. Finally, we are giving responders a faster way to take a misbehaving machine out of service, and adding alerts so changes like this are spotted within seconds.

We will share a more detailed write-up of these incidents in our monthly availability report, along with the status of the repairs we are making to prevent issues like these in the future.
Oct 7, 16:25 UTC
Update - Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
Oct 7, 16:23 UTC
Update - We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
Oct 7, 15:58 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 7, 15:56 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 7, 15:49 UTC
Update - The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
Oct 7, 15:49 UTC
Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Oct 7, 15:47 UTC
Update - We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
Oct 7, 15:41 UTC
Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:35 UTC
Update - Actions is operating normally.
Oct 7, 15:32 UTC
Update - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Oct 7, 15:31 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:27 UTC
Update - Git Operations is operating normally.
Oct 7, 15:27 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:25 UTC
Update - We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
Oct 7, 15:24 UTC
Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:21 UTC
Update - Webhooks is experiencing degraded availability. We are continuing to investigate.
Oct 7, 15:16 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:15 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Oct 7, 15:14 UTC
Investigating - We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
Oct 7, 15:14 UTC
Incident History Powered by Atlassian Statuspage