down
Is Github down?
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/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Github
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-08 18:18:28 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Github outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Github website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-08 17:58:18 UTC.
Checked address: https://github.com/
DNS lookup: 2 ms · TCP connection: 2 ms · TLS handshake: 4 ms. Certificate expires 2027-01-27; trusted connection: yes.
100%
Successful website checks (24h)
22 successful / 22 measurable checks
15 ms
Median response time
47 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is 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 estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
GitHub official status · fetched 2026-11-08 18:18:28 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
Increase in timeouts for some unauthenticated users · resolved · 2026-11-08T12:32:35.646Z
Product match: components.
Read the provider’s incident report
- · 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.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
- · investigating
We've identified a problematic component and are working to redeploy it.
- · investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
- · investigating
We are continuing to investigate degraded performance primarily for unauthenticated users.
- · investigating
We are investigating reports of impacted performance for some GitHub services.
Degraded performance for multiple GitHub services · resolved · 2026-11-06T00:20:49.369Z
Product match: components.
Read the provider’s incident report
- · 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.
- · monitoring
This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report.
- · investigating
Git Operations is operating normally.
- · monitoring
We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC.
- · monitoring
The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability.
- · investigating
Issues is experiencing degraded performance. We are continuing to investigate.
- · investigating
We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC.
- · investigating
We are investigating reports of degraded performance for Actions and Pages
Incident with Actions · resolved · 2026-11-05T17:42:35.455Z
Product match: components.
Read the provider’s incident report
- · 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.
- · monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- · investigating
Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
- · investigating
We are investigating reports of degraded performance for Actions
Incident with Actions · resolved · 2026-11-07T01:10:18.506Z
Product match: components.
Read the provider’s incident report
- · resolved
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51
- · monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- · investigating
We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
- · investigating
We are investigating reports of degraded availability for Actions
Incident with Actions and Pages · resolved · 2026-11-07T01:04:38.647Z
Product match: components.
Read the provider’s incident report
- · resolved
On November 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were proc
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
- · investigating
We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
- · investigating
Actions is experiencing degraded availability. We are continuing to investigate.
- · investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
- · investigating
We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
- · investigating
We are investigating reports of degraded performance for Actions and Pages
Incident with Pull Requests, Git Operations and Issues · resolved · 2026-11-04T11:50:06.459Z
Product match: components.
Read the provider’s incident report
- · 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.
- · monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- · investigating
The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
- · investigating
We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.
- · investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
- · investigating
We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.
- · investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
- · investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- · investigating
We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
Increased task-related errors for Copilot Mission Control · resolved · 2026-11-04T10:01:44.589Z
Product match: unmapped.
Read the provider’s incident report
- · 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.
- · monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- · investigating
We're continuing to see recovery as rollout continues
- · investigating
We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.
- · investigating
Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations.
- · investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Git Operations · resolved · 2026-11-06T23:36:05.165Z
Product match: components.
Read the provider’s incident report
- · resolved
On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. This was due to a buildup of excess connections on the hosts that serve Git HTTP
- · monitoring
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
- · investigating
We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor.
- · investigating
Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.
- · investigating
We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.
- · investigating
We are investigating reports of degraded performance for Git Operations
Recovery tracker
Provider marked the incident resolved; independent website recovery is still being checked.
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: 13 ms · Earlier median: 16 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 emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
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.
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.
- Spectrum Availability Issue in Phoenix · monitoring
- Fedramp Customers have Delayed Purges · identified
About Github status on Iszdown
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.
This page combines the available Github report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
12 product-matched official components are listed above. Latest public website measurement: 2026-11-08T17:58:18.000Z.
Visit the official Github website · Official provider status · How it works
What to check when Github is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Repository or developer workflow fails
Check whether browsing a repository, cloning or pushing, and running Actions are affected separately. Save local work and avoid sharing private repository details in public reports.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Github outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Increase in timeouts for some unauthenticated users | 117 min | resolved | |
| Degraded performance for multiple GitHub services | 45 min | resolved | |
| Incident with Actions | 52 min | resolved | |
| Incident with Actions | 36 min | resolved | |
| Incident with Actions and Pages | 56 min | resolved | |
| Incident with Pull Requests, Git Operations and Issues | 120 min | resolved | |
| Increased task-related errors for Copilot Mission Control | 77 min | resolved | |
| Incident with Git Operations | 104 min | resolved |
Frequently asked questions about Github
Is Github down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T18:19:58.000Z.
How many Github outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T18:10:00.000Z to 2026-11-08T18:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Github show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Github feature.
When was Github status last updated?
The latest status observation was 2026-11-08T18:18:28.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Github had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Github or report a problem?
Use “Watch this service” to save Github in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Github
Check a related product separately; its status can differ from Github.