Semgrep Status
Incident overview
Total incidents
13
Active now
0
Resolved
13
Avg. resolution
3h 36m
Recent incidents
View all →Results processing is partially degraded
general platform instability
Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine
SMS Scans Degraded
Dynamic Maven & Gradle dependency resolution impaired
Widespread errors on Semgrep AppSec Platform
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
Frequently asked questions
Is Semgrep down right now?
Semgrep is currently operational. DevHelm monitors Semgrep's official status page continuously and updates this page every 5 minutes.
What is Semgrep's current uptime?
Semgrep has a measured 30-day uptime of 99.99%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Semgrep's official status page data.
How many incidents has Semgrep had recently?
Semgrep has experienced 13 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 3h 36m. All incidents are currently resolved.
What components does Semgrep monitor?
DevHelm tracks 16 individual components for Semgrep, including AWS ecr-us-west-2, GitHub GitHub Actions, Login/SSO, Slack Apps/Integrations, Slack Apps/Integrations/APIs, and 11 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Semgrep outages?
You can subscribe to Semgrep's incident feed via Atom/RSS at devhelm.io/status/semgrep/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Semgrep as a dependency in your DevHelm workspace.
About Semgrep status monitoring
This page provides real-time operational status for Semgrep, powered by DevHelm's continuous monitoring infrastructure. We track Semgrep's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Semgrep status data is refreshed every 5 minutes. We currently track 16 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Semgrep in your stack
Get alerted when Semgrep has issues — before your users notice. Set up in 30 seconds.