Semgrep

Affected: Scans and CI/CD

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 21:00 UTC

   Some scans with Semgrep 1.181.0 are unable to be successfully reported to the Semgrep AppSec Platform due to a 400 error. The issue may be related to dynamic dependency resolution.

2. identified 2026-10-19 21:20 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2026-10-19 23:05 UTC

   We have released a fix for this issue and are monitoring to confirm resolution.

4. resolved 2026-10-19 23:49 UTC

   This issue has been resolved.

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

Affected: Dashboard, 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-10-15 19:18 UTC

   We are currently investigating an issue where some asynchronous tasks on the platform are lagging.

2. monitoring 2026-10-15 20:27 UTC

   We have applied a fix and are seeing lag decrease significantly. We will continue to monitor for full recovery.

3. resolved 2026-10-15 20:35 UTC

   This issue has been resolved, and the platform is behaving normally.

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

Affected: Login/SSO

Failure mode: Login, tokens, certificates or credentials failed. 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-10-05 16:00 UTC

   We are currently observing intermittent login failures on semgrep.dev for users signing in with GitHub and GitLab. Affected users may see an "unrecoverable error" page after clicking Continue. Our team has identified the cause and is working on a fix.

2. resolved 2026-10-05 16:14 UTC

   We have rolled out a fix, and logins are now working as expected. This incident has been resolved.

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

Affected: Login/SSO, Dashboard, API, Scans and CI/CD, Managed Scans

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-30 14:07 UTC

   We are currently investigating the source of these issues

2. investigating 2026-09-30 14:26 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-30 14:26 UTC

   Issue has been identified and a fix is rolling out

4. monitoring 2026-09-30 14:36 UTC

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

5. resolved 2026-09-30 18:23 UTC

   Monitoring indicates the platform continues to be stable, and this issue has been resolved.

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

Affected: Dashboard, API, Scans and CI/CD, Managed Scans

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 medium confidence (taxonomy v0.2).

1. identified 2026-09-22 19:24 UTC

   We are currently investigating issues with scans uploading findings which prevents the successful completion of scans. Additionally, we are aware of issues accessing the web user interface.

2. monitoring 2026-09-22 19:27 UTC

   Engineering initiated a rollback to fix issues with scans uploading findings preventing successful completion of Managed Scans and CI scans. We are verifying the fix before marking resolved.

3. resolved 2026-09-22 19:37 UTC

   Resolved. All products were confirmed to be operational, but Engineering will remain on standby to respond to customer reported issues.

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

Affected: Scans and CI/CD, Managed Scans

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-14 18:23 UTC

   We are currently investigating the issue.

2. resolved 2026-09-14 19:33 UTC

   This incident has been resolved.

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

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. investigating 2026-09-10 16:17 UTC

   We are investigating an increase in traffic causing platform wide issues. The UI, scanning, and API may be affected.

2. monitoring 2026-09-10 16:21 UTC

   We believe we have recovered, we are monitoring for additional impact.

3. resolved 2026-09-10 16:36 UTC

   This incident has been resolved.

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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 23:13 UTC

   An incomplete patch release of Semgrep 1.176.1 has left installations of this version using PyPI unable to use the Pro Engine. We recommend explicitly installing version 1.175.1 or 1.176.0 as we work to resolve this issue.

2. resolved 2026-09-04 23:38 UTC

   This issue has been resolved. The Pro Engine can be installed and used normally after installing Semgrep 1.176.1 via PyPI.

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

Affected: Managed Scans

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: AWS.

1. investigating 2026-09-03 21:35 UTC

   We are currently investigating this issue.

2. investigating 2026-09-03 21:55 UTC

   AWS STS outage in us-west-2 is affecting our system. We are investigating mitigations.

3. monitoring 2026-09-03 22:30 UTC

   Early signs of recovery for all Semgrep products. We are actively monitoring AWS updates on the regional, multi-service outage.

4. resolved 2026-09-03 22:45 UTC

   Metrics show full recovery of all Semgrep products. Our engineering team will continue monitoring until the final update from AWS.

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

Affected: Managed Scans

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).

1. identified 2026-09-01 22:50 UTC

   A small number (<1%) of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing since August 28, due to rate limiting applied by a public package registry. Affected projects may show incomplete or missing Supply Chain findings. We...

2. identified 2026-09-01 22:55 UTC

   Under one percent of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing, due to rate limiting applied by a third-party package registry. Affected projects may show incomplete or missing Supply Chain findings. We are rolling...

3. monitoring 2026-09-02 16:25 UTC

   The third party registry's rate limits have been lifted, and impact to scans appears mitigated.

4. resolved 2026-09-03 00:10 UTC

   Dynamic maven & gradle scans are now operating as normal.

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

Affected: Dashboard, Scans and CI/CD

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-25 19:21 UTC

   A bad release is causing widespread failures in the Semgrep AppSec Platform.

2. monitoring 2026-08-25 19:28 UTC

   The release has been rolled back and the platform is now stable.

3. resolved 2026-08-25 22:01 UTC

   This issue has been fully resolved with a successful release.

Excerpts are shortened. Read the full incident on Semgrep'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-08-13 11:30 UTC

   Semgrep experienced an outage affecting login, the API, and scans from 2026-08-13 23:43 UTC to 23:52 UTC. The incident has been resolved.

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

Affected: Managed Scans

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-08-12 18:16 UTC

   We are currently investigating this issue.

2. identified 2026-08-12 19:33 UTC

   We've identified the root cause of the issue and are currently working on a fix.

3. monitoring 2026-08-12 20:23 UTC

   We have rolled out a fix, and scans are now working as expected. We are closely monitoring to ensure continued stability.

4. resolved 2026-08-12 21:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Semgrep'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. investigating 2026-07-23 21:07 UTC

   We are currently investigating this issue.

2. identified 2026-07-23 21:10 UTC

   We have identified the issue and are actively working on a fix.

3. monitoring 2026-07-23 21:30 UTC

   A fix has been deployed. We will continue to monitor our systems to ensure that the issue has been resolved.

4. resolved 2026-07-23 21:36 UTC

   This incident has been resolved.

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

Affected: Dashboard, 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. monitoring 2026-07-20 20:07 UTC

   Processing of findings data has been delayed since approximately 03:20 UTC and is currently lagging approximately 3 hours behind realtime. The underlying cause has been addressed and we are monitoring to ensure the backlog is processed.

2. monitoring 2026-07-20 21:58 UTC

   Backfill is continuing and lag has reduced to approximately 1 hour behind realtime. We continue to monitor to ensure progress.

3. resolved 2026-07-20 22:58 UTC

   This issue has been resolved, and findings data is now displaying normally.

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

Affected: Login/SSO

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).

1. investigating 2026-07-16 09:38 UTC

   We're aware of an issue where customers with custom SSO configs are unable to login to Semgrep and are seeing a 504 Gateway Timeout error. The issue is under investigation

2. resolved 2026-07-16 12:46 UTC

   This incident has been resolved by the third party vendor

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

Affected: Dashboard

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-15 18:08 UTC

   We've observed that when trying to add a new memory, the Memories page crashes, and we are investigating the issue.

2. identified 2026-07-15 18:29 UTC

   We've identified the root cause and observed that both creating and editing memories is affected. We are working on a fix for the issue.

3. resolved 2026-07-15 20:14 UTC

   The fix has been released and this issue is resolved.

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

Affected: Scans and CI/CD, Managed Scans

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-25 21:32 UTC

   We have observed widespread scan failures relating to a bad release of AI skills rules. We are working to fix the issue. To prevent the issue in the meantime, you can disable the "skills.behavioral.skill-destructive-commands.skill-destructive-commands" rule in your Semgrep...

2. monitoring 2026-06-25 22:14 UTC

   We have removed the problem rule ("skills.behavioral.skill-destructive-commands.skill-destructive-commands") and we are seeing scan behavior recover. We are continuing to monitor for full recovery.

3. resolved 2026-06-25 22:27 UTC

   This issue has been resolved. Scans are now running normally.

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

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-22 18:52 UTC

   We are currently investigating this issue.

2. identified 2026-06-22 19:34 UTC

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

3. investigating 2026-06-22 21:14 UTC

   We are currently investigating this issue.

4. monitoring 2026-06-22 21:55 UTC

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

5. resolved 2026-06-22 22:51 UTC

   This incident has been resolved.

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

Affected: Scans and CI/CD, Managed Scans

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 15:30 UTC

   We are currently investigating an issue causing degraded scan performance in CI and Semgrep Managed Scans, and are actively working to resolve it.

2. identified 2026-06-08 16:29 UTC

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

3. monitoring 2026-06-08 16:59 UTC

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

4. monitoring 2026-06-08 17:17 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-08 17:18 UTC

   This incident has been resolved.

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

Affected: Login/SSO

Failure mode: Login, tokens, certificates or credentials failed. 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-05-20 17:34 UTC

   We are currently observing login issues using GitHub auth. Our team has identified the issue and is currently working on a fix. SSO logins are working as expected and are not impacted.

2. monitoring 2026-05-20 17:49 UTC

   We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability.

3. monitoring 2026-05-20 18:17 UTC

   This incident has been resolved.

4. resolved 2026-05-20 18:18 UTC

   This incident has been resolved.

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

Affected: Managed Scans

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 medium confidence (taxonomy v0.2).

1. investigating 2026-05-20 01:18 UTC

   We are currently investigating an issue where full project scans in Managed Scans are being associated with HEAD rather than the name of the default branch. This issue started around 16:00 UTC on May 19 and may result in unexpected new findings notifications, and some findings...

2. identified 2026-05-20 02:08 UTC

   We have identified the issue and are working on a resolution.

3. monitoring 2026-05-20 02:47 UTC

   We have deployed the fix and are monitoring.

4. resolved 2026-05-20 02:52 UTC

   This incident has been resolved.

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

Affected: Managed Scans

Failure mode: Orchestration, control plane, service discovery or load balancing failed. 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-19 18:54 UTC

   We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.

2. investigating 2026-05-19 19:21 UTC

   We are continuing to investigate the issue. We will post updates when further information is available.

3. identified 2026-05-19 19:47 UTC

   We have identified a likely cause of this incident. We are currently rolling out a change to address it.

4. identified 2026-05-19 21:07 UTC

   Since the beginning of the incident, a portion of SMS scans have failed to execute. We have deployed a change to the system. We are seeing scheduling queues begin to recover, and we're continuing to monitor the situation.

5. monitoring 2026-05-19 21:26 UTC

   The scan success rate is recovering. We are continuing to monitor the system.

6. resolved 2026-05-19 21:33 UTC

   This incident has been resolved. We are continuing to monitor the system.

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

Affected: Login/SSO, Dashboard, API

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-05-12 17:27 UTC

   We are currently investigating a performance issue with the Semgrep AppSec Platform that started around 16:00 UTC (9:00 AM Pacific).

2. investigating 2026-05-12 17:51 UTC

   The performance of the platform is beginning to return to baseline. We are continuing to investigate what caused the issue.

3. investigating 2026-05-12 20:08 UTC

   We are continuing to investigate the issue. While overall performance has remained relatively stable since 10:30 Pacific, some reporting metrics and issue details may lag behind realtime.

4. investigating 2026-05-12 22:36 UTC

   Latency and errors have increased in the last hour. We are continuing to investigate the performance issues and apologize for the impact.

5. investigating 2026-05-13 00:01 UTC

   We have applied mitigations but are continuing to investigate the root cause of the issue. Platform performance may still lag at times and some reporting and issue status data may be stale.

6. resolved 2026-05-13 16:24 UTC

   This issue has been resolved. We determined that the performance degradation had multiple contributing causes and will be working to address those issues.

Excerpts are shortened. Read the full incident on Semgrep'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-04-30 22:00 UTC

   Between 21:48 - 22:00 UTC some managed scans experienced additional latency. The root cause has been resolved.

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

Affected: Login/SSO

Failure mode: Login, tokens, certificates or credentials failed. 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-04-28 18:16 UTC

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

2. monitoring 2026-04-28 19:11 UTC

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

3. resolved 2026-04-28 19:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Semgrep'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-04-24 12:30 UTC

   From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.

Excerpts are shortened. Read the full incident on Semgrep'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 medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. resolved 2026-04-23 16:00 UTC

   Starting around 16:00 UTC, some diff-aware Managed Scans for GitHub.com projects failed due to inability to fetch information about relevant branches, coinciding with a degradation in GitHub availability. The failure rate returned to normal just after 17:00 UTC and the system is...

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

Affected: Scans and CI/CD, Managed Scans

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-22 18:14 UTC

   We have identified a problem in the service that generates the configuration for new scans. This incident began at approximately 17:30 UTC, and it affects both Managed Scans and CI scans. We have taken action and are actively monitoring the system. If you have a scan that is...

2. resolved 2026-04-22 18:35 UTC

   This incident has been resolved.

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

Affected: Login/SSO, Managed Scans

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-20 20:37 UTC

   Some users are unable to log in; some managed scans are failing to start, and CI scans may not be able to process results. We're investigating the cause of all three.

2. identified 2026-04-20 21:56 UTC

   We've identified the cause of the backend issues. Some traffic has resumed but services are still degraded, and we're continuing to remediate.

3. resolved 2026-04-21 00:29 UTC

   The problem is resolved and scans and logins are now processing normally.

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

Affected: Managed Scans

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. investigating 2026-04-14 00:02 UTC

   Since 22:00 UTC, some fail-open processes for unfinished Managed Scans may have been delayed up to 40 minutes. We are investigating the issue.

2. monitoring 2026-04-14 00:46 UTC

   We have implemented a change to allow faster processing of fail-open requests, and the delay has reduced to under 5 minutes. We are monitoring to ensure the system remains stable.

3. resolved 2026-04-14 17:23 UTC

   This issue has been resolved. Fail-open processes for unfinished Managed Scans continue to run normally.

Excerpts are shortened. Read the full incident on Semgrep'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. identified 2026-04-13 17:08 UTC

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

2. monitoring 2026-04-13 17:32 UTC

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

3. resolved 2026-04-13 18:13 UTC

   This incident has been resolved.

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

Affected: Dashboard, API, Scans and CI/CD

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. investigating 2026-04-08 19:35 UTC

   Since around 16:45 UTC, we have observed errors related to processing SCA dependencies. Some new dependency results since that time may not be available in the platform, and related licenses may not have been analyzed. We are investigating the issue and confirming the scope of...

2. identified 2026-04-08 20:03 UTC

   We've identified the issue and are working on a fix. In addition to dependency and license results, some expected comments and other notifications may not be surfaced while the issue is active.

3. monitoring 2026-04-08 20:20 UTC

   We've released a fix and are seeing errors start to resolve.

4. resolved 2026-04-08 21:10 UTC

   This issue has been resolved, and scan processing is completing normally.

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

Affected: Dashboard

Failure mode: Login, tokens, certificates or credentials failed. 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-03-31 17:14 UTC

   We've identified an issue starting approximately 24 hours ago where users with read-only access to Semgrep AppSec Platform do not see their projects, and are working on a fix.

2. monitoring 2026-03-31 19:03 UTC

   We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm.

3. resolved 2026-03-31 21:36 UTC

   This issue has been resolved, and read-only users should be able to view their projects as normal.

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

Affected: Dashboard, 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. monitoring 2026-03-26 15:27 UTC

   Starting March 26 around 06:00 UTC, findings data in Semgrep AppSec Platform may have been out of date by up to 9 hours. We have implemented a fix and are monitoring as data backfills.

2. monitoring 2026-03-26 19:38 UTC

   Realtime sync is now healthy. We are continuing to monitor the data backfill.

3. monitoring 2026-03-26 23:43 UTC

   Data backfill is now complete for most organizations. We are continuing to monitor the final syncs.

4. monitoring 2026-03-27 18:20 UTC

   Data backfill continues to progress, and realtime sync remains healthy.

5. resolved 2026-03-30 23:55 UTC

   All data has backfilled and the system is healthy.

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

Affected: Managed Scans

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-17 21:22 UTC

   We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.

2. monitoring 2026-03-17 22:21 UTC

   We have released a fix for this issue and are monitoring the results.

3. resolved 2026-03-17 22:37 UTC

   This issue has been resolved and scans are behaving normally.

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

Affected: Managed Scans

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-13 18:10 UTC

   Errors started Mar 12 at 21:30 PST and have been increasing since then.

2. investigating 2026-03-13 18:15 UTC

   We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail. This is primarily affecting diff scans, which are used for checks on PRs and MRs. The error rate began to rise at approximately 21:30PT on Thursday, March 12 (2026-03-13 04:30 UTC)....

3. identified 2026-03-13 18:55 UTC

   We have identified the cause of the problem and are working on a fix.

4. monitoring 2026-03-13 19:25 UTC

   We’ve assessed that the scan failures are due to insufficient resources allocated to scans in particular projects. In response, we increased the resources available to affected projects. We are actively monitoring scan performance, and we’re seeing errors diminish. If your...

5. resolved 2026-03-13 19:48 UTC

   This incident has been resolved.

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

Affected: GitHub Pull Requests, Scans and CI/CD, Managed Scans

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-03-06 12:04 UTC

   We are investigating reports of issues affecting repository scans and pull request checks. Some customers may see scans not starting or checks not appearing on pull requests. We are investigating and will share updates as more information becomes available.

2. investigating 2026-03-06 12:24 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-03-06 15:47 UTC

   We've identified the root cause of the issue that was affecting repository scans and pull request checks, and a fix has now been rolled out. We are now monitoring the results to make sure everything is running smoothly.

4. resolved 2026-03-06 16:18 UTC

   This issue has been resolved, and scans have returned to normal operation.

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

Affected: Login/SSO

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-03 19:23 UTC

   We are currently investigating a crash on the login page for Semgrep AppSec Platform. Existing sessions in the platform are still operative.

2. identified 2026-03-03 19:28 UTC

   We have identified the source of the issue and are working on a fix.

3. monitoring 2026-03-03 19:42 UTC

   We have released a fix and the login page is now loading. We are monitoring for system stability.

4. resolved 2026-03-03 20:05 UTC

   This issue has been resolved. Login and other platform functions are behaving normally.

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

Affected: Scans and CI/CD, Managed Scans

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-02-24 22:38 UTC

   We are currently investigating an issue with scan results not being processed. You may see scan jobs appear to hang or time out at the stage of reporting findings to the platform.

2. investigating 2026-02-24 23:13 UTC

   We have rolled out a fix and are seeing scan results processing resume. We are monitoring the system for stability.

3. resolved 2026-02-24 23:20 UTC

   This issue has been resolved, and the system is now processing scans normally.

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

Affected: Scans and CI/CD, Managed Scans

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-02-23 18:09 UTC

   We've identified an increase in errors for starting and completing scans since approximately 17:00 UTC (9:00 AM PST), and are working to resolve the issue.

2. monitoring 2026-02-23 19:50 UTC

   Scan start and completion performance is now normal and we are continuing to monitor.

3. resolved 2026-02-23 20:13 UTC

   This issue has been resolved, and the services are currently behaving normally.

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

Affected: Scans and CI/CD, Managed Scans

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-02-12 17:09 UTC

   We are currently investigating an issue with degraded performance of scan start and completion in CI and Semgrep Managed Scans.

2. monitoring 2026-02-12 17:29 UTC

   We have made changes to improve service availability and scans are now able to start and complete as expected. We will continue to monitor.

3. resolved 2026-02-12 17:54 UTC

   This issue has been resolved, and scans are starting and completing normally.

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

Affected: Login/SSO, Dashboard, API, Registry

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-02-11 21:49 UTC

   Semgrep AppSec platform is slow to load or returning errors, and we're currently investigating the issue.

2. monitoring 2026-02-11 22:09 UTC

   The platform appears to be stable now, and we're currently monitoring the results.

3. resolved 2026-02-11 23:05 UTC

   The platform has remained stable, and this issue is considered resolved.

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

Affected: Managed Scans

Failure mode: Orchestration, control plane, service discovery or load balancing failed. 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-01-27 23:20 UTC

   Some scans running in Semgrep Managed Scans are currently delayed in starting. We're investigating the cause.

2. monitoring 2026-01-28 00:02 UTC

   We've addressed the underlying reasons for the scan delays and Managed Scans are returning to normal. We'll continue to monitor to ensure the issue is resolved.

3. resolved 2026-01-28 00:47 UTC

   This incident has been resolved.

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

Affected: 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-01-15 19:47 UTC

   We have identified intermittent errors occurring on some platform services, and we are investigating.

2. monitoring 2026-01-15 22:28 UTC

   We have implemented a fix and are monitoring the platform for stability.

3. resolved 2026-01-16 20:47 UTC

   This issue has been resolved, and the platform is currently stable.

Excerpts are shortened. Read the full incident on Semgrep'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 medium confidence (taxonomy v0.2).

1. resolved 2026-01-13 15:30 UTC

   We observed periods of elevated error rates in starting and completing scans between 15:30 UTC and 18:15 UTC. Fixes have been applied and scans are now behaving normally.

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

Affected: Scans and CI/CD, Managed Scans

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-01-09 17:02 UTC

   We are currently investigating an issue with degraded scan performance in CI and Semgrep Managed Scans.

2. investigating 2026-01-09 18:44 UTC

   We are continuing to investigate the cause of the issue.

3. monitoring 2026-01-09 22:53 UTC

   We've identified and implemented several changes, and we are seeing recovery. We will continue to actively monitor.

4. resolved 2026-01-09 23:27 UTC

   This issue has been resolved. The system is now stable and scans are executing normally.

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

Affected: Scans and CI/CD

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-01-08 10:40 UTC

   We're aware of an issue where CI scans are not completing or taking a long time to do so. You may see scans getting stuck on the "Uploading scan results" or "Finalizing scan" stages.

2. identified 2026-01-08 11:18 UTC

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

3. monitoring 2026-01-08 12:11 UTC

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

4. resolved 2026-01-08 13:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Semgrep'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. monitoring 2025-12-23 21:39 UTC

   Semgrep's Wiz integration will be unavailable until January 5. Contact support with any urgent questions.

2. monitoring 2026-01-06 18:12 UTC

   Semgrep's Wiz integration remains unavailable at this time. We are targeting January 9 to re-activate the integration. Contact support with any urgent questions.

3. monitoring 2026-01-09 21:30 UTC

   Semgrep's Wiz integration remains unavailable. However, we are in the final testing and release stages and are targeting January 14 to re-activate the integration. Contact support with any urgent questions.

4. resolved 2026-01-14 06:16 UTC

   This incident has been resolved.

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

Affected: Scans and CI/CD

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 2025-12-19 20:43 UTC

   We've observed an increase in error rate when starting scans and we are investigating the cause.

2. monitoring 2025-12-19 21:04 UTC

   We have rolled out a fix and are seeing signs of recovery. We are continuing to monitor closely.

3. resolved 2025-12-19 21:11 UTC

   This issue has been resolved and scans are now starting normally.

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