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.

Semgrep AppSec Platform users with read-only access cannot see their projects

Mar <var data-var='date'>30</var>, <var data-var='time'>23:55</var> UTC Resolved - All data has backfilled and the system is healthy. Mar <var data-var='date'>27</var>, <var data-var='time'>18:20</var> UTC Update - Data backfill continues to progress, and realtime sync remains healthy. Mar <var data-var='date'>26</var>, <var data-var='time'>23:43</var> UTC Update - Data backfill is now complete for most organizations. We are continuing to monitor the final syncs. Mar <var data-var='date'>26</var>, <var data-var='time'>19:38</var> UTC Update - Realtime sync is now healthy. We are continuing to monitor the data backfill. Mar <var data-var='date'>26</var>, <var data-var='time'>15:27</var> UTC Monitoring - 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.

Findings data out of date for organizations using combined Code/AI view

Mar <var data-var='date'>17</var>, <var data-var='time'>22:37</var> UTC Resolved - This issue has been resolved and scans are behaving normally. Mar <var data-var='date'>17</var>, <var data-var='time'>22:21</var> UTC Monitoring - We have released a fix for this issue and are monitoring the results. Mar <var data-var='date'>17</var>, <var data-var='time'>21:22</var> UTC Investigating - We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.

Elevated error rates in Managed Scans

Mar <var data-var='date'>13</var>, <var data-var='time'>19:48</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>13</var>, <var data-var='time'>19:25</var> UTC Monitoring - 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 repository was affected, you can push a new commit to your PR/MR to trigger a new scan. The new scan will run with increased resources. Mar <var data-var='date'>13</var>, <var data-var='time'>18:55</var> UTC Identified - We have identified the cause of the problem and are working on a fix. Mar <var data-var='date'>13</var>, <var data-var='time'>18:15</var> UTC Update - 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). We will share updates as information becomes available. Mar <var data-var='date'>13</var>, <var data-var='time'>18:10</var> UTC Investigating - Errors started Mar 12 at 21:30 PST and have been increasing since then.

Elevated errors on managed diff scans

Mar <var data-var='date'> 6</var>, <var data-var='time'>16:18</var> UTC Resolved - This issue has been resolved, and scans have returned to normal operation. Mar <var data-var='date'> 6</var>, <var data-var='time'>15:47</var> UTC Monitoring - 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. Mar <var data-var='date'> 6</var>, <var data-var='time'>12:24</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'> 6</var>, <var data-var='time'>12:04</var> UTC Investigating - 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.

Investigating issues with pull request checks and repository scans

Mar <var data-var='date'> 3</var>, <var data-var='time'>20:05</var> UTC Resolved - This issue has been resolved. Login and other platform functions are behaving normally. Mar <var data-var='date'> 3</var>, <var data-var='time'>19:42</var> UTC Monitoring - We have released a fix and the login page is now loading. We are monitoring for system stability. Mar <var data-var='date'> 3</var>, <var data-var='time'>19:28</var> UTC Identified - We have identified the source of the issue and are working on a fix. Mar <var data-var='date'> 3</var>, <var data-var='time'>19:23</var> UTC Investigating - We are currently investigating a crash on the login page for Semgrep AppSec Platform. Existing sessions in the platform are still operative.

Semgrep AppSec Platform login page is not working

Feb <var data-var='date'>24</var>, <var data-var='time'>23:20</var> UTC Resolved - This issue has been resolved, and the system is now processing scans normally. Feb <var data-var='date'>24</var>, <var data-var='time'>23:13</var> UTC Update - We have rolled out a fix and are seeing scan results processing resume. We are monitoring the system for stability. Feb <var data-var='date'>24</var>, <var data-var='time'>22:38</var> UTC Investigating - 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.

Newly reported scan results not being processed (CI and Semgrep Managed Scans)

Feb <var data-var='date'>23</var>, <var data-var='time'>20:13</var> UTC Resolved - This issue has been resolved, and the services are currently behaving normally. Feb <var data-var='date'>23</var>, <var data-var='time'>19:50</var> UTC Monitoring - Scan start and completion performance is now normal and we are continuing to monitor. Feb <var data-var='date'>23</var>, <var data-var='time'>18:09</var> UTC Identified - 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.

Is Semgrep down?

Semgrep status is UP

Lastest published events

Scan failures with exit code 7 due to invalid rule

Delays in scan processing

Degraded scan performance in CI and Semgrep Managed Scans

Semgrep Services, Components and Regions

Recent Semgrep events

Scan failures with exit code 7 due to invalid rule

Delays in scan processing

Degraded scan performance in CI and Semgrep Managed Scans

Database Maintenance for all tenants

Logins are failing for users via GitHub auth

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

Get your FREE account now,
5 monitors included!

Is Semgrep down?

Semgrep status is UP

Lastest published events

Scan failures with exit code 7 due to invalid rule

Delays in scan processing

Degraded scan performance in CI and Semgrep Managed Scans

Semgrep Services, Components and Regions

Recent Semgrep events

Scan failures with exit code 7 due to invalid rule

Delays in scan processing

Degraded scan performance in CI and Semgrep Managed Scans

Database Maintenance for all tenants

Logins are failing for users via GitHub auth

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

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!