Is Github Down?
Is Github not working for everyone right now? Get current Github outages, status, timeouts and issue reports today.
Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.
https://github.com/
0 recorded outage reports in the displayed 24-hour window.
Mapped components are operational in the latest official feed; individual experiences can vary.
Estimated down reports for Github — last 24 hours
Not enough Google Trends data is available for this service yet.
No user-submitted outage reports in the last 24 hours.
Github website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-10-19 05:41:04 UTC.
Checked address: https://github.com/
DNS lookup: 41 ms · TCP connection: 2 ms · TLS handshake: 6 ms. Certificate expires 2026-11-29; trusted connection: yes.
100%
Successful website checks (24h)
3 successful / 3 measurable checks
52 ms
Median response time
76 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Gaps are unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and Google activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest official feed; individual experiences can vary.
- Official provider feed: recently checked; checked 2026-10-19 05:42:30 UTC.
- Direct website measurements: 3 checks in the last 24 hours.
- Google Trends estimate: 0 samples; last checked Unknown.
- Autocomplete: 0 recent query observations. Suggestions are not individual down reports.
Sources measure different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
GitHub official status · fetched 2026-10-19 05:42:30 UTC
12 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Git Operations | operational |
| Webhooks | operational |
| Visit www.githubstatus.com for more information | operational |
| API Requests | operational |
| Issues | operational |
| Pull Requests | operational |
| Actions | operational |
| Packages | operational |
| Pages | operational |
| Copilot | operational |
| Codespaces | operational |
| Copilot AI Model Providers | operational |
Official incident timeline
CCA Automations are delayed when starting an Automation · resolved · 2026-10-15T19:00:06.028Z
Product match: unmapped.
Read the provider’s incident report
- · 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.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
CCA Automations are experiencing delays when users start an Automation
- · investigating
We are investigating reports of impacted performance for some GitHub services.
[Retroactive] Actions workflow run logs delayed · resolved · 2026-10-14T00:13:11.803Z
Product match: unmapped.
Read the provider’s incident report
- · 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.
Incident with Actions, Pull Requests and Issues · resolved · 2026-10-15T17:28:05.702Z
Product match: components.
Read the provider’s incident report
- · 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 U
- · investigating
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
- · investigating
Web and email notifications continue to be delayed as we work through a backlog of notifications.
- · investigating
Notifications have resumed but will continue to be delayed as we work through a backlog.
- · investigating
We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
- · investigating
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
- · investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- · investigating
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.
- · investigating
Pull Requests is operating normally.
- · investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
- · investigating
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.
Incident with Git Operations, Issues, Actions and Pull Requests · resolved · 2026-10-12T19:19:29.599Z
Product match: components.
Read the provider’s incident report
- · 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
- · monitoring
All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
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.
- · investigating
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Incident with Git Operations, Pull Requests and Actions · resolved · 2026-10-12T19:23:37.760Z
Product match: components.
Read the provider’s incident report
- · 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
- · monitoring
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.
- · monitoring
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.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- · investigating
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
- · investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
- · investigating
Actions is operating normally.
- · investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- · investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
Several services are degraded · resolved · 2026-10-12T18:18:45.812Z
Product match: components.
Read the provider’s incident report
- · resolved
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, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximatel
- · investigating
We are deploying a mitigation and plan to resume migrations shortly thereafter
- · investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
- · investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
- · investigating
Pull Requests is operating normally.
- · investigating
Webhooks is operating normally.
- · investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
Disruption with some GitHub services · resolved · 2026-10-09T15:47:28.139Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
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 to the service that powers these pages.This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mit
- · investigating
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
- · investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Actions · resolved · 2026-10-06T22:48:02.341Z
Product match: components.
Read the provider’s incident report
- · resolved
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. During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve nor
- · investigating
Pages is operating normally.
- · investigating
Actions is operating normally.
- · investigating
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
- · investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- · investigating
Pages is experiencing degraded performance. We are continuing to investigate.
- · investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
- · investigating
Actions is experiencing degraded availability. We are continuing to investigate.
- · investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
- · investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
- · investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
- · investigating
We are investigating reports of degraded performance for Actions
Recovery tracker
No recent recovery can be established from available evidence.
1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 76 ms · Earlier median: 52 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent problem-related autocomplete suggestions have been collected for this service.
US English Google autocomplete suggestions help discover problem patterns. They can persist after an incident and do not measure report counts or prove an outage. New phrases require corroboration before accelerating Trends collection.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Powered by Globalping. Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Github.
More about Github service
Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.