Semgrep logo

Is Semgrep Down?

SecurityLive status, outages, and incident history

No. Semgrep is up right now.

Every monitored Semgrep system is operational as of August 29, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s
How we know: the official Semgrep status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Semgrep Component Status

The main Semgrep systems on this page. All 16 are operational right now.

16operational
AWS » AWS ec2-us-west-2
Operational
AWS » AWS ecr-us-west-2
Operational
AWS » AWS eks-us-west-2
Operational

13 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AWS » AWS firehose-us-west-2, GitHub » GitHub API Requests, GitHub » GitHub GitHub Actions, GitHub » GitHub Pull Requests, GitHub » GitHub Visit www.githubstatus.com for more information, semgrep.dev » API, semgrep.dev » Dashboard, semgrep.dev » Login/SSO, semgrep.dev » Managed Scans, semgrep.dev » Registry, semgrep.dev » Scans and CI/CD, Slack » Slack Apps/Integrations, and 1 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Semgrep Outages & Incidents

Incident history from the official Semgrep status page, including resolution updates.

Widespread errors on Semgrep AppSec PlatformResolved Aug 25, 2026 · 2h 40mResolved

This issue has been fully resolved with a successful release. --- [2026-08-25T19:28:13.864Z] (monitoring) The release has been rolled back and the platform is now stable. --- [2026-08-25T19:21:15.063Z] (identified) A bad release is causing widespread failures in the Semgrep AppSec Platform.

Semgrep outage between 2026-08-13 23:43 UTC and 23:52 UTCResolved Aug 14, 2026 · -792 minResolved

Semgrep experienced an outage affecting login, the API, and scans from 2026-08-13 23:43 UTC to 23:52 UTC. The incident has been resolved.

Lockfileless scans failing for certain deploymentsResolved Aug 12, 2026 · 2h 46mResolved

This incident has been resolved. --- [2026-08-12T20:23:25.053Z] (monitoring) We have rolled out a fix, and scans are now working as expected. We are closely monitoring to ensure continued stability. --- [2026-08-12T19:33:51.434Z] (identified) We've identified the root cause of the issue and are currently working on a fix. --- [2026-08-12T18:16:54.082Z] (investigating) We are currently investigating this issue.

Semgrep Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Semgrep incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
May 3197.38% average · 18 days with incidentsAug 29

Going further back: Semgrep uptime by month and every recorded Semgrep outage.

Live Semgrep Outage Reports

Problems reported by engineers using Semgrep. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Semgrep problems reported yet.

Something wrong with Semgrep on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Semgrep

Semgrep is a lightweight static analysis tool for finding bugs and enforcing code standards, supporting over 30 programming languages. Semgrep outages interrupt code analysis pipelines. Track Semgrep status and outages here.

Over the past 30 days, PulsAPI has measured Semgrep uptime at 99.83%. Response times, incident history, and SLA tracking for Semgrep are available on the PulsAPI dashboard.

Semgrep Status FAQ

Is Semgrep down right now?

PulsAPI checks Semgrep every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Semgrep status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Semgrep is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Semgrep recovers.

How do I check Semgrep uptime history?

PulsAPI tracks Semgrep uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.83%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Semgrep.

How fast does PulsAPI detect Semgrep outages?

PulsAPI polls the official Semgrep status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Semgrep components?

Yes. PulsAPI monitors 16 individual Semgrep components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Semgrep goes down?

Yes. Create a PulsAPI account and subscribe to Semgrep. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Semgrep status changes.

How do I report an issue with Semgrep to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Semgrep problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Semgrep?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor Semgrep alongside up to 24 other services at pulsapi.com/signup.

Track Semgrep with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when Semgrep status changes.

Start free trial