Disruption with Dependabot Alerts
Закончилось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.
Массовые сбои
с 18 октября, 23:00 по 25 октября, 19:20 · 0Массовых сбоев с 18 октября, 23:00 по 25 октября, 19:20 не было.
Все 1 сайт · доступность сайтов с 18 октября, 23:00 по 25 октября, 19:20.
Доступность сайтов на GitHub100%с 18 октября, 23:00 по 25 октября, 19:20
Ответ сайтов, медиана0,15 сс 18 октября, 23:00 по 25 октября, 19:20
Открывается сейчас1 из 1
Доступность сайтов за сутки
открывалисьс перебоямимногие не открывались· клетка — часИстория доступности
с 18 октября · клетка — деньСвои сайты GitHub
Открываются · 1
GitHub сообщает
за 30 дней · 11 объявлений · страница статуса →23 октября, 17:58 – 23 октября, 21:51
Degraded availability for GitHub Actions, GitHub Pages and Webhooks
ЗакончилосьOn October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost.
CCA Automations are delayed when starting an Automation
ЗакончилосьWe suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.
[Retroactive] Actions workflow run logs delayed
ЗакончилосьOn October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up.
Incident with Git Operations, Issues, Actions and Pull Requests
ЗакончилосьOn October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7
Incident with Git Operations, Pull Requests and Actions
ЗакончилосьOn October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected.
Disruption with some GitHub services
ЗакончилосьOn October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.
Incident with Actions
ЗакончилосьOn October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes.
Elevated request latency
ЗакончилосьOn October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.
[Retroactive] Actions workflow run failures after deployment gate approvals
ЗакончилосьOn October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval.
Copilot Code Review is unable to complete reviews
ЗакончилосьOn September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.
Как считаем
Каждый сайт открываем из России так же, как браузер посетителя. «Не открывается» — когда три проверки подряд кончились одним из исходов: нет ответа за 10 секунд, ошибка сервера, недействительный сертификат или страница «технические работы» вместо сайта. Защиту от ботов и запрет для роботов сбоем не считаем. Сайт, который не открывается из России, но открывается из-за рубежа, считаем отдельно. Площадка — сеть, через которую сайт отвечает: хостинг, защита от атак или собственная сеть компании. Видите ошибку — напишите нам, перепроверим.