outages.live
Live
GitHubIncident ·

Incident with Webhooks API

ResolvedOfficial update
0

GitHub Webhooks API had timeouts and errors that affected about 1% of customer traffic. GitHub mitigated the degradation and monitored stability. The incident is resolved and lasted about 51 minutes.

State

Resolved

Started

Lasted

51 min

Worst impact

Degraded

Timeline

5 updates
18:4318:5519:0819:2119:33
DegradedNoticeUpdate postedTimes in UTC

Investigating

32 min 63%

Resolved

6 min 12%

Monitoring

13 min 25%

Updates

Times in UTC

As posted by GitHub

Resolved

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.

Monitoring

The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.

Investigating

Webhooks API is experiencing timeouts and errors impacting about 1% of customer traffic. We are working through possible mitigation strategies.

Resolved
Investigating

We are investigating reports of degraded performance for Webhooks

Affected components

1
Webhooks

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

44

Median duration

1 h 12 min

This incident

30% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

20 h 7 min
median 1 h 12 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Disruption with Sign-in and Sign-up

GitHub sign-in and sign-up do not work for some users. Email delivery for account sign-in and new account sign-up is disrupted. GitHub is investigating.

Degraded

GitHub·Impact across multiple GitHub products including Actions, Pages, and Copilot products.

GitHub reports a major outage that affected Webhooks, Actions, Pages, and Copilot. GitHub later reported recovery across all services and monitored the fix. GitHub marked the incident resolved. The outage lasted 33 minutes.

Resolved

GitHub·Incident with Webhooks

GitHub Webhooks had degraded performance. GitHub reports that the incident is resolved. The outage lasted 4 minutes.

Resolved

GitHub·Incident with Git Operations and Pull Requests

Git operations and Pull Requests had elevated response times and failures, and Actions workflows triggered from Pull Requests were delayed. GitHub reports that the incident is resolved. It lasted 1 hour and 44 minutes.

Resolved

GitHub·Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot

GitHub reports degraded availability for the GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol models in Copilot products and IDE surfaces. GitHub mitigated the issue and monitored the service for stability. The outage is resolved and lasted 50 minutes.

Resolved

Follow GitHub

Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "github" and tell me if GitHub has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=github
Slack
/feed subscribe https://outages.live/feed.xml?providers=github

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane