Incidentsby GlyphIncident with Issues and Webhooks
May 4, 15:45 UTCMay 4, 16:40 UTC
Duration
55m
Impact
Critical
Root cause
Not disclosed
GitHub, 90 days
69 incidents
Affected
Not listed by the vendor.
Lesson: Engineering teams should record full diagnostic details during incidents affecting issue tracking and webhook delivery systems.
What happened
On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures to prevent recurrence.
Timeline
- Resolved · May 4, 16:40 UTC
On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures to prevent recurrence.