Live  /  GitHub  /  Incident

GitHub: Delayed Actions status check results

GitHub · github.comMinor incidentResolved2026-10-23 08:05 UTC
Public — what happened

Summary

GitHub reported a minor incident in which results from Actions workflows were showing up late within GitHub. The company said the delays began at 07:07 UTC, and it opened an investigation at 07:29 UTC after reports of slower performance. GitHub said some recovery was already visible by 07:31 UTC, that it had mitigated the problem by 07:53 UTC, and that results were back to normal delivery times as of 07:27 UTC. The incident was marked resolved at 08:05 UTC, and GitHub said it would keep monitoring and look for ways to reduce future impact.

Affected

Actions

As listed on GitHub’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach GitHub against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for GitHub: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the GitHub report →

More from GitHub

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the GitHub status & history page.

Related: GitHub status & history. SquidGrid is not affiliated with GitHub.