Socket

Affected: Ticketing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-16 07:28 UTC

   We have observed that ticketing integrations are having delays in creating/updating/closing tickets. We have identified the cause and are working on a fix.

2. identified 2026-10-16 08:01 UTC

   We are starting a deploy which should resolve the issue for new tickets. After this completes we will work to get missed ticket updates replayed.

3. identified 2026-10-16 08:42 UTC

   We have restored live functionality and are working on replaying older events that were missed during the incident window.

4. resolved 2026-10-16 09:19 UTC

   Replay completed. Tickets service has been restored to normal operations.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-01 21:00 UTC

   All systems were impacted from slower responses times. As part of of the overall recovery from the maintenance yesterday. This has now been resolved and systems are back to normal status.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-01 07:59 UTC

   We have observed that ticketing integrations are having delays in creating/updating/closing tickets. We have identified the cause and are working on a fix.

2. identified 2026-10-01 09:02 UTC

   We have deployed a fix for new creations/updates/deletions going forwards. We are working on un-sticking delivery of the events from earlier in the incident window.

3. identified 2026-10-01 13:15 UTC

   The events that were missed during the incident window are being replayed now. The tickets should be creating/updating/closing.

4. monitoring 2026-10-01 14:56 UTC

   All the events have been replayed successfully. The tickets have been created/updated/closed accordingly.

5. resolved 2026-10-01 15:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-09-30 18:18 UTC

   Socket's GitHub app is experiencing event processing delays.

2. identified 2026-10-01 00:17 UTC

   We have partially stabilized the system but might continue to have degradation of the Github App. We expect this to be resolved by the emergency maintenance.

3. monitoring 2026-10-01 03:24 UTC

   A fix has been deployed and we are restoring full capacity.

4. monitoring 2026-10-01 03:24 UTC

   A fix has been deployed and we are restoring full capacity.

5. resolved 2026-10-01 03:35 UTC

   The GitHub app has been restored to full capacity and throughput.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Package Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-24 19:27 UTC

   We are currently investigating the issue

2. investigating 2026-09-24 19:28 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-24 19:38 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-09-24 20:14 UTC

   A fix has been implemented and we are monitoring the results

5. resolved 2026-09-24 21:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 22:13 UTC

   We are currently investigating this issue.

2. investigating 2026-09-22 23:15 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-23 01:15 UTC

   We identified the issue and resolved the cause.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 19:52 UTC

   We are currently investigating this issue.

2. identified 2026-09-17 20:21 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-17 20:35 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-17 22:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 16:54 UTC

   We are currently investigating this issue.

2. identified 2026-09-17 16:54 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-17 17:12 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-09-17 18:10 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-09-17 20:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-05 07:21 UTC

   We are currently investigating this issue.

2. identified 2026-09-05 07:30 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-05 07:41 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-05 09:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 23:05 UTC

   The Events collection system is incorrectly rejecting events.

2. resolved 2026-08-21 01:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-14 13:00 UTC

   We have identified an issue that is degrading Github App performance which might cause slow or stuck PR checks while we implement the fix.

2. resolved 2026-08-14 13:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Disruption with Login and Release Asset downloads.

1. monitoring 2026-08-12 22:02 UTC

   GitHub is currently experiencing a service disruption that may impact customers attempting to download GitHub-hosted releases, including Socket Firewall. This is an upstream GitHub issue and does not impact the operation of existing Socket Firewall deployments. Customers...

2. resolved 2026-08-12 22:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-04 21:52 UTC

   We have identified an issue causing delays in uploading events to our API.

2. resolved 2026-08-04 22:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 14:25 UTC

   We are currently investigating load errors for the dashboard overview and threat intel pages for select customers.

2. identified 2026-08-04 14:48 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-08-04 21:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Website, Socket Dashboard, Package Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 07:42 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-04 08:33 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-04 08:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-02 11:15 UTC

   We are currently investigating this but you may experience slower API queries then normal

2. monitoring 2026-08-02 14:18 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-02 14:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-30 21:48 UTC

   We are investigating delayed scan times.

2. identified 2026-07-30 21:50 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2026-07-30 22:46 UTC

   We've identified the problem and deployed remediation and are monitoring system performance. Request and report latencies are restoring to normal.

4. resolved 2026-07-30 23:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 12:27 UTC

   Currently investigating degraded performance in Socket's API.

2. identified 2026-07-24 14:54 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-24 16:35 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-24 17:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-24 11:00 UTC

   Currently investigating degraded performance to Socket's API.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 14:41 UTC

   We are currently investigating this issue.

2. investigating 2026-07-23 14:59 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-23 14:59 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-07-23 15:04 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-07-23 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-07-21 23:09 UTC

   We have identified an issue that is causing elevated latency for some requests on the GitHub App and API. We are working on a fix.

2. monitoring 2026-07-22 00:11 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-22 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2026-07-20 01:13 UTC

   We are observing elevated error rates on Socket's GitHub app due to elevated error rates originating from GitHub's API.

2. resolved 2026-07-20 02:28 UTC

   Upstream API requests appear to be operating normally now.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-16 22:48 UTC

   We are currently investigating an increase in Github App report error rates.

2. identified 2026-07-16 23:12 UTC

   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.

3. monitoring 2026-07-16 23:45 UTC

   GitHub has restored service.

4. resolved 2026-07-17 00:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-13 23:00 UTC

   Partial outage of ingesting new scans due to increased load.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2026-07-13 20:24 UTC

   We are seeing elevated timeouts and error rates on GitHub App reports. A fix has been implemented, and we are monitoring to ensure recovery.

2. resolved 2026-07-13 23:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-13 15:44 UTC

   We've observed degraded API performance and are investigating a fix.

2. identified 2026-07-13 16:30 UTC

   We have identified a degraded performance with the scans from the API and queued GitHub webhook durations. A fix is being put in place.

3. identified 2026-07-13 16:35 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2026-07-13 16:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. resolved 2026-07-08 17:29 UTC

   Socket's GitHub app is experiencing degraded performance causing delayed check run indicators.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-24 15:15 UTC

   We are currently investigating reports of degraded API and Integration performance

2. identified 2026-06-24 16:39 UTC

   The issue has been identified and we are deploying fixes.

3. resolved 2026-06-24 19:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-23 06:02 UTC

   We're investigating an issue where scans are taking longer than expected to complete.

2. monitoring 2026-06-23 07:01 UTC

   A fix has been deployed and we're monitoring the situation. Performance may remain degraded while we clear the backlog of queued scans.

3. resolved 2026-06-23 10:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-19 03:09 UTC

   We are currently investigating an issue affecting public package pages.

2. resolved 2026-06-19 04:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 16:15 UTC

   We are investigating elevated 4xx and 5xx status codes.

2. resolved 2026-06-16 16:32 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 21:56 UTC

   We are investigating degraded performance affecting API responses.

2. identified 2026-06-08 22:14 UTC

   We have identified a fix and are working on testing and deployment.

3. monitoring 2026-06-08 23:03 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-06-08 23:55 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-08 23:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 17:26 UTC

   We are investigating degraded performance affecting PURL API responses.

2. identified 2026-06-03 18:18 UTC

   We have identified a fix and are working on testing and deployment.

3. monitoring 2026-06-03 21:12 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-03 22:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 17:05 UTC

   We are investigating degraded performance affecting PURL API responses.

2. monitoring 2026-05-27 19:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-27 20:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 17:46 UTC

   We noticed that the page load times are increased and we are currently investigating the issue.

2. identified 2026-05-26 22:08 UTC

   We have identified a fix and it still working on it.

3. identified 2026-05-26 23:43 UTC

   We have implemented a fix, and system performance is recovering. We are continuing to monitor the system to ensure stability.

4. resolved 2026-05-27 02:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket Website, Socket Dashboard

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-25 08:44 UTC

   We have identified elevated latency and timeouts on socket.dev caused by high request load. We are working on a solution.

2. monitoring 2026-05-25 09:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-25 09:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-18 19:24 UTC

   Due to an increase in some traffic it has caused degraded performance on our system; we are implementing a fix.

2. monitoring 2026-05-18 21:14 UTC

   A fix has been implemented and it appears that numbers are recovering. We are monitoring until some backlogs are fully drained.

3. resolved 2026-05-19 00:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 15:48 UTC

   We are currently investigating reports of timeouts through our scan APIs.

2. monitoring 2026-05-05 16:57 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-05 20:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Package Pages, Java Analysis

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-29 19:48 UTC

   We are currently investigating an issue affecting a subset of Maven scans.

2. resolved 2026-04-29 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 21:52 UTC

   We are currently investigating an issue degrading system performance for a subset of our customers.

2. monitoring 2026-04-28 22:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-28 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-04-21 19:34 UTC

   We are currently investigating a problem with delays in running scans via the GitHub App and API.

2. identified 2026-04-21 19:34 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-04-21 20:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Website, Socket Dashboard, Package Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-11 17:00 UTC

   We have identified a problem causing increased error rates and timeouts throughout our system. We are working on a fix.

2. monitoring 2026-04-11 20:06 UTC

   A fix has been implemented and we are monitoring.

3. resolved 2026-04-11 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-04-08 20:25 UTC

   We are observing a delay in starting GitHub App reports. We have identified the cause, and are rolling out a fix.

2. monitoring 2026-04-08 22:14 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-08 23:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-04-07 16:17 UTC

   We are observing a delay in starting GitHub App reports. We have identified the cause, and are rolling out a fix.

2. resolved 2026-04-07 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-04-06 21:26 UTC

   We are currently investigating timeouts affecting ~1% of GitHub App reports.

2. monitoring 2026-04-06 22:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-06 22:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-30 12:01 UTC

   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.

2. identified 2026-03-30 15:57 UTC

   We have rolled out a initial fixes and working on additional updates. Overall response times and errors have improved.

3. resolved 2026-03-30 23:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Website, Socket Dashboard, Package Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 02:36 UTC

   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.

2. monitoring 2026-03-25 02:46 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-25 02:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-03-14 06:16 UTC

   We are currently investigating problems with GitHub App reports not starting. Preliminary investigation shows high error rates coming from the upstream GitHub API.

2. resolved 2026-03-14 06:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket API, Socket for GitHub, Socket Website, Socket Dashboard, Package Pages

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-13 22:27 UTC

   We are currently investigating an issue that is causing an outage due to DNS. We are investigating and determining the impact

2. investigating 2026-03-13 22:31 UTC

   We have identified the issue and seeing services load.

3. resolved 2026-03-13 22:34 UTC

   The outage was caused by a DNS migration which has now been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.

Affected: Socket for GitHub

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-03-06 16:15 UTC

   We are investigating an issue with some GitHub app reports not starting.

2. investigating 2026-03-06 17:50 UTC

   GitHub is having a Webhooks incident which may be impacting webhook deliveries to Socket. We are working to confirm this.

3. investigating 2026-03-06 20:53 UTC

   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.

4. resolved 2026-03-07 07:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Socket's status page.