← Back to GitHub History
minor✓ Resolved
Incident with Webhooks API
Status
resolved
Duration
51m
Updates
5
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
On November 12, 2026, between 17:59 UTC and 19:05 UTC, the GitHub Webhooks API experienced elevated latency and timeouts. During this time, about 1.23% of Webhooks API requests were slower than normal or timed out, peaking at about 3.63% of requests for a short period. 0.14% of webhook API requests failed during the incident. Webhook deliveries were unaffected. We traced the slow responses to elevated latency in an upstream database service that the Webhooks API depends on. Latency returned to normal at 19:05 UTC, and we continued to monitor until we resolved the incident at 19:33 UTC. We are working with our database provider to understand the cause and are improving our playbooks to detect degradations more quickly.
monitoring
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
investigating
Webhooks API has traffic has recovered. We will continue to monitor for stability.
investigating
Webhooks API is experiencing timeouts and errors impacting about 1% of customer traffic. We are working through possible mitigation strategies.
investigating
We are investigating reports of degraded performance for Webhooks
📊 TECHNICAL DETAILS
Internal ID
ebc2576d-e2cc-4487-bf28-2822bc067bc6
External ID
gl7yhd7jx00v
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
51m
Total Duration
5
Status Updates
Affected Components
Webhooks
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed