GitHub Status · History · Incident #6386

RESOLVED

Incident with Webhooks

Minor · Started Aug 13, 2026 · 2:45 PM

  • Duration

    50m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

Incident with Webhooks

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.


  • Started

    Aug 13, 2026 · 2:45 PM

  • Resolved

    Aug 13, 2026 · 3:36 PM

  • Duration

    50m

  • Severity

    Minor

Event timeline

How this incident unfolded

  • Investigating

    Aug 13 · 2:45 PM GitHub

    We are investigating reports of degraded performance for Webhooks

  • Investigating

    Aug 13 · 2:46 PM GitHub

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  • Investigating

    Aug 13 · 2:46 PM GitHub

    Issues is experiencing degraded performance. We are continuing to investigate.

  • Investigating

    Aug 13 · 2:46 PM GitHub

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  • Investigating

    Aug 13 · 2:56 PM GitHub

    Packages is experiencing degraded performance. We are continuing to investigate.

  • Investigating

    Aug 13 · 2:58 PM GitHub

    We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.

  • Monitoring

    Aug 13 · 3:33 PM GitHub

    The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

  • Monitoring

    Aug 13 · 3:33 PM GitHub

    We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.

  • Resolved

    Aug 13 · 3:36 PM GitHub

    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.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.