Degraded Scan Performance
Timeline · 1 update
- resolved Apr 30, 2026, 10:29 PM UTC
Between 21:48 - 22:00 UTC some managed scans experienced additional latency. The root cause has been resolved.
There were 19 Semgrep outages since February 11, 2026 totaling 146h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 21:48 - 22:00 UTC some managed scans experienced additional latency. The root cause has been resolved.
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.
From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.
Starting around 16:00 UTC, some diff-aware Managed Scans for GitHub.com projects failed due to inability to fetch information about relevant branches, coinciding with a degradation in GitHub availability. The failure rate returned to normal just after 17:00 UTC and the system is now stable.
We have identified a problem in the service that generates the configuration for new scans. This incident began at approximately 17:30 UTC, and it affects both Managed Scans and CI scans. We have taken action and are actively monitoring the system. If you have a scan that is pending, you can push a new commit to cause the scan to retry.
This incident has been resolved.
Some users are unable to log in, and some managed scans are failing to start. We're investigating both.
We've identified the cause of the backend issues. Some traffic has resumed but services are still degraded, and we're continuing to remediate.
The problem is resolved and scans and logins are now processing normally.
Since 22:00 UTC, some fail-open processes for unfinished Managed Scans may have been delayed up to 40 minutes. We are investigating the issue.
We have implemented a change to allow faster processing of fail-open requests, and the delay has reduced to under 5 minutes. We are monitoring to ensure the system remains stable.
This issue has been resolved. Fail-open processes for unfinished Managed Scans continue to run normally.
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.
Since around 16:45 UTC, we have observed errors related to processing SCA dependencies. Some new dependency results since that time may not be available in the platform, and related licenses may not have been analyzed. We are investigating the issue and confirming the scope of impact.
We've identified the issue and are working on a fix. In addition to dependency and license results, some expected comments and other notifications may not be surfaced while the issue is active.
We've released a fix and are seeing errors start to resolve.
This issue has been resolved, and scan processing is completing normally.
We've identified an issue starting approximately 24 hours ago where users with read-only access to Semgrep AppSec Platform do not see their projects, and are working on a fix.
We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm.
This issue has been resolved, and read-only users should be able to view their projects as normal.
Starting March 26 around 06:00 UTC, findings data in Semgrep AppSec Platform may have been out of date by up to 9 hours. We have implemented a fix and are monitoring as data backfills.
Realtime sync is now healthy. We are continuing to monitor the data backfill.
Data backfill is now complete for most organizations. We are continuing to monitor the final syncs.
Data backfill continues to progress, and realtime sync remains healthy.
All data has backfilled and the system is healthy.
We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.
We have released a fix for this issue and are monitoring the results.
This issue has been resolved and scans are behaving normally.
Errors started Mar 12 at 21:30 PST and have been increasing since then.
We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail. This is primarily affecting diff scans, which are used for checks on PRs and MRs. The error rate began to rise at approximately 21:30PT on Thursday, March 12 (2026-03-13 04:30 UTC). We will share updates as information becomes available.
We have identified the cause of the problem and are working on a fix.
We’ve assessed that the scan failures are due to insufficient resources allocated to scans in particular projects. In response, we increased the resources available to affected projects. We are actively monitoring scan performance, and we’re seeing errors diminish. If your repository was affected, you can push a new commit to your PR/MR to trigger a new scan. The new scan will run with increased resources.
This incident has been resolved.
We are investigating reports of issues affecting repository scans and pull request checks. Some customers may see scans not starting or checks not appearing on pull requests. We are investigating and will share updates as more information becomes available.
We are continuing to investigate this issue.
We've identified the root cause of the issue that was affecting repository scans and pull request checks, and a fix has now been rolled out. We are now monitoring the results to make sure everything is running smoothly.
This issue has been resolved, and scans have returned to normal operation.
We are currently investigating a crash on the login page for Semgrep AppSec Platform. Existing sessions in the platform are still operative.
We have identified the source of the issue and are working on a fix.
We have released a fix and the login page is now loading. We are monitoring for system stability.
This issue has been resolved. Login and other platform functions are behaving normally.
We are currently investigating an issue with scan results not being processed. You may see scan jobs appear to hang or time out at the stage of reporting findings to the platform.
We have rolled out a fix and are seeing scan results processing resume. We are monitoring the system for stability.
This issue has been resolved, and the system is now processing scans normally.
We've identified an increase in errors for starting and completing scans since approximately 17:00 UTC (9:00 AM PST), and are working to resolve the issue.
Scan start and completion performance is now normal and we are continuing to monitor.
This issue has been resolved, and the services are currently behaving normally.
We are currently investigating an issue with degraded performance of scan start and completion in CI and Semgrep Managed Scans.
We have made changes to improve service availability and scans are now able to start and complete as expected. We will continue to monitor.
This issue has been resolved, and scans are starting and completing normally.
Semgrep AppSec platform is slow to load or returning errors, and we're currently investigating the issue.
The platform appears to be stable now, and we're currently monitoring the results.
The platform has remained stable, and this issue is considered resolved.
Pingoru polls Semgrep's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required