Sep 4, 22:23 UTC
Resolved - On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence. Sep 4, 22:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Elevated request latency | 0 | 14.4 | 01-10-2026 |
| 2 | Incident across several services | 0 | 13.85 | 24-09-2026 |
| 3 | Incident with several GitHub Services | 0 | 15.23 | 13-09-2026 |
| 4 | Incident with Pull Requests | 0 | 10.44 | 20-09-2026 |
| 5 | Disruption with some GitHub services | 0 | 10.97 | 15-09-2026 |
| 6 | Disruption with some GitHub services | 0 | 11.39 | 26-08-2026 |
| 7 | Disruption with Copilot Code Review | 0 | 10.97 | 04-09-2026 |
| 8 | Disruption with some GitHub services | 0 | 8.51 | 06-10-2026 |
| 9 | Delays in commit processing | 0 | 14.66 | 01-09-2026 |
| 10 | Actions Larger Runner Jobs for some customers may be slow to start | 0 | 10.94 | 14-09-2026 |