Is Semgrep down?
Last checked just nowNo incidents right now.
Semgrep is operational right now. Last checked just now; the most recent incident resolved 5d ago.
Real-time Semgrep status, recent outages, and incident history — pulled directly from Semgrep's official status page at https://status.semgrep.dev/?utm_source=embed every 5 minutes. Pingoru tracks 16 Semgrep services and has captured 19 incidents in the last 90 days (97.46% uptime). Get email, Slack, Discord, or webhook alerts the moment Semgrep reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Scans and CI/CDManaged Scans
Timeline · 5 updates
- investigating · Jun 08, 2026, 04:28 PM UTC
We are currently investigating an issue causing degraded scan performance in CI and Semgrep Managed Scans, and are actively working to resolve it.
- identified · Jun 08, 2026, 04:29 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jun 08, 2026, 04:59 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring · Jun 08, 2026, 05:17 PM UTC
We are continuing to monitor for any further issues.
- resolved · Jun 08, 2026, 05:18 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Login/SSO
Timeline · 4 updates
- identified · May 20, 2026, 05:34 PM UTC
We are currently observing login issues using GitHub auth. Our team has identified the issue and is currently working on a fix. SSO logins are working as expected and are not impacted.
- monitoring · May 20, 2026, 05:49 PM UTC
We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability.
- monitoring · May 20, 2026, 06:17 PM UTC
This incident has been resolved.
- resolved · May 20, 2026, 06:18 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Managed Scans
Timeline · 4 updates
- investigating · May 20, 2026, 01:18 AM UTC
We are currently investigating an issue where full project scans in Managed Scans are being associated with HEAD rather than the name of the default branch. This issue started around 16:00 UTC on May 19 and may result in unexpected new findings notifications, and some findings not being closed as expected.
- identified · May 20, 2026, 02:08 AM UTC
We have identified the issue and are working on a resolution.
- monitoring · May 20, 2026, 02:47 AM UTC
We have deployed the fix and are monitoring.
- resolved · May 20, 2026, 02:52 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Managed Scans
Timeline · 6 updates
- investigating · May 19, 2026, 06:54 PM UTC
We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.
- investigating · May 19, 2026, 07:21 PM UTC
We are continuing to investigate the issue. We will post updates when further information is available.
- identified · May 19, 2026, 07:47 PM UTC
We have identified a likely cause of this incident. We are currently rolling out a change to address it.
- identified · May 19, 2026, 09:07 PM UTC
Since the beginning of the incident, a portion of SMS scans have failed to execute. We have deployed a change to the system. We are seeing scheduling queues begin to recover, and we're continuing to monitor the situation.
- monitoring · May 19, 2026, 09:26 PM UTC
The scan success rate is recovering. We are continuing to monitor the system.
- resolved · May 19, 2026, 09:33 PM UTC
This incident has been resolved. We are continuing to monitor the system.
Latest: This incident has been resolved. We are continuing to monitor the system.
-
- Login/SSODashboardAPI
Timeline · 6 updates
- investigating · May 12, 2026, 05:27 PM UTC
We are currently investigating a performance issue with the Semgrep AppSec Platform that started around 16:00 UTC (9:00 AM Pacific).
- investigating · May 12, 2026, 05:51 PM UTC
The performance of the platform is beginning to return to baseline. We are continuing to investigate what caused the issue.
- investigating · May 12, 2026, 08:08 PM UTC
We are continuing to investigate the issue. While overall performance has remained relatively stable since 10:30 Pacific, some reporting metrics and issue details may lag behind realtime.
- investigating · May 12, 2026, 10:36 PM UTC
Latency and errors have increased in the last hour. We are continuing to investigate the performance issues and apologize for the impact.
- investigating · May 13, 2026, 12:01 AM UTC
We have applied mitigations but are continuing to investigate the root cause of the issue. Platform performance may still lag at times and some reporting and issue status data may be stale.
- resolved · May 13, 2026, 04:24 PM UTC
This issue has been resolved. We determined that the performance degradation had multiple contributing causes and will be working to address those issues.
Latest: This issue has been resolved. We determined that the performance degradation had multiple contributing causes and will be working to address those issues.
-
See the full Semgrep outage history
12 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Semgrep outage history →Or sign up free to get alerts when Semgrep breaks · 10 free monitors · No credit card
- Started Jun 08, 2026, 03:30 PM UTC · Resolved Jun 08, 2026, 05:18 PM UTC · 1h 47m
- Started May 20, 2026, 05:34 PM UTC · Resolved May 20, 2026, 06:18 PM UTC · 44m
- Managed Scans: full project scans being associated with HEAD instead of the default branch name ResolvedStarted May 20, 2026, 01:18 AM UTC · Resolved May 20, 2026, 02:52 AM UTC · 1h 33m
- Started May 19, 2026, 06:54 PM UTC · Resolved May 19, 2026, 09:33 PM UTC · 2h 38m
- Started May 12, 2026, 05:27 PM UTC · Resolved May 13, 2026, 04:24 PM UTC · 22h 56m
- Degraded Scan Performance ResolvedStarted Apr 30, 2026, 10:29 PM UTC · Resolved Apr 30, 2026, 10:00 PM UTC · —
- Started Apr 28, 2026, 06:16 PM UTC · Resolved Apr 28, 2026, 07:13 PM UTC · 57m
- Started Apr 24, 2026, 04:37 PM UTC · Resolved Apr 24, 2026, 12:30 PM UTC · —