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 October 13, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Semgrep breaks

Semgrep is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Semgrep status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), 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.

See all of them free

Component statuses may change independently during partial outages.

Recent Semgrep Outages & Incidents

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

Intermittent login failures on semgrep.devResolved Oct 5, 2026 · 14 minResolved

We have rolled out a fix, and logins are now working as expected. This incident has been resolved. --- [2026-10-05T16:00:13.390Z] (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.

Backend 503 timeout on all pagesResolved Sep 30, 2026 · 4h 16mResolved

Monitoring indicates the platform continues to be stable, and this issue has been resolved. --- [2026-09-30T14:36:18.173Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-30T14:26:57.621Z] (identified) Issue has been identified and a fix is rolling out --- [2026-09-30T14:26:01.823Z] (investigating) We are continuing to investigate this issue. --- [2026-09-30T14:07:02.768Z] (investigating) We are currently investigating the source of these issues

Interruption to Scans and Accessing Web AppResolved Sep 22, 2026 · 12 minResolved

Resolved. All products were confirmed to be operational, but Engineering will remain on standby to respond to customer reported issues. --- [2026-09-22T19:27:28.217Z] (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. --- [2026-09-22T19:24:33.451Z] (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.

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
Jul 1599.99% average · 22 days with incidentsOct 13

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.98%. Response times, incident history, and SLA tracking for Semgrep are available on the PulsAPI dashboard.

Semgrep Status FAQ

Is Semgrep down right now?

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. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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.98%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Semgrep changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Semgrep outages?

PulsAPI reads the official Semgrep status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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 free account and subscribe to Semgrep: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Semgrep plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Semgrep with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services