GitHub header

All Systems Operational

About This Site

For the status of GitHub.com, please visit: githubstatus.com

Git Operations ? Operational
Webhooks ? Operational
API Requests ? Operational
Issues ? Operational
Pull Requests Operational
Actions ? Operational
Packages ? Operational
Pages ? Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Sep 28, 2025

No incidents reported today.

Sep 27, 2025

No incidents reported.

Sep 26, 2025

No incidents reported.

Sep 25, 2025

No incidents reported.

Sep 24, 2025
Resolved - On September 24, between 15:00 and 17:25 UTC, customers using the Australia stamp of GitHub Enterprise Cloud experienced failures and delays when running workflows on GitHub Actions. During this period, processing of Actions webhook events and scheduled invocations was paused. After the incident was resolved, delayed webhooks were delivered, and approximately 98% of Actions events were eventually processed.

The incident was caused by an existing misconfiguration in our stream processing system preventing automated recovery when multiple brokers went unavailable. When these failures occurred simultaneously, the misconfigured threshold prevented jobs from being enqueued.

We have corrected this configuration across all environments, and implemented tests which ensure future configuration conformance and prevent similar issues.

Sep 24, 17:34 UTC
Update - We have identified the issue with some hosts in our infrastructure and are working on mitigating the issue.

Sep 24, 17:13 UTC
Update - We are investigating reports of degraded performance in regards to starting Actions workflows.
Sep 24, 16:38 UTC
Investigating - We are investigating reports of degraded performance for Actions
Sep 24, 16:35 UTC
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.
Sep 24, 09:18 UTC
Update - Between around 8:16 UTC and 8:51 UTC we saw elevated errors on Claude Opus 4 and Opus 4.1, up to 49% of requests were failing. This has recovered to around 4% of requests failing, we are monitoring recovery.
Sep 24, 09:16 UTC
Investigating - We are currently investigating this issue.
Sep 24, 09:08 UTC
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.
Sep 24, 00:26 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 and Claude Sonnet 4 are once again available in Copilot Chat, VS Code and other Copilot products.

We will continue monitoring to ensure stability, but mitigation is complete.

Sep 24, 00:26 UTC
Update - We are experiencing degraded availability for the Claude Sonnet 3.7 and Claude Sonnet 4 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

Other models are available and working as expected.

Sep 23, 22:22 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Sep 23, 22:22 UTC
Sep 23, 2025
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.
Sep 23, 01:46 UTC
Update - Code search has recovered.
Sep 23, 01:46 UTC
Update - Customers in the GitHub Enterprise Cloud - AU environment may currently be experiencing issues with code search. We have identified the issue and are working on a mitigation.
Sep 23, 00:00 UTC
Investigating - We are currently investigating this issue.
Sep 22, 23:57 UTC
Sep 22, 2025
Sep 21, 2025

No incidents reported.

Sep 20, 2025

No incidents reported.

Sep 19, 2025

No incidents reported.

Sep 18, 2025

No incidents reported.

Sep 17, 2025

No incidents reported.

Sep 16, 2025

No incidents reported.

Sep 15, 2025
Resolved - On September 15th between 17:55 and 18:20 UTC, Copilot experienced degraded availability for all features. This was due a partial deployment of a feature flag to a global rate limiter. The flag triggered behavior that unintentionally rate limited all requests, resulting in 100% of them returning 403 errors. The issue was resolved by reverting the feature flag which resulted in immediate recovery.

The root cause of the incident was from an undetected edge case in our rate limiting logic. The flag was meant to scale down rate limiting for a subset of users, but unintentionally put our rate limiting configuration into an invalid state.

To prevent this from happening again, we have addressed the bug with our rate limiting. We are also adding additional monitors to detect anomalies in our traffic patterns, which will allow us to identify similar issues during future deployments. Furthermore, we are exploring ways to test our rate limit scaling in our internal environment to enhance our pre-production validation process.

Sep 15, 18:28 UTC
Investigating - We are currently investigating this issue.
Sep 15, 18:21 UTC
Sep 14, 2025

No incidents reported.