Disruption with some GitHub services
Status: investigating
Customers may see delays of up to two days in Dependabot version updates.<br /><br />Dependabot Security updates are not delayed.<br /><br />The team is investigating mitigations for the backlog.<br /><br />Next update in 1 hour.
Affected components:
At: Jun 3, 2026, 20:18:52 GMT, details
Status: investigating
Customers may see delays of up to two days in Dependabot version updates.<br /><br />Dependabot Security updates are not delayed.<br /><br />The team is investigating mitigations for the backlog.<br /><br />Next update in 1 hour.
Affected components:
At: Jun 3, 2026, 20:18:52 GMT, details
Disruption with some GitHub services
Status: investigating
We are preparing a mitigation for the delayed Dependabot scheduled version updates.<br /><br />Next update in 2 hours.
Affected components:
At: Jun 3, 2026, 21:10:56 GMT, details
Status: investigating
We are preparing a mitigation for the delayed Dependabot scheduled version updates.<br /><br />Next update in 2 hours.
Affected components:
At: Jun 3, 2026, 21:10:56 GMT, details
Disruption with some GitHub services
Status: investigating
We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. <br /><br />Next update in 12 hours.
Affected components:
At: Jun 3, 2026, 23:38:20 GMT, details
Status: investigating
We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. <br /><br />Next update in 12 hours.
Affected components:
At: Jun 3, 2026, 23:38:20 GMT, details
Disruption with some GitHub services
Status: monitoring
Job lag has recovered from a peak of 1.71 days to 9h 9m at 19:29 UTC and continues to decrease. Backlog is draining at a healthy rate with no signs of reversal. New jobs are processing on schedule. Remaining lag will continue to drain over the next few hours as queued work completes; this is expected post-incident catch-up, not active impact. We will continue monitoring and re-engage if lag trend reverses.
Affected components:
At: Jun 4, 2026, 02:37:07 GMT, details
Status: monitoring
Job lag has recovered from a peak of 1.71 days to 9h 9m at 19:29 UTC and continues to decrease. Backlog is draining at a healthy rate with no signs of reversal. New jobs are processing on schedule. Remaining lag will continue to drain over the next few hours as queued work completes; this is expected post-incident catch-up, not active impact. We will continue monitoring and re-engage if lag trend reverses.
Affected components:
At: Jun 4, 2026, 02:37:07 GMT, details
Disruption with some GitHub services
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Disruption with some GitHub services
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Disruption with some GitHub services
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 04:11:59 GMT, details
Copilot Code Review Failing
Status: investigating
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress.
Affected components:
At: Jun 4, 2026, 18:03:24 GMT, details
Status: investigating
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress.
Affected components:
At: Jun 4, 2026, 18:03:24 GMT, details
Copilot Code Review Failing
Status: investigating
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress.
Affected components:
At: Jun 4, 2026, 18:03:24 GMT, details
Status: investigating
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress.
Affected components:
At: Jun 4, 2026, 18:03:24 GMT, details
Copilot Code Review Failing
Status: investigating
We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress, we expect mitigation in approximately 30m.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
Affected components:
At: Jun 4, 2026, 18:22:27 GMT, details
Status: investigating
We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress, we expect mitigation in approximately 30m.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
Affected components:
At: Jun 4, 2026, 18:22:27 GMT, details
Copilot Code Review Failing
Status: investigating
The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
Affected components:
At: Jun 4, 2026, 18:52:02 GMT, details
Status: investigating
The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
Affected components:
At: Jun 4, 2026, 18:52:02 GMT, details
Copilot Code Review Failing
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 4, 2026, 19:07:42 GMT, details
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 4, 2026, 19:07:42 GMT, details
Copilot Code Review Failing
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 4, 2026, 19:07:42 GMT, details
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 4, 2026, 19:07:42 GMT, details
Copilot Code Review Failing
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Copilot Code Review Failing
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Copilot Code Review Failing
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Status: resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Affected components:
At: Jun 4, 2026, 19:59:27 GMT, details
Live updates degraded
Status: investigating
We are investigating reports of impacted performance for some GitHub services.
Affected components:
At: Jun 4, 2026, 20:20:39 GMT, details
Status: investigating
We are investigating reports of impacted performance for some GitHub services.
Affected components:
At: Jun 4, 2026, 20:20:39 GMT, details
Disruption with some GitHub services
Status: investigating
We are investigating reports of impacted performance for some GitHub services.
Affected components:
At: Jun 5, 2026, 17:20:31 GMT, details
Status: investigating
We are investigating reports of impacted performance for some GitHub services.
Affected components:
At: Jun 5, 2026, 17:20:31 GMT, details
Disruption with some GitHub services
Status: investigating
Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
Affected components:
At: Jun 5, 2026, 17:25:44 GMT, details
Status: investigating
Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
Affected components:
At: Jun 5, 2026, 17:25:44 GMT, details
Disruption with some GitHub services
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 5, 2026, 18:05:00 GMT, details
Status: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Affected components:
At: Jun 5, 2026, 18:05:00 GMT, details
Accidentally deleted subscriptions for chat integrations (Slack and MS Teams)
Status: monitoring
We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
Affected components:
At: Jun 5, 2026, 18:43:49 GMT, details
Status: monitoring
We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
Affected components:
At: Jun 5, 2026, 18:43:49 GMT, details