Resolved: GitHub has been running normally again for over an hour, webhooks are delivered without delay and deploys from GitHub repositories start as usual. If a push during the disruption did not trigger a deploy, it can be started manually from the dashboard.

GitHub reports webhooks, pull requests and Actions as normal again. Delayed webhooks are being delivered, so pending deploys start automatically. We will keep monitoring for a while. If a deploy did not start after a push, it can be triggered manually from the dashboard.

GitHub has raised the severity of the disruption but reports first signs of recovery of its event platform. Webhooks and pull requests are still delayed. For deploys nothing has changed: automatic deploys after a push to a GitHub repository may start late, while a manual deploy from the dashboard works. The component "GitHub" under "Third-party services" also shows GitHub's current state.

GitHub has named the cause: increased load on its internal event platform is delaying webhooks, pull requests and Actions. GitHub is shifting traffic and adding capacity; the delays continue until this takes effect. For deploys nothing has changed: automatic deploys after a push to a GitHub repository may start late, while a manual deploy from the dashboard works.

New on this status page: under "Third-party services", the components "GitHub" and "Cloudflare-Proxy" now show the live state of these providers as far as it matters for CitexNode Deploy. GitHub is still reporting webhook delays; automatic deploys from GitHub repositories may therefore start late, while a manual deploy from the dashboard works.

GitHub is now also reporting delays for GitHub Actions; the disruption is still under investigation on their side. For deploys nothing has changed: automatic deploys after a push may start late, while a manual deploy from the dashboard works. The disruption may also delay the release of the patched PHP runtimes we are waiting for in the separate PHP security incident.

The cause is on GitHub's side: their webhook delivery is delayed, so push notifications reach us late. Nothing needs to be done on our side; once GitHub catches up on deliveries, pending deploys start automatically. If you don't want to wait, you can start the deploy manually from the dashboard. We keep monitoring the situation at GitHub.

Since 14:52 UTC GitHub has been reporting a disruption: webhooks, pull requests and GitHub Actions are delayed (https://www.githubstatus.com). As a result, automatic deploys after a push to a GitHub repository may start late. Our own build infrastructure is running normally; projects from other Git hosts are not affected, and a deploy started manually from the dashboard still works.