Changes / Socket / Github App reports are failing
Socket: Critical incident: Github App reports are failing
Summary
Socket’s GitHub App reports failed in a critical-impact incident starting 2026-07-16 23:45 UTC, lasting 15 min and resolved at 2026-07-17 00:00 UTC. Socket attributed the failures to a high error rate on GitHub’s API and reported that GitHub restored service.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Incident page: full timeline of updates →
What changed
Before: not present
After: Github App reports are failing
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-16 23:45 UTC
Before: not present
After: 2026-07-17 00:00 UTC
Before: not present
After: Integrations - Socket for GitHub, Socket for GitHub
Before: not present
After: We are currently investigating an increase in Github App report error rates.
Before: not present
After: The GitHub App is failing due to a high error rate on GitHub's API: https://www.githubstatus.com/incidents/gxycch3076xk
We are dependent on GitHub to restore service.
Before: not present
After: GitHub has restored service.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When | Change | Kind |
|---|---|---|
| Critical incident: Github App reports are failing (this change) Socket’s GitHub App reports failed in a critical-impact incident starting 2026-07-16 23:45 UTC, lasting 15 min and resolved at 2026-07-17 00:00 UTC. Socket attributed the failures to a high error rate on GitHub’s API and reported that GitHub restored service. | Major incident |