Datvero automation observatory · www.githubstatus.com
No. GitHub's status page reports Actions operational, with no open incident affecting GitHub Actions (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
Read from GitHub's official status API at November 6, 2026, 18:10 UTC. Datvero republishes what GitHub states; it is not an independent uptime measurement.
From August 13 to November 6, 2026, www.githubstatus.com lists 22 incidents affecting Actions: 8 critical, 4 major, 10 minor and 0 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.3 h. Longest: “Project updates delayed” (October 22, 2026), 11 h. In the last 30 days: 13 incidents, 6 of them major or critical.
| Posted (UTC) | Incident | Impact | Components | Duration |
|---|---|---|---|---|
| Nov 5, 23:36 | Degraded performance for multiple GitHub services | minor | Git Operations, Issues, Actions, Pages | 45 min |
| Nov 5, 16:50 | Incident with Actions | minor | Actions | 52 min |
| Nov 4, 17:40 | Incident with Actions | major | Actions | 36 min |
| Nov 4, 16:05 | Incident with Actions and Pages | major | Webhooks, Actions, Pages | 56 min |
| Nov 4, 09:49 | Incident with Pull Requests, Git Operations and Issues | major | Git Operations, API Requests, Issues, Pull Requests, Actions | 2 h |
| Oct 30, 17:50 | Incident with Actions, Pages, and Webhooks | major | Webhooks, Actions, Pages | 1.5 h |
| Oct 26, 18:48 | Incident with Actions, Issues, API Requests and Pull Requests | minor | API Requests, Issues, Pull Requests, Actions | 9 min |
| Oct 23, 07:29 | Delayed Actions status check results | minor | Actions | 36 min |
| Oct 22, 15:28 | Project updates delayed | minor | API Requests, Issues, Pull Requests, Actions, Packages | 11 h |
| Oct 22, 14:18 | Incident with Actions | minor | Actions | 1 h |
| Oct 21, 14:52 | Delays for Pull Requests and Webhook deliveries | critical | Webhooks, Pull Requests, Actions | 4.5 h |
| Oct 19, 15:49 | Degraded availability for GitHub Actions, GitHub Pages and Webhooks | critical | Webhooks, Actions, Pages | 1.1 h |
| Oct 12, 12:21 | Incident with Actions, Pull Requests and Issues | minor | Issues, Pull Requests, Actions | 7.9 h |
| Oct 7, 17:17 | Incident with Git Operations, Issues, Actions and Pull Requests | critical | Git Operations, Issues, Pull Requests, Actions | 48 min |
| Oct 7, 15:14 | Incident with Git Operations, Pull Requests and Actions | critical | Git Operations, Webhooks, Issues, Pull Requests, Actions | 1.2 h |
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. GitHub's status page reports Actions operational, with no open incident affecting GitHub Actions (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
From August 13 to November 6, 2026, www.githubstatus.com lists 22 incidents affecting Actions: 8 critical, 4 major, 10 minor and 0 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 1.3 h. Longest: “Project updates delayed” (October 22, 2026), 11 h. In the last 30 days: 13 incidents, 6 of them major or critical.
This page covers Actions, as named on the official status page. For all of GitHub, see the GitHub page.
GitHub publishes it at https://www.githubstatus.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with GitHub.
The status page lists what GitHub has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to GitHub Actions succeeds.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: GitHub's public status API (www.githubstatus.com/api/v2) is read every 5 minutes, its incident list every 15 minutes, and each incident is kept with its official timestamps. Durations run from the first post to the resolved post. Machine readable copy: services.json. Official source: https://www.githubstatus.com/.
Statuses, incident names and texts belong to GitHub. Datvero is not affiliated with GitHub. A green status page does not mean every workflow that calls GitHub Actions succeeds.