GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Disruption with Copilot Code Review

ResolvedmajorOfficial source confirmedFirst recorded update Sep 4, 2026, 08:39 PM · Resolved Sep 4, 2026, 10:26 PM

On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.<br /><br />We apologize for the disruption.

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Updates (5)

  1. Sep 4, 2026, 10:26 PM
    Disruption with Copilot Code Review

    On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.<br /><br />We apologize for the disruption.

    GitHub ↗
  2. Sep 4, 2026, 10:25 PM
    Disruption with Copilot Code Review

    The degradation has been mitigated. We are monitoring to ensure stability.

    GitHub ↗
  3. Sep 4, 2026, 09:54 PM
    Disruption with Copilot Code Review

    We are applying the mitigation and expect recovery within approximately 30 minutes.

    GitHub ↗
  4. Sep 4, 2026, 08:57 PM
    Disruption with Copilot Code Review

    Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.

    GitHub ↗
  5. Sep 4, 2026, 08:39 PM
    Disruption with Copilot Code Review

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

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.