starslingdev - Incident with Pull Requests, Issues, Git Operations and API Requests – Incident details

All systems operational

Incident with Pull Requests, Issues, Git Operations and API Requests

Resolved
Degraded performance
Started about 2 months agoLasted about 1 hour

Affected

Third Party: GitHub → API Requests

Operational from 12:10 PM to 12:10 PM, Degraded performance from 12:10 PM to 1:16 PM

Third Party: GitHub → Pull Requests

Operational from 12:10 PM to 12:10 PM, Degraded performance from 12:10 PM to 1:16 PM

Updates
  • Resolved
    UTC
    Resolved

    On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates (3.5% of pushes via HTTPS and 0.2% of pushes via SSH failed; no fetches/clones failed). An internal analytics component generated unexpectedly high load, which caused CPU saturation on the underlying infrastructure. This led to cascading slowdowns and errors across services that depend on Git operations. The issue was mitigated by stopping the offending component. Services began recovering shortly after mitigation and were fully restored by 13:16 UTC. We are taking steps to add resource limits and kill switches for internal analytics components to prevent similar issues in the future.

  • Update
    UTC
    Update

    We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.

  • Investigating
    UTC
    Investigating

    We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests