Is GitHub API down?

What works right now

• ●UpREST APIYes: api.github.com answers (gh, bots, CI steps).200 in 123 ms
• ●UpGit over HTTPS (not critical)Yes: git clone, fetch and push reach github.com.200 in 175 ms

Failing for you? Check whether it is you

1. Is it you? Check the rate limit first

   A 403 or 429 with x-ratelimit-remaining: 0 is a rate limit, not an outage. Unauthenticated calls get 60 requests an hour per IP; authenticated calls get 5,000. Checking costs nothing:

   gh api rate_limit
   # or
   curl -s https://api.github.com/rate_limit

   Copy

What to do while GitHub API is down

When GitHub API is down, scripts, bots, CI steps and the gh CLI that call api.github.com fail. Git itself (clone, fetch, push) is a separate system and may still work: see the Git over HTTPS line.

1. Back off and retry

   Honor Retry-After and x-ratelimit-reset, and retry with exponential backoff and jitter so every client does not retry at once.

2. Spend fewer calls

   Send If-None-Match with the last ETag. A 304 reply on an authenticated request does not count against your primary rate limit.

   curl -s -H "Authorization: Bearer $GH_TOKEN" -H 'If-None-Match: "ETAG_FROM_LAST_RESPONSE"' https://api.github.com/repos/OWNER/REPO

   Copy

3. Go modules keep working

   proxy.golang.org serves module versions it has already cached, so most go build runs do not need GitHub at all.

Last 24 hours

Last 30 days

Incident timeline

Outages our checks saw, and incidents from the official status page, newest first.

1. OfficialOct 23, 14:58 UTC · 3.9 hDisruption with Dependabot Alerts

   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.

2. OfficialOct 23, 7:29 UTC · 36 minDelayed Actions status check results

   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.

3. OfficialOct 22, 15:28 UTC · 11 hProject updates delayed

   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.

4. OfficialOct 22, 14:18 UTC · 1 hIncident with Actions Results

   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.

5. OfficialOct 21, 14:52 UTC · 4.5 hDelays for Pull Requests and Webhook deliveries

   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.

6. OfficialOct 19, 15:49 UTC · 1.1 hDegraded availability for GitHub Actions, GitHub Pages and Webhooks

   On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. <br /><br />Impact <br /><br /> - Workflow statu

7. OfficialOct 15, 18:31 UTC · 24 minCCA Automations are delayed when starting an Automation

   We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.<br />

8. OfficialOct 14, 0:12 UTC · 1 min[Retroactive] Actions workflow run logs delayed

   On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and r

9. OfficialOct 12, 12:21 UTC · 7.9 hIncident with Actions, Pull Requests and Issues

   On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br /><b

10. OfficialOct 7, 17:17 UTC · 48 minIncident with Git Operations, Issues, Actions and Pull Requests

    On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: http

11. OfficialOct 7, 16:25 UTC · 1 minIncident with Git Operations, Pull Requests and Actions

    On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data fail

12. OfficialOct 6, 19:57 UTC · 3.7 hSeveral services are degraded

    On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAu

13. OfficialOct 5, 23:47 UTC · 1.7 hDisruption with some GitHub services

    On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to

14. OfficialOct 5, 19:11 UTC · 3.6 hIncident with Actions

    On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br

15. OfficialOct 1, 14:47 UTC · 3.2 hActions Job Delays

    On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.19

16. OfficialOct 1, 13:37 UTC · 20 minElevated request latency

    On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on

17. OfficialOct 1, 11:34 UTC · 1 min[Retroactive] Actions workflow run failures after deployment gate approvals

    On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has reco

18. OfficialSep 28, 21:16 UTC · 52 minCopilot Code Review is unable to complete reviews

    On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not au

19. OfficialSep 24, 16:51 UTC · 3.8 hDisruption with billing information updates

    Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests

20. OfficialSep 23, 10:11 UTC · 18.7 hIncident across several services

    Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed

21. OfficialSep 15, 19:11 UTC · 49 minDisruption with some GitHub services

    On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock

22. OfficialSep 14, 18:40 UTC · 55 minActions Larger Runner Jobs for some customers may be slow to start

    On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute

23. OfficialSep 13, 9:16 UTC · 1.5 hIncident with several GitHub Services

    On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup. At peak, 8.8% of requests to

24. OfficialSep 4, 22:02 UTC · 21 minDegradation in repos contents API

    On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.<br /><br />The cause was a capacity change that spread one of our clusters across additiona

25. OfficialSep 4, 20:39 UTC · 1.8 hDisruption with Copilot Code Review

    On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permission

Official status

The official page: https://www.githubstatus.com/.

Get alerts, or show it in your README

Follow the RSS feed of GitHub API incidents in any reader, or paste this badge into a README; it updates itself.

[![GitHub API status](https://tensorust-status.vercel.app/api/badge?id=github-api)](https://tensorust.com/status/github-api/)

How we check GitHub API

Every 5 minutes, from Washington, D.C., with no API key. A failed check is retried once after 2 seconds before it counts; GitHub API is down when every critical check fails, and degraded when some do or the official page reports a problem.

• https://api.github.com/zen: api.github.com (a rate-limit reply still counts as up).
• https://github.com/octocat/Hello-World.git/info/refs?service=git-upload-pack: What git clone and git fetch talk to (not critical: a failure shows as degraded, not down).

Other services