GitHub Status
GitHub Octicon logo
Help
Community
Status
GitHub.com
Subscribe to UpdatesSubscribe
x
Get email notifications whenever GitHub creates, updates or resolves an incident.
Email address:
Enter OTP:
Resend OTP in: seconds
Didn't receive the OTP?
Resend OTP
By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Get text message notifications whenever GitHub creates or resolves an incident.
Country code:
Afghanistan (+93)
Albania (+355)
Algeria (+213)
American Samoa (+1)
Andorra (+376)
Angola (+244)
Anguilla (+1)
Antigua and Barbuda (+1)
Argentina (+54)
Armenia (+374)
Aruba (+297)
Australia/Cocos/Christmas Island (+61)
Austria (+43)
Azerbaijan (+994)
Bahamas (+1)
Bahrain (+973)
Bangladesh (+880)
Barbados (+1)
Belarus (+375)
Belgium (+32)
Belize (+501)
Benin (+229)
Bermuda (+1)
Bolivia (+591)
Bosnia and Herzegovina (+387)
Botswana (+267)
Brazil (+55)
Brunei (+673)
Bulgaria (+359)
Burkina Faso (+226)
Burundi (+257)
Cambodia (+855)
Cameroon (+237)
Canada (+1)
Cape Verde (+238)
Cayman Islands (+1)
Central Africa (+236)
Chad (+235)
Chile (+56)
China (+86)
Colombia (+57)
Comoros (+269)
Congo (+242)
Congo, Dem Rep (+243)
Costa Rica (+506)
Croatia (+385)
Cyprus (+357)
Czech Republic (+420)
Denmark (+45)
Djibouti (+253)
Dominica (+1)
Dominican Republic (+1)
Egypt (+20)
El Salvador (+503)
Equatorial Guinea (+240)
Estonia (+372)
Ethiopia (+251)
Faroe Islands (+298)
Fiji (+679)
Finland/Aland Islands (+358)
France (+33)
French Guiana (+594)
French Polynesia (+689)
Gabon (+241)
Gambia (+220)
Georgia (+995)
Germany (+49)
Ghana (+233)
Gibraltar (+350)
Greece (+30)
Greenland (+299)
Grenada (+1)
Guadeloupe (+590)
Guam (+1)
Guatemala (+502)
Guinea (+224)
Guyana (+592)
Haiti (+509)
Honduras (+504)
Hong Kong (+852)
Hungary (+36)
Iceland (+354)
India (+91)
Indonesia (+62)
Iraq (+964)
Ireland (+353)
Israel (+972)
Italy (+39)
Jamaica (+1)
Japan (+81)
Jordan (+962)
Kenya (+254)
Korea, Republic of (+82)
Kosovo (+383)
Kuwait (+965)
Kyrgyzstan (+996)
Laos (+856)
Latvia (+371)
Lebanon (+961)
Lesotho (+266)
Liberia (+231)
Libya (+218)
Liechtenstein (+423)
Lithuania (+370)
Luxembourg (+352)
Macao (+853)
Macedonia (+389)
Madagascar (+261)
Malawi (+265)
Malaysia (+60)
Maldives (+960)
Mali (+223)
Malta (+356)
Martinique (+596)
Mauritania (+222)
Mauritius (+230)
Mexico (+52)
Monaco (+377)
Mongolia (+976)
Montenegro (+382)
Montserrat (+1)
Morocco/Western Sahara (+212)
Mozambique (+258)
Namibia (+264)
Nepal (+977)
Netherlands (+31)
New Zealand (+64)
Nicaragua (+505)
Niger (+227)
Nigeria (+234)
Norway (+47)
Oman (+968)
Pakistan (+92)
Palestinian Territory (+970)
Panama (+507)
Paraguay (+595)
Peru (+51)
Philippines (+63)
Poland (+48)
Portugal (+351)
Puerto Rico (+1)
Qatar (+974)
Reunion/Mayotte (+262)
Romania (+40)
Russia/Kazakhstan (+7)
Rwanda (+250)
Samoa (+685)
San Marino (+378)
Saudi Arabia (+966)
Senegal (+221)
Serbia (+381)
Seychelles (+248)
Sierra Leone (+232)
Singapore (+65)
Slovakia (+421)
Slovenia (+386)
South Africa (+27)
Spain (+34)
Sri Lanka (+94)
St Kitts and Nevis (+1)
St Lucia (+1)
St Vincent Grenadines (+1)
Sudan (+249)
Suriname (+597)
Swaziland (+268)
Sweden (+46)
Switzerland (+41)
Taiwan (+886)
Tajikistan (+992)
Tanzania (+255)
Thailand (+66)
Togo (+228)
Tonga (+676)
Trinidad and Tobago (+1)
Tunisia (+216)
Turkey (+90)
Turks and Caicos Islands (+1)
Uganda (+256)
Ukraine (+380)
United Arab Emirates (+971)
United Kingdom (+44)
United States (+1)
Uruguay (+598)
Uzbekistan (+998)
Venezuela (+58)
Vietnam (+84)
Virgin Islands, British (+1)
Virgin Islands, U.S. (+1)
Yemen (+967)
Zambia (+260)
Zimbabwe (+263)
Phone number:
Change number
Enter OTP:
Resend OTP in: 30 seconds
Didn't receive the OTP?
Resend OTP
Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status.
Webhook URL:
The URL we should send the webhooks to
Email address:
We'll send you email if your endpoint fails
By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Visit our support site.
Get the Atom Feed or RSS Feed.
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.66
% 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.9
% 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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
May 26, 2026
Incident with Actions and Pages
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 26, 13:18 UTC
Update -
The degradation has been mitigated. We are monitoring to ensure stability.
May 26, 13:01 UTC
Monitoring -
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
May 26, 13:00 UTC
Update -
We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation
May 26, 12:37 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
May 26, 12:17 UTC
Update -
We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.
May 26, 11:53 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
May 26, 11:19 UTC
Investigating -
We are investigating reports of degraded performance for Actions and Pages
May 26, 10:57 UTC
May 25, 2026
No incidents reported.
May 24, 2026
No incidents reported.
May 23, 2026
Intermittent errors with app installation token authentication
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 23, 19:32 UTC
Update -
This is fully mitigated, we will continue to monitor to ensure it does not reoccur.
May 23, 19:32 UTC
Update -
We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.
May 23, 19:06 UTC
Update -
We see significant signs of mitigation and are monitoring for full mitigation.
May 23, 18:42 UTC
Update -
We are seeing signs of mitigation and are continuing to monitor for complete mitigation. Next update in one hour.
May 23, 17:41 UTC
Update -
We are continuing to investigate an elevated error rate of authentication failures for app installation tokens. Next update in one hour.
May 23, 16:35 UTC
Update -
We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens. We are continuing to investigate.
May 23, 16:01 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
May 23, 16:00 UTC
May 22, 2026
No incidents reported.
May 21, 2026
No incidents reported.
May 20, 2026
Incident with Actions
Resolved -
On May 20, 2026, between 16:00 UTC and 17:45 UTC, GitHub Actions customers experienced run start delays exceeding 5 minutes. Approximately 4.5% of all runs were delayed during the impact window, with scale set jobs disproportionately affected. 30% of scale set jobs were delayed and 4% failed to start entirely. The incident was caused by a misconfigured health check on an internal service that assigns jobs to runners. A brief latency spike in an upstream dependency triggered health check failures across several pods, removing them from service and concentrating load on the remaining capacity. The added load drove memory pressure that escalated into a cascading failure in one regional cluster, leaving it unable to self-recover. Responders mitigated the incident by scaling capacity in the healthy regional clusters and draining traffic away from the impaired one, after which run start latency recovered. To prevent recurrence, we are strengthening our health check configuration to avoid cascading failure scenarios and evaluating automated mitigations to rebalance traffic when a region is degraded.
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
← Incident History
Powered by Atlassian Statuspage
GitHub text logo
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your
inbox.
Subscribe
Product
Features
Enterprise
Copilot
Security
Pricing
Team
Resources
Roadmap
Compare GitHub
Platform
Developer API
Partners
Education
GitHub CLI
GitHub Desktop
GitHub Mobile
Support
Docs
Community Forum
Professional Services
Skills
Contact GitHub
Company
About
Customer
stories
Blog
The ReadME Project
Careers
Newsroom
Inclusion
Social Impact
Shop
© GitHub, Inc.
Terms
Privacy (Updated 08/2022)
GitHub X
GitHub Facebook
GitHub LinkedIn
GitHub YouTube
Twitch
TikTok
GitHub.com |
The GitHub status page provides a detailed overview of the operational health and incident history of the GitHub platform, focusing on system uptime and past service disruptions. Over the past ninety days, the platform has maintained high uptime across various services, with metrics such as Git Operations, Webhooks, API Requests, Issues, Pull Requests, Actions, Packages, Pages, Copilot, Codespaces, and Copilot AI Model Providers consistently reporting uptime rates near or above ninety-nine percent, demonstrating general stability.
The status reports indicate that systems are generally operational, although the platform acknowledges the possibility of performance degradation, partial outages, and major outages. The service history documents several significant incidents involving critical components, primarily related to GitHub Actions, Pages, and CodeQL, which highlight challenges in maintaining performance and availability.
A major incident on May 26, 2026, involved degraded performance affecting GitHub Actions and Pages, stemming from authentication issues. This period included updates detailing investigations into authentication failures and the subsequent mitigation efforts to stabilize the affected services. Prior to this, on May 20, 2026, an incident related to GitHub Actions occurred where run start delays exceeded five minutes. This failure was traced to a misconfigured health check on an internal service responsible for job assignment, which triggered a cascading failure in one regional cluster due to memory pressure. The mitigation involved scaling capacity in healthy regions and draining traffic to recover execution time.
Further incidents involved CodeQL, the code scanning service. On May 13, 2026, delays in CodeQL processing were caused by replication lag during an internal database migration, which reduced worker capacity. The response involved scaling processing workers by thirty-four percent to mitigate the impact, showing that capacity increases could be applied permanently following such events. A separate incident on May 12, 2026, related to CodeQL, webhooks, notifications, and Slack integration also suffered delays. This was attributed to replication lag from a database migration, which caused insufficient worker capacity for job enqueues. Mitigation for this event involved scaling out processing workers to handle the increased load and implementing plans to use dedicated worker pools for high-usage shared queues to prevent future bottlenecks.
Intermittent authentication errors related to app installation tokens were also reported and resolved on May 23, 2026, through applied mitigations. The incident history demonstrates that the platform actively manages performance and availability through investigation, mitigation deployment, and ongoing monitoring, focusing on fixing issues related to service discovery, queuing services, and worker capacity management to prevent cascading failures during infrastructure events. |