New Multi-region uptime checks and custom-domain status pages

Semgrep Outage History

Daily provider-status observations and published incident history for Semgrep.

Degraded performance

Semgrep is reporting degraded performance. Verified . Official provider source.

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

Jul 24Oct 21

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 23 Today
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
minor Observed active window 2h 49m

View incident details and source

Started:

Scans and CI/CD
monitoring
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.
Observed lag in async tasks
minor Observed active window 1h 21m

View incident details and source

Started:

Dashboard API
monitoring
We have applied a fix and are seeing lag decrease significantly. We will continue to monitor for full recovery.
investigating
We are currently investigating an issue where some asynchronous tasks on the platform are lagging.
Intermittent login failures on semgrep.dev
major Observed active window 14m

View incident details and source

Started:

Login/SSO
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.
September 2026
Interruption to Scans and Accessing Web App
major Observed active window 15m

View incident details and source

Started:

Dashboard API Scans and CI/CD Managed Scans
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.
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.
Results processing is partially degraded
minor Observed active window 1h 11m

View incident details and source

Started:

Scans and CI/CD Managed Scans
investigating
We are currently investigating the issue.
Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine
major Observed active window 26m

View incident details and source

Started:

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.
SMS Scans Degraded
major Observed active window 1h 9m

View incident details and source

Started:

Managed Scans
monitoring
Early signs of recovery for all Semgrep products. We are actively monitoring AWS updates on the regional, multi-service outage.
investigating
AWS STS outage in us-west-2 is affecting our system. We are investigating mitigations.
investigating
We are currently investigating this issue.
August 2026
Widespread errors on Semgrep AppSec Platform
critical Observed active window 2h 43m

View incident details and source

Started:

Dashboard Scans and CI/CD
monitoring
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.

March 2026
Elevated error rates in Managed Scans
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.
Elevated errors on managed diff scans
major Source not attested
Last archived state: resolved
View archived record details
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.
identified
We have identified the cause of the problem and are working on a fix.
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.
investigating
Errors started Mar 12 at 21:30 PST and have been increasing since then.
Get alerts for Semgrep Subscribe to the provider incident feed Browse all services