Is GitHub down?
For agents
proceed
Proceed.
GET upbutler.com/status/github/status.agent.json
MCP: upstream_status {"service":"github"}
Git operations, Actions, API, Packages and Copilot. An Actions incident stalls every deploy that runs through it.
What GitHub reports
Operational
Taken as is from GitHub's own status page API. Incident titles and component names below are theirs.
Open www.githubstatus.comUpButler's independent probe
API edge is answeringHTTP 200 · 212 ms
One request without credentials to api.github.com every two minutes. An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
GitHub components
12 operational
- Git OperationsOperational
- WebhooksOperational
- Visit www.githubstatus.com for more informationOperational
- API RequestsOperational
- IssuesOperational
- Pull RequestsOperational
- ActionsOperational
- PackagesOperational
- PagesOperational
- CopilotOperational
- CodespacesOperational
- Copilot AI Model ProvidersOperational
GitHub incidents, last 90 days
9 finished incidents seen since UpButler started tracking on 2026-10-10, 6 of them rated major or critical by GitHub. A typical one lasted 1 h 10 min; the longest 3 h 43 min.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Incident with Git Operations, Issues, Actions and Pull Requests | critical | 48 min | |
| Incident with Git Operations, Pull Requests and Actions | critical | 1 h 10 min | |
| Several services are degraded | critical | 3 h 43 min | |
| Disruption with some GitHub services | major | 1 h 45 min | |
| Incident with Actions | critical | 3 h 38 min | |
| Actions Job Delays | minor | 3 h 9 min | |
| Elevated request latency | minor | 20 min | |
| [Retroactive] Actions workflow run failures after deployment gate approvals | minor | under a minute | |
| Copilot Code Review is unable to complete reviews | critical | 52 min |
Tell your outage from GitHub's
Declare that your project depends on GitHub. When one of your monitors fails while GitHub has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- githubcurl -s https://upbutler.com/status/github/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "github",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 200
}
}Questions
- Is GitHub down right now?
- No. As of 2026-10-10 05:08 UTC, GitHub is operational. This page reads the status again every 60 seconds.
- Where does this status come from?
- From GitHub's own status page API at https://www.githubstatus.com. UpButler reads it once for everyone (not once per visitor) every 60 seconds with conditional requests, and shows it unchanged: incident titles and component names are GitHub's words.
- What does UpButler's own GitHub check prove?
- Every two minutes UpButler sends one request without credentials to the GitHub API edge (api.github.com). Any answer from the edge, usually HTTP 200, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while GitHub reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check GitHub status?
- Fetch https://upbutler.com/status/github/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"github"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or GitHub's?
- Add "github" to the dependencies of your UpButler workspace. When one of your monitors fails while GitHub has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in code, packages and workflows
UpButler is not affiliated with GitHub. Status and incident text belong to GitHub and are read from their public status source; the probe result is UpButler's own measurement.