Get told when GitHub breaks
One email when GitHub reports an incident, one when it is resolved. No account, nothing else.
Used only for GitHub status alerts. Every email carries an unsubscribe link.
GitHub components
12 of 12 operational
Show all 12 components
- Git OperationsOperational
- WebhooksOperational
- Visit www.githubstatus.com for more informationOperational
- API RequestsOperational
- IssuesOperational
- Pull RequestsOperational
- ActionsOperational
- PackagesOperational
- PagesOperational
- CopilotOperational
- CodespacesOperational
- Copilot AI Model ProvidersOperational
Recent GitHub incidents
The most recent incidents GitHub has published, newest first.
- critical
Incident with Copilot AI Model Providers
Resolved in 2h 8m
- minor
Disruption with GitHub Billing
Resolved in 20h 7m
- minor
Incident with Actions and Pull Requests
Resolved in 1h 30m
- critical
Incident with Actions
Resolved in 2h 50m
- minor
Disruption with some GitHub services
Resolved in 59m
- minor
Actions delays in starting runs
Resolved in 38m
- major
Elevated errors on Fable 5 due to upstream provider
Resolved in 47m
- none
Degraded Git Operations over SSH
Resolved in 0m
- critical
Intermittent failures creating agent tasks
Resolved in 9h 54m
- major
Incident with Actions
Resolved in 47m
GitHub status: common questions
- Is GitHub down right now?
- GitHub is not reporting any problems. All 12 components are operational. No incident is open. This page mirrors the official GitHub status feed. PingView last read it on August 31, 2026 at 07:40 AM UTC.
- Where does this GitHub status data come from?
- Directly from the official GitHub status page at www.githubstatus.com. PingView polls that feed, records every incident it publishes and keeps a permanent, dated history that the vendor page itself does not retain.
- How often is this page updated?
- PingView reads the official GitHub feed and rebuilds this page every 5 minutes. The timestamp of the last successful read is shown next to the status, so you can tell how fresh the answer is.
- GitHub reports everything as operational, but my integration is failing. What now?
- A vendor status page is a global signal, not a per customer one. Partial failures, regional routing problems and issues that hit a single account often never appear on it. Check the GitHub endpoints your own product calls, from more than one region, and compare your timeline against the vendor's. That is what PingView does, and the SLA calculator turns the resulting downtime into a number you can put in front of a client.