GitHub experienced a minor incident on June 3, 2026, lasting 8h 29m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 03, 2026, 07:42 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 03, 2026, 07:43 PM UTC
We'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.
- investigating Jun 03, 2026, 08:18 PM UTC
Customers 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.
- investigating Jun 03, 2026, 09:10 PM UTC
We are preparing a mitigation for the delayed Dependabot scheduled version updates. Next update in 2 hours.
- investigating Jun 03, 2026, 11:38 PM UTC
We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. Next update in 12 hours.
- monitoring Jun 04, 2026, 02:35 AM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 04, 2026, 02:37 AM UTC
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.
- monitoring Jun 04, 2026, 04:11 AM UTC
Job lag has recovered to within normal operating thresholds. We are declaring this incident closed and will follow up with a summary soon.
- resolved Jun 04, 2026, 04:11 AM UTC
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.