BREAKING: GitHub Webhooks Down — Immediate Workarounds for Indie Hackers [4yz3c18qmdxn]

GitHub experiencing partial webhook disruption. What's affected, how to respond now, and recovery timeline.

BREAKING: GitHub Webhooks Incident — What You Need to Know

⚠️ STATUS: Investigating | SEVERITY: Minor | IMPACT: Partial

---

What's Down & Who's Affected

GitHub is currently experiencing an incident affecting webhook delivery. This impacts:

CI/CD pipelines relying on push/PR webhooks (GitHub Actions may be unaffected, but third-party webhook consumers are experiencing delays)

Automated deployments triggered by repository events

Bot integrations awaiting webhook payloads (Slack bots, Discord notifications, custom servers)

Third-party services like Vercel, Netlify, CodeShip waiting on repository event notifications

Custom automation you've built on webhook listeners

NOT affected: Git operations, repository access, GitHub Actions (so far), API calls via REST endpoints.

---

Immediate Workarounds — Do This Now

1. GitHub Actions Users

If using GitHub Actions for CI/CD, you're likely fine. Test a workflow manually if critical:

Go to your Actions tab

Click "Run workflow" to manually trigger builds

This bypasses webhook dependency

2. Third-Party Webhook Consumers (Vercel, Netlify, etc.)

Temporarily disable auto-deploys if you can't afford delays

Manually trigger deploys via platform dashboards

Monitor your hosting provider's status page (they may retry webhooks)

3. Custom Webhook Listeners

Implement exponential backoff + retry logic immediately if you don't have it

Add polling as fallback: query GitHub API every 5-10 minutes for recent commits instead of waiting for webhooks

Log all failed webhook attempts; you'll need this for recovery validation

4. Slack/Discord Bots

Switch to manual notifications if critical

Consider using GitHub's built-in Slack integration as temporary alternative

GitHub's native integrations may have different delivery paths

---

How to Check If Your Project Is Affected

1. Go to: Settings → Webhooks (in any affected repository) 2. Look for recent deliveries with status codes like 5xx or timeouts 3. Check timestamps: Are recent pushes/PRs missing corresponding webhook events? 4. Test manually: Make a small commit; wait 30 seconds. Did your integration react? 5. Monitor logs: Check your webhook receiver logs for request gaps

---

Alternative Tools to Consider (Short Term)

If you need immediate solutions:

GitHub Actions + Artifacts API – reliable alternative for most automation

Polling-based approach – query /repos/{owner}/{repo}/events API every N minutes

GitLab webhooks – if you mirror repos there as backup

Gitea/Gitops – self-hosted options (not practical right now, but note for future)

AWS EventBridge – can integrate with GitHub via custom polling

---

How to Monitor Recovery

1. GitHub Status Page: https://www.githubstatus.com/ (refresh every 2-3 min) 2. Your webhook dashboard: Settings → Webhooks → Recent Deliveries (watch for success rate recovery) 3. Test webhook: Create a dummy repo, push a commit, verify payload arrives 4. Community signals: Check #devops on relevant Slack communities (actual users report faster than status pages)

Expected recovery window: GitHub typically resolves webhook incidents within 30-90 minutes.

---

Bottom Line

✅ Expect delayed webhook delivery (minutes to hours)

✅ Use manual triggers or GitHub Actions as temporary fallback

�� Add retry logic now—it prevents future similar issues

✅ No action needed if you're not using webhooks

Stay calm. This is a partial, investigating incident—not a full outage. Your repos are safe.

Will update as GitHub reports progress.