There were 13 Socket outages since February 25, 2026 totaling 40h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue affecting a subset of Maven scans.
This incident has been resolved.
We are currently investigating an issue degrading system performance for a subset of our customers.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating a problem with delays in running scans via the GitHub App and API.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We have identified a problem causing increased error rates and timeouts throughout our system. We are working on a fix.
A fix has been implemented and we are monitoring.
This incident has been resolved.
We are observing a delay in starting GitHub App reports. We have identified the cause, and are rolling out a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are observing a delay in starting GitHub App reports. We have identified the cause, and are rolling out a fix.
This incident has been resolved.
We are currently investigating timeouts affecting ~1% of GitHub App reports.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of intermittent errors and elevated response times on the Socket API. Some requests may take longer than expected or require retries. We are actively working to resolve the issue and will provide updates as we have them.
We have rolled out a initial fixes and working on additional updates. Overall response times and errors have improved.
This incident has been resolved.
We are investigating reports of page load failures across the Socket dashboard. Some users may experience slow or failed page loads or API calls. We are actively working to resolve the issue and will provide updates as we have them.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating problems with GitHub App reports not starting. Preliminary investigation shows high error rates coming from the upstream GitHub API.
This incident has been resolved.
We are currently investigating an issue that is causing an outage due to DNS. We are investigating and determining the impact
We have identified the issue and seeing services load.
The outage was caused by a DNS migration which has now been resolved.
We are investigating an issue with some GitHub app reports not starting.
GitHub is having a Webhooks incident which may be impacting webhook deliveries to Socket. We are working to confirm this.
We have investigated further and still believe this to be a problem with GitHub upstream. We are working on implementing mitigations. If a PR has a stuck check run, please try closing and reopening the PR. This will cause GitHub to send another webhook, which should be delivered.
This incident has been resolved.
We are experiencing elevated GitHub App report run times. We are currently investigating.
This incident has been resolved.
Pingoru polls Socket's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required