Search

Changes / Socket / GitHub App reports not starting

Socket: Critical incident: GitHub App reports not starting

Summary

Socket’s GitHub App reports were not starting, affecting Integrations - Socket for GitHub and Socket for GitHub. The vendor rated the impact critical; the incident started at 2026-03-14 06:16 UTC and was resolved at 2026-03-14 06:54 UTC, lasting 37 min. Preliminary investigation showed high error rates from the upstream GitHub API.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: GitHub App reports not starting
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-14 06:16 UTC
AddedResolved time#5
Before: not present
After: 2026-03-14 06:54 UTC
AddedAffected components#6
Before: not present
After: Integrations - Socket for GitHub, Socket for GitHub
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating problems with GitHub App reports not starting. Preliminary investigation shows high error rates coming from the upstream GitHub API.
AddedUpdateresolved#8
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

WhenChangeKind
Critical incident: GitHub App reports not starting (this change)
Socket’s GitHub App reports were not starting, affecting Integrations - Socket for GitHub and Socket for GitHub. The vendor rated the impact critical; the incident started at 2026-03-14 06:16 UTC and was resolved at 2026-03-14 06:54 UTC, lasting 37 min. Preliminary investigation showed high error rates from the upstream GitHub API.
Major incident

All Socket changes → · Socket profile · Markdown · JSON