[2026-06-03] Incident Thread #197937
Replies: 9 comments 2 replies
-
UpdateWe're seeing delays in Dependabot scheduled version update runs. Our team is actively working on a fix and will share updates as the situation develops. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see any alerts about Copilot issues. I am only seeing "agent" and no "plan" mode, and all my requests are erroring out.
|
Beta Was this translation helpful? Give feedback.
-
UpdateCustomers may see delays of up to two days in Dependabot version updates. Dependabot Security updates are not delayed. The team is investigating mitigations for the backlog. Next update in 1 hour. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe are preparing a mitigation for the delayed Dependabot scheduled version updates. Next update in 2 hours. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. Next update in 12 hours. |
Beta Was this translation helpful? Give feedback.
-
UpdateJob 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. |
Beta Was this translation helpful? Give feedback.
-
UpdateJob lag has recovered to within normal operating thresholds. We are declaring this incident closed and will follow up with a summary soon. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.
-
Incident SummaryBetween June 1, 2026, 23:00 UTC and June 4, 2026 04:11 UTC, customers experienced delays in Dependabot scheduled version updates. Pull request creation for version updates was delayed, with delays increasing over time and reaching up to two days. Approximately 1.5 million repositories with active Dependabot version update configurations were affected. Dependabot security updates were not affected. The primary cause was changes to an internal platform service that routes requests for Dependabot and other services. We mitigated the incident by deploying a fix that enables batch enqueuing of update jobs, which significantly increased processing throughput. Once the backlog was drained, Dependabot returned to normal processing times. To reduce the risk of recurrence, we are working on tuning batch size and concurrency limits for Dependabot update job processing. We are also adding monitoring for job processing lag to enable earlier detection and faster mitigation of similar issues. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
❗ An incident has been declared:
Disruption with some GitHub services
Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.
Beta Was this translation helpful? Give feedback.
All reactions