Skip to main content
HostTracker
HOST-TRACKER
website monitoring service
Status pages Instant check Price
Login Register

GitHub outage on October 19, 2026: Degraded availability for GitHub Actions, GitHub Pages and Webhooks

GitHub reported an incident affecting GitHub for 1 hour 8 minutes on 19 October 2026, from 15:49 to 16:56 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started
15:49
19 Oct 2026 UTC
Resolved
16:56
19 Oct 2026 UTC
Duration
1h 8m
1 hour 8 minutes
Impact
Critical
as rated by GitHub
Updates
6
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Degraded availability for GitHub Actions, GitHub Pages and Webhooks

Resolved Critical impact 19 Oct 2026 15:49 UTC View on GitHub's status page
  1. Official
    Investigating

    We are investigating reports of degraded performance for Actions and Pages

  2. Official
    Investigating

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  3. Official
    Investigating

    We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. Customers may experience delays in workflow processing, site builds and webhook delivery.

  4. Official
    Investigating

    We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.

  5. Official
    Monitoring

    Actions, Pages and Webhooks are operating normally.

  6. Official
    Resolved

    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. Impact - Workflow status updates, logs, and checks were delayed. - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. Pages deployments and webhooks generated by Actions runs were delayed. An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to...

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.