Is GitHub down right now?
Real-time GitHub status pulled directly from githubstatus.com — the same source GitHub itself uses to report incidents. We fetch the public Statuspage feed every 30 seconds, normalize it, and show whether Git Operations, Actions, Pull Requests, Issues, Pages, Packages, Codespaces, and Copilot are operational. If something is degraded, you’ll see the active incident, when it started, and what GitHub has acknowledged so far.
Major outage: AWS
GitHub
OperationalSource hosting, Actions, Pages, Packages, Copilot.
Status from www.githubstatus.com · last fetched 1s ago
Developer Platforms
Upstream returned 404
Upstream returned 404
Atlassian source hosting and Pipelines.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
FedRAMP workspaces and API orgs have degraded performance — started 4 days ago
Upstream returned invalid JSON
We’ve suspended access to Claude Mythos 5 and Claude Fable 5 — started 7 days ago
AI code editor — chat, tab, composer.
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
Run open-source ML models via API.
Cloud / Hosting
Service disruption: Increased Error Rates — started 51 days ago
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. — started 11 days ago
Workers AI experiencing degraded availability in some models — started 4 days ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Global app servers, Postgres, volumes.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Next.js hosting, Edge, Serverless functions.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain) — started 111 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
SMS Delivery Delays from Twilio Phone Numbers to Surf Telecom Brazil — started 1 day ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Transactional + marketing email at scale.
Auth / Identity
Communication
Trouble submitting workflow forms with file attachments on Android. — started 4 days ago
No public machine-readable feed; consult the official status page.
Voice, video, text servers and DMs.
Zoom Phone/Zoom Contact Center General Underlying Provider Maintenance — started 12 days ago
Monitoring / Dev Tools
Upstream returned invalid JSON
Upstream returned invalid JSON
APM, infra, logs, RUM, synthetics.
Collaborative design, FigJam, Dev Mode.
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
GitHub 90-day incident history
Last 90 days
66.67% incident-free
Quick facts about GitHub
- GitHub publishes its own status at githubstatus.com using Atlassian Statuspage.
- Components tracked: Git Operations, API requests, Webhooks, Issues, Pull Requests, Actions, Packages, Pages, Codespaces, Copilot.
- Outages are reported in your timezone here, but the upstream feed is in UTC.
- Copilot incidents appear under the GitHub status page — they don’t have a separate domain.
- Major outages are rare but historically have lasted between 30 minutes and 4 hours.
How do I know if it's GitHub or my own setup?
- Open this page on a different network — if GitHub still appears down here, it’s on their side.
- Run `git ls-remote https://github.com/YOUR_REPO.git` from your terminal. A 503 confirms a server issue.
- Check the Actions tab at github.com/<org>/<repo>/actions for queueing — Actions backlogs are common during partial outages.
- If only HTTPS clones are failing, try SSH (`git@github.com`). If both fail, it’s not your auth.
Frequently asked questions
Why is GitHub slow today?
If the dashboard above shows a degraded or partial-outage indicator, the slowness is on GitHub’s side. Common culprits are Actions queue backups, increased latency on Pull Requests, or Pages deploys timing out. Click "View details" on the GitHub card to see exactly which sub-system is affected.
How do I know if it’s GitHub or my internet?
Open this page on a separate network (mobile data, for example). If GitHub still appears down here, it’s a real outage. If the page loads cleanly here but you can’t reach GitHub from your network, the issue is local — try ping github.com and dig github.com to narrow down whether DNS or routing is the problem.
Where can I report a GitHub outage?
Outages are tracked on githubstatus.com, but to escalate one as a GitHub customer use https://support.github.com. For Enterprise customers, your designated support contact takes priority over public reports.
Does GitHub have a status API?
Yes — https://www.githubstatus.com/api/v2/summary.json returns a JSON snapshot of overall status plus every component. It’s public, requires no authentication, and is the same feed this page consumes.
How often does GitHub go down?
Looking at the last 90 days of the Statuspage feed, GitHub typically logs 1–4 incidents per month, most lasting under 30 minutes. The historical heatmap above shows the full picture for this service.
Is GitHub Copilot down separately?
Copilot is reported as a component on the same GitHub status page. If GitHub itself is operational but Copilot completions are failing, look for "Copilot" specifically in the affected components list.