GitHub header

All Systems Operational

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
90 days ago
99.83 % uptime
Today
Webhooks Operational
90 days ago
99.73 % uptime
Today
Visit www.githubstatus.com for more information Operational
API Requests Operational
90 days ago
99.98 % uptime
Today
Issues Operational
90 days ago
99.86 % uptime
Today
Pull Requests Operational
90 days ago
99.55 % uptime
Today
Actions Operational
90 days ago
99.7 % uptime
Today
Packages Operational
90 days ago
99.98 % uptime
Today
Pages Operational
90 days ago
99.96 % uptime
Today
Copilot Operational
90 days ago
99.88 % uptime
Today
Codespaces Operational
90 days ago
99.77 % uptime
Today
Copilot AI Model Providers Operational
90 days ago
100.0 % uptime
Today
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.

May 21, 2026

No incidents reported today.

May 20, 2026
Incident with Actions
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.
May 20, 20:14 UTC
Update - Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.
May 20, 19:41 UTC
Update - 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.
May 20, 18:17 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
May 20, 17:52 UTC
Update - 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.
May 20, 17:46 UTC
Investigating - We are investigating reports of degraded performance for Actions
May 20, 16:58 UTC
May 19, 2026

No incidents reported.

May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026
Actions is experiencing degraded availability
Resolved - On 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.

At 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.

To 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.
May 15, 08:48 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
May 15, 08:41 UTC
Update - We 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.
May 15, 08:29 UTC
Update - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
May 15, 08:27 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
May 15, 08:26 UTC
Update - Pages is experiencing degraded availability. We are continuing to investigate.
May 15, 08:14 UTC
Investigating - We are investigating reports of degraded availability for Actions
May 15, 08:13 UTC
[Retroactive] Incident with GitHub.com
Resolved - Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed.

The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.
May 15, 02:30 UTC
May 14, 2026

No incidents reported.

May 13, 2026
Incident with CodeQL
Resolved - On May 13, 2026, between 14:31 and 16:03 UTC, the Code Scanning service experienced processing delays and 12% of check runs took over 15 minutes to complete. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues.

We mitigated the impact by scaling our processing workers by 34%. Code Scanning results returned to normal processing times after the mitigation was applied.

The capacity increases are permanent, and we are looking into more ways to decrease the load on our workers to help prevent this in the future.
May 13, 16:03 UTC
Update - CodeQL impact has been mitigated. We are continuing to monitor for durable recovery.
May 13, 15:30 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
May 13, 15:26 UTC
Update - We have applied a mitigation to increase processing capacity. We are continuing to monitor to confirm full recovery. We will provide another update by 15:30 UTC.
May 13, 14:58 UTC
Update - We are investigating delays affecting CodeQL, the code analysis engine used by Code Scanning. Some users may experience delayed or incomplete code scanning results. Our engineering team is investigating. We will provide another update by 15:15 UTC.
May 13, 14:43 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 13, 14:41 UTC
May 12, 2026
Incident with CodeQL, Webhooks, Notifications, and Slack Integration
Resolved - On May 12, 2026, between 13:41 and 17:43 UTC, some services experienced delays in processing. For the Code Scanning service, 53% of check runs took over 15 minutes to complete. Additionally, notifications took an average of 22 minutes to be delivered and Slack integration webhooks took an average of 20 minutes to be delivered. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues.

We mitigated the impact by scaling our processing workers to handle the increased load. All services returned to normal processing times after the mitigation was applied.

We are working to create dedicated worker pools for some of our high usage shared queues to help prevent this in the future.
May 12, 17:43 UTC
Update - All services have fully recovered.
May 12, 17:43 UTC
Update - CodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.
May 12, 16:59 UTC
Update - Webhooks have fully recovered. Continuing to work on recovery for the other services.
May 12, 16:29 UTC
Update - Webhooks is operating normally.
May 12, 16:28 UTC
Update - We've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.
May 12, 16:18 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
May 12, 15:44 UTC
Update - We're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.
May 12, 15:42 UTC
Update - CodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.
May 12, 15:13 UTC
Investigating - We are investigating reports of degraded performance for CodeQL
May 12, 14:38 UTC
May 11, 2026
Incident with high errors on Git Operations
Resolved - On May 11th, 2026, between 14:00 UTC and 14:33 UTC, HTTP-based Git read operations were degraded. On average, the error rate was 2.8% and peaked at 7.5% of requests to the service. This was due to resource exhaustion in a networking gateway between GitHub.com’s frontend service for Git operations and a dependency service that performs authentication and authorization. Following the initial spike, the frontend service became stuck in a degraded state in one of our data centers, increasing time to mitigation.

We mitigated the incident by scaling the networking gateway and re-deploying the frontend service.

To reduce our time to detection and mitigation in the future, we are adding auto-scaling to the networking gateway, and resolving a bug which caused the frontend service to remain degraded.
May 11, 14:33 UTC
Investigating - We are investigating reports of degraded performance for Git Operations
May 11, 14:25 UTC
May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026
CCR and CCA failing to start for PR comments
Resolved - On May 7, 2026, between 04:12 UTC and 06:13 UTC, Copilot Cloud Agent and Copilot Code Review Agent sessions for pull requests were delayed or failed to start.

The issue was caused by follow-up recovery work from a separate Pull Requests incident (https://www.githubstatus.com/incidents/f5pb5d5mr9yh). As part of that recovery, we ran a large database migration, which caused replication delays on several replica hosts.

Although those replicas were not serving user traffic, our safeguards correctly treated the elevated replication lag as a signal to slow down writes to the affected database cluster. As a result, some pull request background processing was temporarily delayed. That processing is responsible for sending the internal events that Copilot agents use to begin work, so affected agents did not start until the database replicas caught up.

The system recovered once replication lag returned to normal and pull request processing resumed. We are reviewing how this safeguard interacts with recovery migrations so we can reduce the chance of similar secondary impact during future incident recovery work.
May 7, 06:56 UTC
Update - Copilot code review and cloud agents are starting again for pull requests, we are monitoring for full recovery.
May 7, 06:14 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
May 7, 06:13 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
May 7, 05:02 UTC
← Incident History Powered by Atlassian Statuspage