Semgrep Status
Incident overview
Total incidents
17
Active now
0
Resolved
17
Avg. resolution
2h 58m
Recent incidents
View all →Workflows Performance Degraded
Delayed Scans
Scans are degraded or delayed
Delay in findings being updated
Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0
Observed lag in async tasks
Intermittent login failures on semgrep.dev
Backend 503 timeout on all pages
Interruption to Scans and Accessing Web App
Results processing is partially degraded
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 100.00%. 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 17 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 2h 58m. 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.