GitHub statusLiveFetched seconds agoSource: githubstatus.com
Is GitHub down?
Live status check · All systems operational
Live status pulled from githubstatus.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About GitHub status
GitHub incidents reach almost every dev team at once. The platform splits into Git Operations, Actions, Pages, API, Codespaces, and Copilot — and an incident on one rarely affects the others, so naming the right component matters.
Components and surfaces that can break
- Surface 01
Git Operations (push, pull, clone) and the API.
- Surface 02
Actions, Packages, Pages, and Codespaces.
- Surface 03
Webhooks, Copilot, and the website itself.
Recent GitHub incidents
GitHub maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if GitHub is actually down
Identify the right component before assuming the worst
githubstatus.com splits 7+ components. Webhooks being delayed is a very different problem from Git Operations being down. If your CI is failing, check Actions specifically — Git Operations may still be fine.
GitHub Actions cron drifts even when GitHub is healthy
Scheduled workflows are best-effort and run late under load. If you depend on a 5-minute schedule firing on time, GitHub Actions is the wrong primitive even on a green-status day.
Webhook redelivery is your friend
If GitHub Webhooks are degraded and your downstream missed a delivery, use the 'Recent Deliveries' panel on the webhook settings page to redeliver manually once the platform recovers.
Keep firing through the incident
Schedule your own GitHub health check with Crontap
GitHub Actions scheduled workflows drift — sometimes by 15+ minutes under load — and missed runs are not caught up. If you're using Actions as cron, Crontap can call a webhook on the workflow's repository_dispatch event with the cadence you actually need.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
GitHub status: FAQ
- How do I check the right GitHub status component?
- githubstatus.com lists each component separately. Your symptoms map to a component: failing pushes → Git Operations; CI builds not starting → Actions; missing webhook deliveries → Webhooks. Read the right row first.
- Why are my GitHub Actions cron jobs late?
- Scheduled workflows are explicitly best-effort. Under load (especially at the top of the hour), they routinely drift 5-30 minutes. This isn't an outage — it's how the scheduler is designed.
- How do I trigger GitHub Actions on a precise schedule?
- Convert the schedule to a repository_dispatch webhook and have Crontap call it on the exact cron you need. Crontap fires on time, calls the GitHub API, and Actions starts the workflow synchronously. Full pattern in our GitHub Actions cron drift post.