Semgrep Outage History
Uptime record, past incidents, and downtime history for Semgrep.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 68% | 25 | 8 |
| April 2026 | 73.3% | 30 | 8 |
| March 2026 | 58.1% | 31 | 13 |
| February 2026 | 80% | 5 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Logins are failing for users via GitHub auth
Started: May 20, 5:34 PM
monitoring
We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability.
May 20, 5:49 PM
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.
May 20, 5:34 PM
Managed Scans: full project scans being associated with HEAD instead of the default branch name
Started: May 20, 1:18 AM
monitoring
We have deployed the fix and are monitoring.
May 20, 2:47 AM
identified
We have identified the issue and are working on a resolution.
May 20, 2:08 AM
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.
May 20, 1:18 AM
Scheduling delays for Semgrep Managed Scanning (SMS)
Started: May 19, 6:54 PM
monitoring
The scan success rate is recovering. We are continuing to monitor the system.
May 19, 9:26 PM
identified
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 19, 9:07 PM
identified
We have identified a likely cause of this incident. We are currently rolling out a change to address it.
May 19, 7:47 PM
investigating
We are continuing to investigate the issue. We will post updates when further information is available.
May 19, 7:21 PM
investigating
We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.
May 19, 6:54 PM
Slow performance and intermittent errors in the Semgrep AppSec Platform
Started: May 12, 5:27 PM
investigating
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 13, 12:01 AM
investigating
Latency and errors have increased in the last hour. We are continuing to investigate the performance issues and apologize for the impact.
May 12, 10:36 PM
investigating
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 12, 8:08 PM
investigating
The performance of the platform is beginning to return to baseline. We are continuing to investigate what caused the issue.
May 12, 5:51 PM
investigating
We are currently investigating a performance issue with the Semgrep AppSec Platform that started around 16:00 UTC (9:00 AM Pacific).
May 12, 5:27 PM
April 2026
A small subset of users are unable to login
Started: Apr 28, 6:16 PM
identified
The issue has been identified and a fix is being implemented.
Apr 28, 6:16 PM
Scans failing to start
Started: Apr 22, 6:14 PM
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.
Apr 22, 6:14 PM
Login and scans are failing for some users
Started: Apr 20, 8:37 PM
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 20, 9:56 PM
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.
Apr 20, 8:37 PM
Delays for Managed scans fail-open process
Started: Apr 14, 12:02 AM
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 14, 12:46 AM
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.
Apr 14, 12:02 AM
Teams configuration is intermittently not loading and logins slow for some users
Started: Apr 13, 5:08 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 13, 5:32 PM
identified
The issue has been identified and a fix is being implemented.
Apr 13, 5:08 PM
Supply chain dependency processing issues
Started: Apr 8, 7:35 PM
monitoring
We've released a fix and are seeing errors start to resolve.
Apr 8, 8:20 PM
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 8, 8:03 PM
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.
Apr 8, 7:35 PM
March 2026
Semgrep AppSec Platform users with read-only access cannot see their projects
Started: Mar 31, 5:14 PM
monitoring
We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm.
Mar 31, 7:03 PM
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.
Mar 31, 5:14 PM
Findings data out of date for organizations using combined Code/AI view
Started: Mar 26, 3:27 PM
monitoring
Data backfill continues to progress, and realtime sync remains healthy.
Mar 27, 6:20 PM
monitoring
Data backfill is now complete for most organizations. We are continuing to monitor the final syncs.
Mar 26, 11:43 PM
monitoring
Realtime sync is now healthy. We are continuing to monitor the data backfill.
Mar 26, 7:38 PM
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.
Mar 26, 3:27 PM
Elevated error rates in Managed Scans
Started: Mar 17, 9:22 PM
investigating
We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.
Mar 17, 9:22 PM
Elevated errors on managed diff scans
Started: Mar 13, 6:10 PM
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 13, 7:25 PM
identified
We have identified the cause of the problem and are working on a fix.
Mar 13, 6:55 PM
investigating
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 13, 6:15 PM
investigating
Errors started Mar 12 at 21:30 PST and have been increasing since then.
Mar 13, 6:10 PM