Is GitHub down right now?

As of 7/16/2026, 8:37:46 PM, GitHub is operational. This page is updated every 60 seconds with live monitoring data.

How do I check GitHub status?

Check apistatuscheck.com/api/github for real-time GitHub monitoring, and compare with the official GitHub status page at https://www.githubstatus.com.

Where is the official GitHub status page?

The official GitHub status page is https://www.githubstatus.com. You can also track updates here on API Status Check at https://apistatuscheck.com/api/github.

What should I do when GitHub is down?

When GitHub is down: (1) Check the official status page for incident updates and estimated resolution time. (2) Confirm the issue is not local — test on another device or network. (3) If you're a developer, implement exponential backoff retry logic instead of hammering the API. (4) Subscribe to outage alerts on this page so you're notified the moment GitHub recovers. (5) Consider a fallback or alternative service for critical workloads.

Is GitHub Down?

Q: Is GitHub down for everyone or just me?

To confirm whether it's a global GitHub outage or an issue isolated to your account: (1) Check the current status indicator at the top of this page — if we show a major outage, it's affecting all users. (2) Try accessing GitHub from a different device or network to rule out local issues. (3) Clear your browser cache and cookies, then retry. (4) Check community reports on Downdetector or social media for other users reporting the same problem. If the service fails on multiple devices and networks, it's down for everyone.

Real-time status monitoring

All Systems Operational

30d uptime100.00%

100.00%

Uptime (30d)

22ms

Response Time

Incidents (7d)

8:37:46 PM

Last Checked

As of 7/16/2026, 8:37:46 PM, GitHub is operational.

📡 Monitor GitHub uptime every 30 seconds — get alerted in under a minute

Trusted by 100,000+ websites · Free tier available

Start Free →

⚡ Get notified instantly when GitHub goes down

Email alerts in under 60 seconds. 14-day free trial — $0 today.

Start Free Trial →

Embed GitHub Status Badge

Show live GitHub status in your README, documentation, or website

Markdown

[![GitHub Status](https://apistatuscheck.com/api/badge/github)](https://apistatuscheck.com/api/github)

HTML

<a href="https://apistatuscheck.com/api/github"><img src="https://apistatuscheck.com/api/badge/github" alt="GitHub Status" /></a>

Browse all 100 API badges →

Response Time (24h)

Min: 50msMax: 1028msAvg: 93ms

1028ms514ms0ms

<500ms

500-2000ms

>2000ms

Recent Incidents

criticalresolved

Disruption with some GitHub services

Jul 16, 09:13 AM — Resolved Jul 16, 12:20 PM

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

minorresolved

Incident with Webhooks

Jul 14, 05:38 PM — Resolved Jul 14, 06:01 PM

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

minorresolved

Disruption with some GitHub services

Jul 14, 08:21 AM — Resolved Jul 14, 09:56 AM

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

majorresolved

Actions runs are experiencing failures to start

Jul 13, 01:32 PM — Resolved Jul 13, 01:53 PM

On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes. The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained. To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.

criticalresolved

Delays starting Actions runs

Jul 9, 04:34 AM — Resolved Jul 9, 01:52 PM

On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start.At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.

View full outage history →

Get GitHub Outage Alerts

Be the first to know when GitHub go down.

Alert Pro

14-day free trial

Stop checking — get alerted instantly

Next time GitHub goes down, you'll know in under 60 seconds — not when your users start complaining.

Email alerts for GitHub + 9 more APIs
$0 due today for trial
Cancel anytime — $9/mo after trial

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys

What is GitHub?

Code hosting and version control platform

Official Status Page →API Documentation →

GitHub Down? Try These Steps

Check the official GitHub status page for announcements
Try refreshing your browser or clearing cache
Check your internet connection
Try accessing from a different network or VPN
Check social media for reports from other users
Set up automated monitoring so you know before your users do — Better Stack monitors every 30 seconds

Is GitHub down for everyone or just me?

To determine whether it's a widespread GitHub outage or a problem specific to your account or location:

Check the status indicator above — if this page shows a major outage, it's confirmed global.
Try a different device or network — if it works on mobile data but not Wi-Fi, it's likely a local network issue, not GitHub.
Clear cache and cookies — browser issues can mimic service outages.
Check community reports — Downdetector and social media will show whether hundreds of other users are reporting the same issue.
Test the API directly (for developers) — a raw request returning 5xx errors confirms a service-side outage; a 429 means you've hit your personal rate limit.

Official source: GitHub Status Page

⏱️

The average API outage costs $5,600 per minute

Gartner estimates downtime costs $5,600/min on average. 98% of organizations say a single hour of downtime costs over $100,000. Proactive monitoring catches issues in under 30 seconds.

Monitor with Better Stack →Calculate your cost →