Incident with Webhooks API
Facts
- Source
- GitHub Status · original
- Started
- (19 h ago)
- Ended
- · lasted 51 min
- How it ended
- Microsoft marked it resolved.
- First captured by us
- Last changed
- (43 min ago)
- Affected services
- GitHub webhooks
Last text from Microsoft
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.
Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.
Official updates
Posted by GitHub Status, newest first.
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 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
What Microsoft changed
Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.
First version we captured
Captured · Microsoft's own timestamp · revision343ntf20Original text as we first saw it
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.