- Detected by Pingoru
- Aug 05, 2025, 09:47 PM UTC
- Resolved
- Aug 06, 2025, 02:02 AM UTC
- Duration
- 4h 15m
Affected: Socket Dashboard
Timeline · 6 updates
-
investigating Aug 05, 2025, 09:47 PM UTC
We are investigating elevated errors and timeouts with loading organization alerts in the dashboard.
-
investigating Aug 05, 2025, 10:00 PM UTC
We are continuing to investigate this issue.
-
identified Aug 05, 2025, 10:08 PM UTC
An upstream cloud provider is having an outage, which is affecting the loading of analytics data in our dashboard. We are awaiting resolution from them. Scanning and blocking of threats continue to operate normally.
-
monitoring Aug 05, 2025, 10:25 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 05, 2025, 10:29 PM UTC
We have made changes to work around our provider issues. Dashboard analytics are currently working again. We are monitoring to ensure the service stays healthy.
-
resolved Aug 06, 2025, 02:02 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2025, 03:09 PM UTC
- Resolved
- Jul 28, 2025, 08:06 PM UTC
- Duration
- 4h 56m
Affected: Socket Dashboard
Timeline · 3 updates
-
investigating Jul 28, 2025, 03:09 PM UTC
We are seeing increased error rate when fetching alerts and analytics, and the team is investigating.
-
monitoring Jul 28, 2025, 03:29 PM UTC
We have increased capacity of the system by scaling up necessary components and we are seeing a decrease in the error rate. We will continue to evaluate our infrastructure to look for ways to avoid issues like this in the future.
-
resolved Jul 28, 2025, 08:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2025, 03:32 PM UTC
- Resolved
- Jul 20, 2025, 01:26 AM UTC
- Duration
- 9h 53m
Affected: JavaScript Analysis
Timeline · 4 updates
-
investigating Jul 19, 2025, 03:32 PM UTC
We are currently experiencing an outage where our system is running behind with downloading tarballs for npm. This issue is preventing users from receiving proper alerts on newly published npm package versions.
-
investigating Jul 19, 2025, 04:10 PM UTC
We have identified a processing backlog for npm tarball downloads. However, the backlog is actively being reduced, and services are working normally. We are investigating steps to increase system capacity.
-
monitoring Jul 19, 2025, 07:20 PM UTC
A fix has been implemented to increase the queue priority for downloading npm tarballs, and additional resources have been provisioned. We are already observing improvements and will continue to monitor the situation closely.
-
resolved Jul 20, 2025, 01:26 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 04, 2025, 12:31 AM UTC
- Resolved
- Jul 04, 2025, 12:42 AM UTC
- Duration
- 11m
Affected: Socket Dashboard
Timeline · 2 updates
-
investigating Jul 04, 2025, 12:31 AM UTC
We have discovered an issue with our processing of alerts for Org Alerts, Org Dependencies, and and Repo Alerts. It can take longer than usual for them to appear after the latest scan to the default branch of your repo. We are currently investigating.
-
resolved Jul 04, 2025, 12:42 AM UTC
Service is working normally again at this point
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2025, 07:43 PM UTC
- Resolved
- Jun 17, 2025, 08:39 PM UTC
- Duration
- 55m
Affected: Socket for GitHub
Timeline · 3 updates
-
investigating Jun 17, 2025, 07:43 PM UTC
We are currently investigating this issue.
-
identified Jun 17, 2025, 07:47 PM UTC
We are experiencing an elevated error rate on GitHub API requests due to an upstream GitHub incident.
-
resolved Jun 17, 2025, 08:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:47 PM UTC
- Resolved
- Jun 12, 2025, 09:10 PM UTC
- Duration
- 2h 23m
Affected: Socket APISocket for GitHubSocket WebsiteSocket DashboardPackage Pages
Timeline · 2 updates
-
identified Jun 12, 2025, 06:47 PM UTC
We are monitoring an issue with our upstream cloud providers that are having outages or degraded performance. This can impact the processing of the Github integration, Dashboard loading, and other features.
-
resolved Jun 12, 2025, 09:10 PM UTC
Our upstream cloud providers (Cloudflare, GCP, etc) have resolve their outages and operations should be back to normal.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 09:44 AM UTC
- Resolved
- Jun 03, 2025, 10:32 AM UTC
- Duration
- 47m
Affected: Socket for GitHub
Timeline · 2 updates
-
investigating Jun 03, 2025, 09:44 AM UTC
Engineering is investigating an issue that is causing the Socket Github App to process the Webhooks from Github very slowly. This could cause Socket PR checks to either get triggered after a long amount of time or Socket PR checks be in a pending state for longer than normal. times. We are actively investigating and working on fixing this.
-
resolved Jun 03, 2025, 10:32 AM UTC
This has been resolved and all checks should be performing as normal. We determined that the only impact was for the internal Socket org and customers should not have been impacted.
Read the full incident report →
- Detected by Pingoru
- May 30, 2025, 08:16 PM UTC
- Resolved
- May 30, 2025, 08:26 PM UTC
- Duration
- 10m
Affected: Socket for GitHub
Timeline · 2 updates
-
investigating May 30, 2025, 08:16 PM UTC
We are currently investigating this issue.
-
resolved May 30, 2025, 08:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 01, 2025, 06:42 PM UTC
- Resolved
- May 02, 2025, 01:42 AM UTC
- Duration
- 7h
Affected: Socket APISocket WebsiteSocket Dashboard
Timeline · 4 updates
-
investigating May 01, 2025, 06:42 PM UTC
We are currently investigating an incident for Socket that is causing an outage of the dashboard.
-
investigating May 01, 2025, 07:01 PM UTC
We are continuing to investigate this issue.
-
monitoring May 01, 2025, 07:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 02, 2025, 01:42 AM UTC
This incident has been resolved. The incident was caused by a DDoS attack on the Socket website. We are improving our DDoS mitigations to avoid future impact.
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2025, 01:12 AM UTC
- Resolved
- Apr 12, 2025, 03:30 AM UTC
- Duration
- 2h 18m
Affected: Socket APISocket for GitHubSocket Dashboard
Timeline · 2 updates
-
investigating Apr 12, 2025, 01:12 AM UTC
We have identified an incident where internal feature flags were inadvertently reset, potentially affecting user experience across our platform. We are currently investigating the impact of this issue and are actively working to restore configuration to its correct state.
-
resolved Apr 12, 2025, 03:30 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2025, 07:14 PM UTC
- Resolved
- Apr 09, 2025, 07:44 PM UTC
- Duration
- 30m
Affected: Socket APISocket for GitHub
Timeline · 2 updates
-
identified Apr 09, 2025, 07:14 PM UTC
Golang scans are currently failing. We are investigating a fix. Other ecosystems are unaffected.
-
resolved Apr 09, 2025, 07:44 PM UTC
We have deployed a fix that restored the behavior of Golang scans.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2025, 04:36 PM UTC
- Resolved
- Apr 07, 2025, 05:32 PM UTC
- Duration
- 55m
Affected: Socket WebsiteSocket DashboardPackage Pages
Timeline · 4 updates
-
investigating Apr 07, 2025, 04:36 PM UTC
We are currently investigating this issue.
-
investigating Apr 07, 2025, 04:38 PM UTC
We are continuing to investigate this issue.
-
monitoring Apr 07, 2025, 05:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 07, 2025, 05:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2025, 12:22 PM UTC
- Resolved
- Mar 25, 2025, 09:29 PM UTC
- Duration
- 9h 7m
Affected: Socket for GitHub
Timeline · 4 updates
-
investigating Mar 25, 2025, 12:22 PM UTC
We are currently investigating an issue with our GitHub App event processing. Socket security checks for pull requests appear to be stalled.
-
identified Mar 25, 2025, 02:24 PM UTC
We identified an issue with long-running database transactions which eventually led to transaction cancellations, affecting our ability to process GitHub events. We have now restored normal operation and are looking into identifying the root cause for the problem.
-
monitoring Mar 25, 2025, 08:52 PM UTC
We have located the root cause of the problem and have started implementing various fixes to prevent this scenario from arising again.
-
resolved Mar 25, 2025, 09:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2025, 03:52 PM UTC
- Resolved
- Mar 24, 2025, 05:58 PM UTC
- Duration
- 2h 5m
Affected: Socket for GitHubSocket DashboardPackage Pages
Timeline · 4 updates
-
investigating Mar 24, 2025, 03:52 PM UTC
We are currently investigating this and have cleared it for know instances where a package has been incorrectly flagged.
-
identified Mar 24, 2025, 04:00 PM UTC
We've identified the issue and are working on deploying a fix
-
monitoring Mar 24, 2025, 05:11 PM UTC
We have deployed a fix and monitoring to ensure that the incorrectly marked packages are correctly marked.
-
resolved Mar 24, 2025, 05:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2025, 01:12 PM UTC
- Resolved
- Mar 09, 2025, 02:44 PM UTC
- Duration
- 1h 31m
Affected: Socket APISocket WebsiteSocket DashboardPackage Pages
Timeline · 4 updates
-
investigating Mar 09, 2025, 01:12 PM UTC
We are currently investigating this issue.
-
monitoring Mar 09, 2025, 02:17 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 09, 2025, 02:26 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 09, 2025, 02:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2025, 11:39 PM UTC
- Resolved
- Feb 26, 2025, 02:12 AM UTC
- Duration
- 1d 2h
Affected: Socket for GitHub
Timeline · 2 updates
-
identified Feb 24, 2025, 11:39 PM UTC
We have identified an issue with some GitHub app check runs intermittently timing out on large repos. We are working on a fix.
-
resolved Feb 26, 2025, 02:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2025, 06:05 PM UTC
- Resolved
- Feb 24, 2025, 07:49 PM UTC
- Duration
- 1h 44m
Affected: Socket for GitHub
Timeline · 3 updates
-
investigating Feb 24, 2025, 06:05 PM UTC
We are currently investigating a high error rate for GitHub reports for select customers.
-
monitoring Feb 24, 2025, 07:21 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 24, 2025, 07:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2024, 12:00 AM UTC
- Resolved
- Sep 23, 2024, 09:04 PM UTC
- Duration
- 2d 21h
Affected: Socket for GitHub
Timeline · 2 updates
-
identified Sep 23, 2024, 04:21 PM UTC
Socket has identified an issue that is causing new installations of the Socket Github App to fail. We are currently working on fix for this. Normal operations for currently installed customers are not impacted.
-
resolved Sep 23, 2024, 09:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2024, 09:46 PM UTC
- Resolved
- Aug 08, 2024, 10:08 PM UTC
- Duration
- 22m
Affected: Socket for GitHub
Timeline · 3 updates
-
investigating Aug 08, 2024, 09:46 PM UTC
We are currently investigating this issue.
-
identified Aug 08, 2024, 09:52 PM UTC
We have identified the issue and have implemented mitigation. Github Bot reports are being generated again.
-
resolved Aug 08, 2024, 10:08 PM UTC
We have implemented a fix and processing is back to normal.
Read the full incident report →
