Is GitHub Down?

Developer ToolsLive status, outages, and incident history

No. GitHub is up right now.

Every monitored GitHub system is operational as of October 6, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment GitHub breaks

GitHub is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official GitHub status page

How we know: the official GitHub status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

GitHub Component Status

The main GitHub systems on this page. All 12 are operational right now.

12operational

Actions

Operational

API Requests

Operational

Codespaces

Operational

9 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Copilot, Copilot AI Model Providers, Git Operations, Issues, Packages, Pages, Pull Requests, Visit www.githubstatus.com for more information, Webhooks.

See all of them free

Component statuses may change independently during partial outages.

Recent GitHub Outages & Incidents

Incident history from the official GitHub status page, including resolution updates.

Disruption with some GitHub servicesResolved Oct 5, 2026 · 1h 44mResolved

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. --- [2026-10-06T00:05:58.926Z] (investigating) Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery. --- [2026-10-05T23:47:45.254Z] (investigating) We are investigating reports of impacted performance for some GitHub services.

Incident with ActionsResolved Oct 5, 2026 · 3h 37mResolved

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. --- [2026-10-05T22:40:41.795Z] (investigating) Pages is operating normally. --- [2026-10-05T21:54:23.028Z] (investigating) Actions is operating normally. --- [2026-10-05T21:32:31.460Z] (investigating) We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages. --- [2026-10-05T21:31:18.177Z] (investigating) Actions is experiencing degraded performance. We are continuing to investigate. --- [2026-10-05T21:22:39.017Z] (investigating) Pages is experiencing degraded performance. We are continuing to investigate. --- [2026-10-05T21:09:15.654Z] (investigating) In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation. --- [2026-10-05T20:47:22.557Z] (investigating) Actions is experiencing degraded availability. We are continuing to investigate. --- [2026-10-05T20:39:27.955Z] (investigating) We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more. --- [2026-10-05T19:50:50.720Z] (investigating) We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more. --- [2026-10-05T19:15:17.486Z] (investigating) We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more. --- [2026-10-05T19:11:58.492Z] (investigating) We are investigating reports of degraded performance for Actions

Actions Job DelaysResolved Oct 1, 2026 · 3h 9mResolved

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. --- [2026-10-01T17:50:54.351Z] (investigating) GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition. --- [2026-10-01T16:48:51.025Z] (investigating) We are currently applying a mitigation and anticipate recovery within thirty minutes. --- [2026-10-01T16:10:24.539Z] (investigating) We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s. --- [2026-10-01T15:29:46.969Z] (investigating) We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes. --- [2026-10-01T15:20:46.089Z] (investigating) Actions is experiencing degraded performance. We are continuing to investigate. --- [2026-10-01T15:10:52.227Z] (monitoring) The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. --- [2026-10-01T15:02:41.043Z] (investigating) Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available. --- [2026-10-01T14:54:13.101Z] (investigating) We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal. --- [2026-10-01T14:47:48.228Z] (investigating) We are investigating reports of degraded performance for Actions

GitHub Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a GitHub incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Jul 899.45% average · 28 days with incidentsOct 6

Going further back: GitHub uptime by month and every recorded GitHub outage.

Live GitHub Outage Reports

Problems reported by engineers using GitHub. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No GitHub problems reported yet.

Something wrong with GitHub on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About GitHub

GitHub is a major code hosting platform with 100M+ developers and 200M+ repositories, powering software development workflows through Git version control, pull requests, GitHub Actions CI/CD, and GitHub Copilot AI. GitHub outages halt code pushes, CI/CD pipelines, and package installs. Track GitHub status and outages here.

Over the past 30 days, PulsAPI has measured GitHub uptime at 99.94%. Response times, incident history, and SLA tracking for GitHub are available on the PulsAPI dashboard.

GitHub Status FAQ

Is GitHub down right now?

The verdict at the top of this page comes from the latest poll of the official GitHub status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if GitHub is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until GitHub recovers.

How do I check GitHub uptime history?

PulsAPI tracks GitHub uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.94%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever GitHub changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect GitHub outages?

PulsAPI reads the official GitHub status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual GitHub components?

Yes. PulsAPI monitors 12 individual GitHub components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when GitHub goes down?

Yes. Create a free account and subscribe to GitHub: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with GitHub to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot GitHub problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor GitHub?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so GitHub plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track GitHub with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services