Socket: Elevated errors on the Socket API.
Affected components: Package PagesSocket API
Timeline of updates
- monitoring
We experienced a period of elevated errors on our API. We were able to immediately remedy the issue so no further impact is expected.
- resolved
The issue has not reoccurred since we initially corrected it.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-02 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
609cb2261d675ec2…Version 2 captured
In the 2026-11-02 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b5d7dc47698ae84a…
Impact, status and times are the vendor’s own, as last archived. View on status.socket.dev (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Socket, started 2026-11-02 16:49 UTC, resolved after 38 min, 2 update(s); edited after publishing.
- Title
- Elevated errors on the Socket API.
- Vendor
- Socket
- Date
- URL
- https://rewindex.com/company/socket/incidents/xphpt9smr8ps
Socket profileRecent Socket incidentsAll outages on November 2, 2026Socket in November 2026MarkdownJSON