GitHub Outage History

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.

GitHub's API Requests component experienced degraded performance, impacting users making API calls. Developers reported slower responses and occasional failures across regions. The outage began at 2:29 PM UTC and was first acknowledged at 2:31 PM UTC; the service remained degraded until 3:56 PM UTC when it returned to normal, for a duration of about 1 hour and 27 minutes.

GitHub's status page documented the investigation and subsequent recovery. The API Requests component moved from up to warn and back to up across two official updates during the incident. User reports indicated global distribution, with activity from multiple regions reporting API errors and slow responses.

GitHub Actions experienced degraded performance, impacting workflows that rely on Actions. Users reported very slow builds and delays in job execution across multiple regions. The issue was isolated to the Actions component. The outage began on 9:12 AM UTC and was resolved by 12:31 PM UTC, lasting about 3 hours and 19 minutes. The provider published 2 status updates during the incident.

GitHub's status page initially indicated an investigation into degraded performance for Actions and later confirmed recovery. Reports from users in various locations corroborate the degraded performance, indicating the impact was observed broadly rather than localized. The Actions component was the affected element throughout the incident.

GitHub Copilot experienced degraded performance for its coding assistance features beginning at 2:46 PM UTC. GitHub reported an investigation into degraded performance affecting the Copilot component, with users potentially noticing slower or less reliable Copilot suggestions during the event. The issue appeared isolated to Copilot and did not list other GitHub services as impacted. The incident lasted about 1 hour 55 minutes, resolving when Copilot returned to normal at 4:41 PM UTC. The GitHub Status page issued two updates during the incident.

The GitHub Codespaces creation service experienced an outage beginning at 8:57 AM UTC with GitHub noting investigations into degraded availability for Codespaces. Users attempting to create Codespaces encountered failures, impacting the Codespaces component and their workflows. The incident prompted GitHub to issue updates describing the degraded availability and ongoing investigation. The outage lasted roughly 2 hours and 4 minutes, resolving by 11:01 AM UTC. A small number of user reports were observed, including a report at 10:30 AM UTC and a sample comment from Madrid at 10:42 AM UTC.