Oct <var data-var='date'> 5</var>, <var data-var='time'>16:14</var> UTC Resolved - We have rolled out a fix, and logins are now working as expected. This incident has been resolved. Oct <var data-var='date'> 5</var>, <var data-var='time'>16:00</var> UTC Identified - 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.

Intermittent login failures on semgrep.dev

Sep <var data-var='date'>30</var>, <var data-var='time'>18:23</var> UTC Resolved - Monitoring indicates the platform continues to be stable, and this issue has been resolved. Sep <var data-var='date'>30</var>, <var data-var='time'>14:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>30</var>, <var data-var='time'>14:26</var> UTC Identified - Issue has been identified and a fix is rolling out Sep <var data-var='date'>30</var>, <var data-var='time'>14:26</var> UTC Update - We are continuing to investigate this issue. Sep <var data-var='date'>30</var>, <var data-var='time'>14:07</var> UTC Investigating - We are currently investigating the source of these issues

Backend 503 timeout on all pages

Sep <var data-var='date'>22</var>, <var data-var='time'>19:37</var> UTC Resolved - Resolved. All products were confirmed to be operational, but Engineering will remain on standby to respond to customer reported issues. Sep <var data-var='date'>22</var>, <var data-var='time'>19:27</var> UTC Monitoring - 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. Sep <var data-var='date'>22</var>, <var data-var='time'>19:24</var> UTC Identified - 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.

Interruption to Scans and Accessing Web App

Sep <var data-var='date'>14</var>, <var data-var='time'>19:33</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>14</var>, <var data-var='time'>18:23</var> UTC Investigating - We are currently investigating the issue.

Results processing is partially degraded

Sep <var data-var='date'>10</var>, <var data-var='time'>16:36</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>10</var>, <var data-var='time'>16:21</var> UTC Monitoring - We believe we have recovered, we are monitoring for additional impact. Sep <var data-var='date'>10</var>, <var data-var='time'>16:17</var> UTC Investigating - We are investigating an increase in traffic causing platform wide issues. The UI, scanning, and API may be affected.

general platform instability

Sep <var data-var='date'> 4</var>, <var data-var='time'>23:38</var> UTC Resolved - This issue has been resolved. The Pro Engine can be installed and used normally after installing Semgrep 1.176.1 via PyPI. Sep <var data-var='date'> 4</var>, <var data-var='time'>23:13</var> UTC Investigating - 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.

Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine

Sep <var data-var='date'> 3</var>, <var data-var='time'>22:45</var> UTC Resolved - Metrics show full recovery of all Semgrep products. Our engineering team will continue monitoring until the final update from AWS. Sep <var data-var='date'> 3</var>, <var data-var='time'>22:30</var> UTC Monitoring - Early signs of recovery for all Semgrep products. We are actively monitoring AWS updates on the regional, multi-service outage. Sep <var data-var='date'> 3</var>, <var data-var='time'>21:55</var> UTC Update - AWS STS outage in us-west-2 is affecting our system. We are investigating mitigations. Sep <var data-var='date'> 3</var>, <var data-var='time'>21:35</var> UTC Investigating - We are currently investigating this issue.

SMS Scans Degraded

Sep <var data-var='date'> 3</var>, <var data-var='time'>00:10</var> UTC Resolved - Dynamic maven & gradle scans are now operating as normal. Sep <var data-var='date'> 2</var>, <var data-var='time'>16:25</var> UTC Monitoring - The third party registry's rate limits have been lifted, and impact to scans appears mitigated. Sep <var data-var='date'> 1</var>, <var data-var='time'>22:55</var> UTC Update - 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 out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time Sep <var data-var='date'> 1</var>, <var data-var='time'>22:50</var> UTC Identified - 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 are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time.

Dynamic Maven & Gradle dependency resolution impaired

Aug <var data-var='date'>25</var>, <var data-var='time'>22:01</var> UTC Resolved - This issue has been fully resolved with a successful release. Aug <var data-var='date'>25</var>, <var data-var='time'>19:28</var> UTC Monitoring - The release has been rolled back and the platform is now stable. Aug <var data-var='date'>25</var>, <var data-var='time'>19:21</var> UTC Identified - A bad release is causing widespread failures in the Semgrep AppSec Platform.

Widespread errors on Semgrep AppSec Platform

Aug <var data-var='date'>13</var>, <var data-var='time'>11:30</var> UTC Resolved - 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.

Semgrep outage between 2026-08-13 23:43 UTC and 23:52 UTC

Aug <var data-var='date'>12</var>, <var data-var='time'>21:03</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>12</var>, <var data-var='time'>20:23</var> UTC Monitoring - We have rolled out a fix, and scans are now working as expected. We are closely monitoring to ensure continued stability. Aug <var data-var='date'>12</var>, <var data-var='time'>19:33</var> UTC Identified - We've identified the root cause of the issue and are currently working on a fix. Aug <var data-var='date'>12</var>, <var data-var='time'>18:16</var> UTC Investigating - We are currently investigating this issue.

Lockfileless scans failing for certain deployments

Jul <var data-var='date'>23</var>, <var data-var='time'>21:36</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>21:30</var> UTC Monitoring - A fix has been deployed. We will continue to monitor our systems to ensure that the issue has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>21:10</var> UTC Identified - We have identified the issue and are actively working on a fix. Jul <var data-var='date'>23</var>, <var data-var='time'>21:07</var> UTC Investigating - We are currently investigating this issue.

Fragment scanner unavailable to some users

Jul <var data-var='date'>20</var>, <var data-var='time'>22:58</var> UTC Resolved - This issue has been resolved, and findings data is now displaying normally. Jul <var data-var='date'>20</var>, <var data-var='time'>21:58</var> UTC Update - Backfill is continuing and lag has reduced to approximately 1 hour behind realtime. We continue to monitor to ensure progress. Jul <var data-var='date'>20</var>, <var data-var='time'>20:07</var> UTC Monitoring - 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.

Findings data display lagging behind realtime

Jul <var data-var='date'>16</var>, <var data-var='time'>12:46</var> UTC Resolved - This incident has been resolved by the third party vendor Jul <var data-var='date'>16</var>, <var data-var='time'>09:38</var> UTC Investigating - 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

Custom SSO Login Issues

Jul <var data-var='date'>16</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'>16</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>14</var>, <var data-var='time'>20:58</var> UTC Scheduled - For users of Semgrep AppSec Platform on the primary tenant, we will be applying important database updates during this time. We do not anticipate any significant impact, but there may be transient connection errors.

Semgrep AppSec Platform: Scheduled database maintenance (primary tenant)

Jul <var data-var='date'>15</var>, <var data-var='time'>20:14</var> UTC Resolved - The fix has been released and this issue is resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>18:29</var> UTC Identified - 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. Jul <var data-var='date'>15</var>, <var data-var='time'>18:08</var> UTC Investigating - We've observed that when trying to add a new memory, the Memories page crashes, and we are investigating the issue.

Adding a memory crashes the Memories page in the platform

Jun <var data-var='date'>25</var>, <var data-var='time'>22:27</var> UTC Resolved - This issue has been resolved. Scans are now running normally. Jun <var data-var='date'>25</var>, <var data-var='time'>22:14</var> UTC Monitoring - 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. Jun <var data-var='date'>25</var>, <var data-var='time'>21:32</var> UTC Identified - 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 policies.

Scan failures with exit code 7 due to invalid rule

Jun <var data-var='date'>22</var>, <var data-var='time'>22:51</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>22</var>, <var data-var='time'>21:55</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>22</var>, <var data-var='time'>21:14</var> UTC Investigating - We are currently investigating this issue. Jun <var data-var='date'>22</var>, <var data-var='time'>19:34</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>22</var>, <var data-var='time'>18:52</var> UTC Investigating - We are currently investigating this issue.

Delays in scan processing

Jun <var data-var='date'> 8</var>, <var data-var='time'>17:18</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 8</var>, <var data-var='time'>17:17</var> UTC Update - We are continuing to monitor for any further issues. Jun <var data-var='date'> 8</var>, <var data-var='time'>16:59</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 8</var>, <var data-var='time'>16:29</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'> 8</var>, <var data-var='time'>15:30</var> UTC Investigating - We are currently investigating an issue causing degraded scan performance in CI and Semgrep Managed Scans, and are actively working to resolve it.

Degraded scan performance in CI and Semgrep Managed Scans

May <var data-var='date'>30</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>30</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>27</var>, <var data-var='time'>14:38</var> UTC Scheduled - During this window, each customer's Semgrep database will experience a brief interruption: - Single tenant customers: ~30-90 seconds of unavailability - All customers (multi-tenant): ~1-2 minutes of unavailability During this brief outage, the Semgrep web app and API may return connection errors. API clients and CI integrations with normal retry/reconnect logic will resume automatically - no action required from customers.

Database Maintenance for all tenants

May <var data-var='date'>20</var>, <var data-var='time'>18:18</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>18:17</var> UTC Update - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>17:49</var> UTC Monitoring - We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability. May <var data-var='date'>20</var>, <var data-var='time'>17:34</var> UTC Identified - 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.

Logins are failing for users via GitHub auth

May <var data-var='date'>20</var>, <var data-var='time'>02:52</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>02:47</var> UTC Monitoring - We have deployed the fix and are monitoring. May <var data-var='date'>20</var>, <var data-var='time'>02:08</var> UTC Identified - We have identified the issue and are working on a resolution. May <var data-var='date'>20</var>, <var data-var='time'>01:18</var> UTC Investigating - 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 not being closed as expected.

Managed Scans: full project scans being associated with HEAD instead of the default branch name

May <var data-var='date'>19</var>, <var data-var='time'>21:33</var> UTC Resolved - This incident has been resolved. We are continuing to monitor the system. May <var data-var='date'>19</var>, <var data-var='time'>21:26</var> UTC Monitoring - The scan success rate is recovering. We are continuing to monitor the system. May <var data-var='date'>19</var>, <var data-var='time'>21:07</var> UTC Update - 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. May <var data-var='date'>19</var>, <var data-var='time'>19:47</var> UTC Identified - We have identified a likely cause of this incident. We are currently rolling out a change to address it. May <var data-var='date'>19</var>, <var data-var='time'>19:21</var> UTC Update - We are continuing to investigate the issue. We will post updates when further information is available. May <var data-var='date'>19</var>, <var data-var='time'>18:54</var> UTC Investigating - We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.

Scheduling delays for Semgrep Managed Scanning (SMS)

May <var data-var='date'>13</var>, <var data-var='time'>16:24</var> UTC Resolved - This issue has been resolved. We determined that the performance degradation had multiple contributing causes and will be working to address those issues. May <var data-var='date'>13</var>, <var data-var='time'>00:01</var> UTC Update - 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. May <var data-var='date'>12</var>, <var data-var='time'>22:36</var> UTC Update - Latency and errors have increased in the last hour. We are continuing to investigate the performance issues and apologize for the impact. May <var data-var='date'>12</var>, <var data-var='time'>20:08</var> UTC Update - 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. May <var data-var='date'>12</var>, <var data-var='time'>17:51</var> UTC Update - The performance of the platform is beginning to return to baseline. We are continuing to investigate what caused the issue. May <var data-var='date'>12</var>, <var data-var='time'>17:27</var> UTC Investigating - We are currently investigating a performance issue with the Semgrep AppSec Platform that started around 16:00 UTC (9:00 AM Pacific).

Slow performance and intermittent errors in the Semgrep AppSec Platform

Apr <var data-var='date'>30</var>, <var data-var='time'>22:00</var> UTC Resolved - Between 21:48 - 22:00 UTC some managed scans experienced additional latency. The root cause has been resolved.

Is Semgrep down?

Semgrep status is UP

Lastest published events

Intermittent login failures on semgrep.dev

Backend 503 timeout on all pages

Interruption to Scans and Accessing Web App

Semgrep Services, Components and Regions

Recent Semgrep events

Intermittent login failures on semgrep.dev

Backend 503 timeout on all pages

Interruption to Scans and Accessing Web App

Results processing is partially degraded

general platform instability

Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine