Semgrep had 60 outages in the last 2 years totaling 717h 38m of downtime — averaging 2.5 incidents per month.
There were 60 Semgrep outages since August 29, 2025 totaling 717h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified intermittent errors occurring on some platform services, and we are investigating.
We have implemented a fix and are monitoring the platform for stability.
This issue has been resolved, and the platform is currently stable.
We observed periods of elevated error rates in starting and completing scans between 15:30 UTC and 18:15 UTC. Fixes have been applied and scans are now behaving normally.
We're aware of an issue where CI scans are not completing or taking a long time to do so. You may see scans getting stuck on the "Uploading scan results" or "Finalizing scan" stages.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Semgrep's Wiz integration will be unavailable until January 5. Contact support with any urgent questions.
Semgrep's Wiz integration remains unavailable at this time. We are targeting January 9 to re-activate the integration. Contact support with any urgent questions.
Semgrep's Wiz integration remains unavailable. However, we are in the final testing and release stages and are targeting January 14 to re-activate the integration. Contact support with any urgent questions.
This incident has been resolved.
We've observed an increase in error rate when starting scans and we are investigating the cause.
We have rolled out a fix and are seeing signs of recovery. We are continuing to monitor closely.
This issue has been resolved and scans are now starting normally.
Between Friday, December 12 at 23:35 UTC and Monday, December 15 at 17:35 UTC, webhook events for new findings were not delivered. Customers who have custom webhooks configured in Semgrep AppSec Platform and created new findings from scans during that time window did not receive webhook events for those findings. The underlying problem has been fixed and normal delivery resumed, but the skipped webhooks will not be retried. We apologize for the disruption. Managed scan logs from the same time period were temporarily not visible in Semgrep AppSec Platform. We have re-processed those logs and they should now be available as of December 16 18:55 UTC.
We are currently investigating an issue with degraded scan performance in Semgrep Managed Scans.
The issue has been identified and a fix is being implemented. Scan performance is recovering.
A fix has been implemented and we are monitoring results. Scan performance has recovered.
Scan performance has successfully recovered. Scans initiated while in the degraded state have been restarted.
We've identified an increase in incomplete scheduled scans (full repo scans) in Managed Scans, and we are investigating.
We've applied a mitigation that has reduced the failure rate, and are continuing to investigate the root cause.
We've released a fix for the issue and are monitoring the results. Scan success rate currently appears normal and steady.
This issue has been resolved, and scans are completing normally.
Managed full scans aren't completing in a subset of Semgrep organizations. We've identified the cause and are rolling out a fix.
We've deployed the fix and we're watching to ensure the problem is resolved.
The issue is no longer affecting most users. We're continuing to monitor the long tail while minimizing further disruption over the US holiday weekend.
This incident has been resolved.
We've seen that some scans are failing with exit code 7, indicating an issue with a rule. We are investigating the cause.
We have released a fix and are now monitoring the results. We are seeing previously affected scans completing successfully.
Most scans are now completing successfully. Some longer-running scans may still exit with code 7. We are continuing to monitor.
This issue has been resolved. No new Managed Scans since the fix have encountered an unexpected exit code 7. If you are not using Managed Scans and encounter an unexpected scan exit code 7, please re-attempt the scan with Semgrep version 1.142.3 or earlier. If you continue to encounter issues, contact Semgrep Support.
We've observed slightly elevated error rates for Managed Scans and are investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified.
The 3rd-party incident has resolved.
Instability issue has resolved. Semgrep app and scans are stable.
This incident has been resolved.
We've observed elevated error rates for Managed Scans, and are currently investigating.
We've rolled back a recent change and the error rate has returned to normal. We are monitoring to ensure stability.
This issue has been resolved, and Managed Scans are running normally.
Dependencies found in Supply Chain scans are currently not being processed and recorded. We've identified the cause and are working on a fix. Scan completion is not affected. Dependencies may be temporarily missing from the Semgrep platform; once the incident is resolved and the project is re-scanned, they will be restored.
Dependency processing has resumed for scans running now. We're continuing to work on a longer-term mitigation.
We've temporarily disabled dependency processing in order to roll out a longer-term fix. New dependencies will not appear in Semgrep during this time. We don't anticipate any impact to scans, and we'll update this page when normal processing resumes.
Dependency processing has resumed and the underlying issue has been resolved.
This incident has been resolved.
We've identified a problem with loading issues in the platform. It is not affecting all users, but some users are not currently able to load issues or projects. We are working on a fix.
We are continuing to work on a fix for this issue.
We've released a fix for this problem, and projects and issues should be loading normally. We are monitoring to ensure system stability.
This problem has been resolved. The app is loading normally.
We have identified an issue with loading the semgrep.dev website due to an outage with an upstream provider. Users will experience 504 Gateway Timeout errors until this provider outage is resolved. The Semgrep AppSec Platform is not impacted, but users that rely on navigating to semgrep.dev in order to log in to the platform will be unable to do so. As a workaround, please navigate directly to `semgrep.dev/login` in the meantime.
This incident has been resolved.
Some Semgrep scans were delayed or failed from approximately 00:35 PDT to 01:25 PDT (07:35 UTC to 08:25 UTC) due to an issue with an upstream provider. Managed Scans and CI scans were both affected.
We've identified an issue that's resulting in slower repository sync, and are working on a fix.
We've rolled out the fix and confirmed that repository sync is no longer delayed.
We're currently investigating an issue where graphs are not displaying on the reporting dashboard page. The rest of the Semgrep platform is functioning normally. We're working on a fix and will provide updates as we make progress.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Check updates to Managed Scans that don't complete within the set Timeout value for "Fail open" are currently delayed up to 20 minutes. We are investigating the issue.
We've applied a fix for the issue, and fail-open updates should now be occurring in a timely manner. We are monitoring for stability.
This issue has been resolved.
We've observed that details pages for individual findings are not loading, and we are investigating.
We've identified the issue with findings details, and are working on a fix.
We've released a fix for the issue, and findings details pages are loading normally. We are monitoring to verify stability.
This issue has been resolved. All findings details pages are loading normally.
On-demand Assistant analysis from the Semgrep AppSec Platform is currently delayed. We have identified the issue and are working on a resolution.
On-demand Assistant analysis is now processing successfully but latency is persisting. Some analysis requests from earlier in the day may have failed; we will attempt to retry these when the system is healthy.
This issue has been resolved, and on-demand Assistant analyses are completing as expected.
We've observed an issue processing scan results, and are investigating.
We've applied a fix and are monitoring for stability.
The system is now processing normally.
The Jira ticketing integration in Semgrep AppSec Platform is currently unavailable due to a provider issue. We are tracking the provider status and will update accordingly.
The provider has addressed the issue but is still monitoring for stability.
The provider has recovered, and the Jira integration is behaving normally.