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.

Degraded Scan Performance

Apr <var data-var='date'>28</var>, <var data-var='time'>19:13</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>28</var>, <var data-var='time'>19:11</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>28</var>, <var data-var='time'>18:16</var> UTC Identified - The issue has been identified and a fix is being implemented.

A small subset of users are unable to login

Apr <var data-var='date'>24</var>, <var data-var='time'>12:30</var> UTC Resolved - From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.

Failure to start scans from 14:35 to 14:52 UTC

Apr <var data-var='date'>23</var>, <var data-var='time'>16:00</var> UTC Resolved - 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 now stable.

Failures running diff-aware scans for GitHub.com customers

Apr <var data-var='date'>22</var>, <var data-var='time'>18:35</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>22</var>, <var data-var='time'>18:14</var> UTC Monitoring - 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 pending, you can push a new commit to cause the scan to retry.

Scans failing to start

Apr <var data-var='date'>21</var>, <var data-var='time'>00:29</var> UTC Resolved - The problem is resolved and scans and logins are now processing normally. Apr <var data-var='date'>20</var>, <var data-var='time'>21:56</var> UTC Identified - We've identified the cause of the backend issues. Some traffic has resumed but services are still degraded, and we're continuing to remediate. Apr <var data-var='date'>20</var>, <var data-var='time'>20:37</var> UTC Investigating - 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.

Login and scans are failing for some users

Apr <var data-var='date'>14</var>, <var data-var='time'>17:23</var> UTC Resolved - This issue has been resolved. Fail-open processes for unfinished Managed Scans continue to run normally. Apr <var data-var='date'>14</var>, <var data-var='time'>00:46</var> UTC Monitoring - 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. Apr <var data-var='date'>14</var>, <var data-var='time'>00:02</var> UTC Investigating - 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.

Delays for Managed scans fail-open process

Apr <var data-var='date'>13</var>, <var data-var='time'>18:13</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>13</var>, <var data-var='time'>17:32</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>13</var>, <var data-var='time'>17:08</var> UTC Identified - The issue has been identified and a fix is being implemented.

Teams configuration is intermittently not loading and logins slow for some users

Apr <var data-var='date'> 8</var>, <var data-var='time'>21:10</var> UTC Resolved - This issue has been resolved, and scan processing is completing normally. Apr <var data-var='date'> 8</var>, <var data-var='time'>20:20</var> UTC Monitoring - We've released a fix and are seeing errors start to resolve. Apr <var data-var='date'> 8</var>, <var data-var='time'>20:03</var> UTC Identified - 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. Apr <var data-var='date'> 8</var>, <var data-var='time'>19:35</var> UTC Investigating - 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 impact.

Supply chain dependency processing issues

Mar <var data-var='date'>31</var>, <var data-var='time'>21:36</var> UTC Resolved - This issue has been resolved, and read-only users should be able to view their projects as normal. Mar <var data-var='date'>31</var>, <var data-var='time'>19:03</var> UTC Monitoring - We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm. Mar <var data-var='date'>31</var>, <var data-var='time'>17:14</var> UTC Identified - 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.

Is Semgrep down?

Semgrep status is UP

Lastest published events

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

Lockfileless scans failing for certain deployments

Fragment scanner unavailable to some users

Semgrep Services, Components and Regions

Recent Semgrep events

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

Lockfileless scans failing for certain deployments

Fragment scanner unavailable to some users

Findings data display lagging behind realtime

Custom SSO Login Issues

Semgrep AppSec Platform: Scheduled database maintenance (primary tenant)