Looking for an update now? Check the current status, or follow Semgrep for future changes.
75.9%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0
We have released a fix for this issue and are monitoring to confirm resolution.
identified
We have identified the issue and are working on a fix.
investigating
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.
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.
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.
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.
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.
The release has been rolled back and the platform is now stable.
identified
A bad release is causing widespread failures in the Semgrep AppSec Platform.
Legacy Incident Archive
22 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Scheduling delays for Semgrep Managed Scanning (SMS)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The scan success rate is recovering. We are continuing to monitor the system.
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.
identified
We have identified a likely cause of this incident. We are currently rolling out a change to address it.
investigating
We are continuing to investigate the issue. We will post updates when further information is available.
investigating
We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.
Slow performance and intermittent errors in the Semgrep AppSec Platform
minorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
Latency and errors have increased in the last hour. We are continuing to investigate the performance issues and apologize for the impact.
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.
investigating
The performance of the platform is beginning to return to baseline. We are continuing to investigate what caused the issue.
investigating
We are currently investigating a performance issue with the Semgrep AppSec Platform that started around 16:00 UTC (9:00 AM Pacific).
April 2026
A small subset of users are unable to login
Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
Scans failing to start
criticalSource not attested
Last archived state: resolved
View archived record details
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.
Login and scans are failing for some users
majorSource not attested
Last archived state: resolved
View archived record details
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.
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.
Delays for Managed scans fail-open process
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
Teams configuration is intermittently not loading and logins slow for some users
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
Supply chain dependency processing issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've released a fix and are seeing errors start to resolve.
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.
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.
March 2026
Semgrep AppSec Platform users with read-only access cannot see their projects
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm.
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.
Findings data out of date for organizations using combined Code/AI view
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Data backfill continues to progress, and realtime sync remains healthy.
monitoring
Data backfill is now complete for most organizations. We are continuing to monitor the final syncs.
monitoring
Realtime sync is now healthy. We are continuing to monitor the data backfill.
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.
