21,228 outages in February - Here are the biggest:

Learn more
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    magnifying glass icon
    Sign Up
    Home • Service directory • GitHub • Outage History
    GitHub icon
    GitHub icon

    GitHub Outage History

    GitHub is up

    There were 154 GitHub outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    GitHub not working for you?

    GitHub not working for you?

    minor icon Minor

    : GitHub services degraded; Issues and Actions impacted

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 5 minutes)

    GitHub experienced a brief disruption affecting some services, with GitHub Actions showing degraded performance. The Issues component also experienced degradation during the incident. The outage began on and was resolved by , lasting about 1 hour and 5 minutes. Users attempting to run workflows or manage issues may have encountered delays and sporadic failures.

    GitHub’s status page documented the incident with two updates: first acknowledging a disruption and degraded performance in Actions, followed by a confirmation that affected components had returned to normal. The incident involved multiple components (Issues and Actions) and was resolved after a focused window of degraded service.

    minor icon Minor

    : GitHub Packages NPM registry intermittent during incident

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (30 minutes)

    GitHub reported an incident affecting the Packages component, with intermittent availability issues in the NPM registry. Other package registries were unaffected. The incident began at and was resolved by , lasting about 30 minutes. GitHub issued 2 status updates during the event, noting ongoing investigations. The NPM registry service returned to normal after the investigation.

    minor icon Minor

    : GitHub Actions degraded performance outage

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    GitHub Actions experienced degraded performance for about 1 hour and 23 minutes, affecting workflows and automation. Users may have seen slower queue times, delayed builds, or intermittent failures. The issue began around and the status page escalated to degraded at .

    The GitHub status page issued 2 updates during the incident, and the Actions component returned to normal by . The outage was limited to the Actions component.

    minor icon Minor

    : GitHub search degraded; multiple components affected

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 hours and 40 minutes)

    GitHub experienced degraded search and increased failure rates across several core areas, including API Requests, Actions, Issues, and Pull Requests, with Packages later affected. Users reported missing pull request lists, empty search results, and difficulties loading PRs and releases. The incident began at as GitHub noted investigations into degraded performance and began collecting diagnostics. The outage lasted roughly 3 hours and 44 minutes, ending with a recovery of the affected components. The provider issued 3 status updates during the incident to share findings and progress.

    GitHub issued multiple status updates detailing the ongoing investigation and the gradual restoration of services. By , the affected components had returned to normal and normal service resumed, with search and PR-related features functioning as expected again.

    minor icon Minor

    : GitHub Pull Requests degraded for nearly 2 hours

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 55 minutes)

    GitHub experienced degraded performance affecting the Pull Requests component, with users potentially seeing slower PR creation, updates, and related workflows. The issue began at and the status moved to warning at as engineers investigated. The outage lasted about 1 hour and 58 minutes and was resolved by . The provider issued 2 status updates during the incident, detailing investigation progress and recovery steps.

    major icon Major

    : GitHub PRs and Webhooks outage disrupts multiple features

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (30 minutes)

    An incident disrupted GitHub pull requests, issues, and related automation, with Webhooks and several services showing degraded performance and intermittent errors. Users reported PR pages failing and delays in PR processing. The incident began around with investigations, and at the status page listed a degraded condition across Issues and Webhooks. Webhooks degraded by , with broader impacts to additional components in subsequent updates. The outage affected five components: Issues, Webhooks, Git Operations, Actions, and Pull Requests, leading to partial outages and degraded performance for a broad set of workflows.

    The provider issued five status updates during the incident, and user reports surged in the early phase, indicating wide impact. The incident lasted roughly 34 minutes, from around to , with full recovery confirmed by the final update.

    minor icon Minor

    : GitHub Git Operations degraded by 429 errors

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    GitHub reported degraded performance for Git Operations and Actions beginning at as the status page noted an ongoing investigation into increased 429 errors. Users attempting Git pushes and running Actions workflows could experience slower operations or intermittent failures while the issue was investigated. The incident lasted about 1 hour and 20 minutes and included two official status updates as the situation evolved.

    minor icon Minor

    : GitHub partial outage hits API, Issues, and PRs

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (8 hours and 35 minutes)

    The incident began around when Git Operations entered a degraded state. Over the next hours, the impact expanded to API Requests, Issues, and Pull Requests as additional components were degraded. By , API Requests, Issues, and Pull Requests were listed as degraded and investigations continued. A related note at indicated GitHub Enterprise Importer migrations were stalled. The affected components gradually returned to normal, with all four core areas reported back to up by . The outage lasted about 8 hours and 35 minutes, during which users could have experienced slower responses or partial functionality in Git operations, workflow-related API calls, issues, and pull requests. The provider issued 4 official updates during the incident.

    minor icon Minor

    : GitHub Actions Hosted Runners delays briefly; job starts delayed

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (55 minutes)

    GitHub experienced a brief degradation in Actions Hosted Runners, with provisioning delays causing jobs to start later than expected. The incident began at when the Actions component moved to a degraded state, with users seeing delays of over 5 minutes for jobs starting. The issue was addressed and the service returned to normal by , for a total duration of about 55 minutes. The provider posted two status updates during the incident documenting investigation and subsequent recovery.

    minor icon Minor

    : GitHub Copilot Claude Sonnet 4 degraded for 15 minutes

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (15 minutes)

    GitHub Copilot experienced a brief degradation affecting the Claude Sonnet 4 model across Copilot Chat, VS Code, and other Copilot products, while other Copilot models remained available. The incident began at and was resolved by , lasting about 15 minutes. The issue was attributed to an upstream model provider, with no impact to other Copilot models. The status page logged two updates during the event, describing the degraded availability and restoration.

    GitHub icon

    Looking for more GitHub outage stats?

    Get real-time insights and historical data on GitHub outages.

    Looking to track GitHub downtime and outages?

    • Receive real-time status updates
    • Show current status on private or public status page
    • Be the first to know if service is down
    • Keep your team informed
    • Monitor alongside other services and websites
    Start monitoring for free