BREAKING: GitHub investigating degraded availability for Actions, Pages, and Webhooks

GitHub Actions, GitHub Pages, and Webhooks experiencing degraded availability. Immediate workarounds and alternatives inside.

What's Down

GitHub is currently investigating degraded availability affecting three critical services:

GitHub Actions: CI/CD pipeline execution may be delayed, failing, or not triggering

GitHub Pages: Static site deployments and hosting may be unavailable or slow

Webhooks: Event notifications to external services may not fire or experience delays

Repository access, pull requests, and direct Git operations appear unaffected at this time.

How to Check If You're Affected

1. Check GitHub Status: Visit [status.github.com](https://status.github.com) for official updates 2. Actions: Go to your repository's Actions tab—look for queued or stuck workflows 3. Pages: Try accessing your deployed GitHub Pages site directly; check the deployment status in repository settings 4. Webhooks: Review your external service logs to confirm webhook payloads aren't arriving

Immediate Workarounds

For GitHub Actions

Pause dependent workflows: Disable automation relying on Actions until service restores

Manual deployment: For critical deployments, use alternative CI/CD (see alternatives below)

Retry manually: Once available, manually re-run failed workflow jobs from the Actions tab

Local testing: Run tests locally before pushing to ensure code quality during outage

For GitHub Pages

Use cached versions: If your site is cached by browsers or CDNs, users may still access it

Temporary redirect: Point DNS to a backup hosting provider (Vercel, Netlify, etc.) if critical

Static file backup: Host built assets on S3, Cloudflare, or similar while Pages recovers

For Webhooks

Manual polling: Temporarily query GitHub API directly instead of waiting for webhook events

Delay external syncs: Postpone systems dependent on real-time webhook notifications

Re-deliver manually: Some webhook services allow manual re-delivery once restored

Alternative Services (Temporary Migration)

CI/CD Alternatives:

GitLab CI/CD

CircleCI

Travis CI

Jenkins

AWS CodePipeline

Hosting Alternatives:

Vercel (GitHub-integrated, instant fallback)

Netlify

Cloudflare Pages

AWS S3 + CloudFront

Traditional web hosting

Webhook Alternatives:

Zapier (polls GitHub API)

IFTTT

Custom polling scripts against GitHub REST/GraphQL API

What You Should Do Now

1. Check status.github.com for incident timeline and ETA 2. Notify your team if Actions or Pages are critical to your workflow 3. Stop starting new deployments until service stabilizes 4. Monitor external services that depend on GitHub webhooks 5. Document the incident for post-mortem analysis

Unclear Details

This report is based on the incident as described. Specific details about:

Root cause of degradation

Percentage of users affected

Exact ETA for resolution

Whether Enterprise is affected differently

...should be confirmed on the official GitHub Status page.

Last Updated: Monitor [status.github.com](https://status.github.com) for real-time updates.