GitHub Outage History

The GitHub Codespaces component experienced degraded performance, causing intermittent issues for users and disrupting related workflows. The incident began at Nov 24, 2025 1:31 PM UTC and was resolved by Nov 24, 2025 3:06 PM UTC, lasting about 1 hour and 35 minutes. GitHub published two status updates noting degraded performance and ongoing investigation. User reports described Copilot chat timeouts in VS Code during the event, indicating the impact was focused on Codespaces-based services rather than the entire GitHub platform.

GitHub Actions experienced a brief degradation in performance beginning around Nov 19, 2025 5:48 PM UTC, with the Actions component listed as degraded at Nov 19, 2025 5:51 PM UTC. The outage lasted roughly 20 minutes and affected automation workflows that rely on GitHub Actions. The incident was resolved by Nov 19, 2025 6:11 PM UTC as the status returned to normal.

The provider issued 2 status updates during the incident describing the degraded performance and the subsequent recovery.

The GitHub outage began at 8:41 PM UTC and affected Git Operations with degraded availability, followed by Codespaces reporting degraded availability as the incident progressed. Users reported push/pull failures and remote access issues, and Codespaces environments experienced instability, signaling a partial outage across core development workflows.

The incident lasted about 1 hour and 15 minutes and was resolved by 9:56 PM UTC. GitHub issued 3 status updates documenting the ongoing investigation and eventual recovery for both Git Operations and Codespaces. Reports from users across many regions indicated a broad geographic footprint, reflecting widespread impact on development activities.

Users began reporting issues with Git operations on GitHub around 2:45 PM UTC, with many unable to push changes and some seeing internal server errors. The problem appeared as degraded performance in the Git Operations component and was most noticeable around 3:00 PM UTC. The incident was acknowledged when GitHub updated the status to warn at 3:06 PM UTC and the issue was resolved about 10 minutes later as the status returned to up at 3:16 PM UTC. Two official status updates were issued during the event. The disruption appeared to be globally observed, with developers across regions reporting push and pull failures or errors during the window.

The Copilot feature for GitHub experienced a partial outage, with code completion suggestions partially unavailable for a portion of users. The incident began at Nov 5, 2025 11:46 PM UTC and was resolved by Nov 6, 2025 12:06 AM UTC, lasting about 20 minutes. GitHub posted two status updates during the incident while engineering investigated and worked to restore Copilot Code Completions. The issue appeared to be limited to the Copilot component, with no broader disruption to GitHub services.

The GitHub Copilot code completion feature experienced degraded performance, with Copilot partially unavailable for roughly 35 minutes from Nov 5, 2025 10:56 PM UTC to 11:31 PM UTC. A small number of users reported Copilot issues beginning around 10:45 PM UTC.

GitHub's status page documented the incident with two updates: first, an investigation into degraded Copilot performance at Nov 5, 2025 10:56 PM UTC, and later a resolution indicating Copilot had returned to normal at 11:31 PM UTC. The issue affected the Copilot component and was resolved after about 35 minutes.

GitHub experienced degraded performance for GitHub Packages downloads, with failures returning 5xx errors and reported failure rates up to 15%. The incident began at 2:36 PM UTC when the GitHub Status page flagged an issue with the Packages component, and users reported problems publishing content and slower workflows around that time.

The outage lasted approximately 4 hours and 45 minutes and was resolved by 7:21 PM UTC as services returned to normal. Users could encounter interruptions when downloading packages or publishing packages, and related workflows (including Copilot usage) experienced slowdowns during the incident.

An incident affected GitHub Actions, causing degraded performance for executing workflows. The issue began around 4:43 AM UTC, with the Actions component listed as degraded after initial investigation at 4:46 AM UTC. The incident was resolved by 6:16 AM UTC when status returned to up. The provider issued 2 status updates during the incident. A small number of users reported issues, including a report from Pune, India. Impact was limited to Actions functionality; other GitHub services remained operational.

The outage began at 4:21 PM UTC and affected GitHub Codespaces and Actions, with users reporting failures to load or create Codespaces and disruptions to CI/CD workflows across multiple regions. The issue progressed from degraded performance to outages for Codespaces, with Actions also experiencing intermittent problems during the incident. The incident lasted about seven hours and was resolved by 11:16 PM UTC when Codespaces returned to normal; Actions was reported as operating normally by 9:06 PM UTC.

GitHub Actions experienced degraded performance due to problems with larger hosted runners, affecting workflows that rely on hosted runners and causing some users to see Copilot issues. The outage began at Oct 23, 2025 4:41 PM UTC when the Actions component entered a degraded state and GitHub indicated they were investigating with a follow-up by Oct 23, 2025 5:03 PM UTC. The incident lasted until Oct 23, 2025 8:26 PM UTC, when the Actions service returned to normal.

GitHub issued two official status updates during the incident describing the investigation and restoration. User reports were limited but described Copilot not working and disruptions to Actions-based workflows. The outage affected the Actions component, with service returning to full functionality after several hours.