Disruption with some GitHub services

Resolved

Minor impact

Started

Lasted 3h 1m

View official incident ↗

Updates

  1. Resolved

    Between 2026-01-16 16:17 and 2026-01-17 02:54 UTC, some Copilot Business users were unable to access and use certain Copilot features and models. This was due to a bug with how we determine if a user has access to a feature, inadvertently marking features and models as inaccessible for users whose enterprise(s) had not configured the policy.<br /><br />We mitigated the incident by reverting the problematic deployment. We are improving our internal monitoring and mitigation processes to reduce the risk and extended downtime of similar incidents in the future.<br />

  2. Investigating

    The fix has been deployed and the issue resolved. We will continue to monitor any incoming reports.

  3. Investigating

    The deployment of the fix is still ongoing. We are now targeting 3:00 AM UTC for full resolution.

  4. Investigating

    The deployment is still in progress. We are still targeting 2:00 AM UTC for full resolution.

  5. Investigating

    Deployment of the fix is in progress. We are still targetting 2:00 AM UTC for full resolution.

  6. Investigating

    Some enterprise Copilot CLI users may encounter an "You are not authorized to use this Copilot feature" error. We have identified the root cause and are currently deploying a fix. Expected resolution: within 2 hours.

  7. Investigating

    We received multiple reports of 403s when attempting to use the Copilot CLI. We have identified the root cause and are rolling out a fix for affected customers.

  8. Investigating

    We are investigating reports of impacted performance for some GitHub services.