Managed scans are delayed
Timeline · 1 update
- resolved Oct 01, 2025, 12:14 AM UTC
From around 1830 to 2330 UTC, managed scans were delayed in starting by up to an hour. The misconfiguration has been fixed and scan latency is returning to normal.
Semgrep had 60 outages in the last 2 years totaling 83h 43m of downtime — averaging 2.5 incidents per month.
There were 60 Semgrep outages since August 29, 2025 totaling 83h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
From around 1830 to 2330 UTC, managed scans were delayed in starting by up to an hour. The misconfiguration has been fixed and scan latency is returning to normal.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
The fix has been implemented and we're working through the backlog of pending scans. Some scans from earlier today may be skipped and can be rerun.
The fix has been implemented and we're working through the backlog of pending scans. Some scans from earlier today may be skipped and can be rerun.
This incident has been resolved.
We are currently investigating issues with creating a private app (for code access) when connecting to GitHub.com as a source code manager.
We've identified the source of the issue and are working on a fix.
A fix has been implemented and we are now seeing successful app creations. We will continue to monitor to confirm the fix.
This issue has been resolved, and app creation requests are succeeding.
We are currently investigating reports from users that connecting to GitHub.com as a source code manager (SCM) in Semgrep AppSec Platform is unsuccessful.
We've identified the problem as a missing authentication refresh between Semgrep and GitHub that affects users in rare situations. If you're currently unable to connect your GitHub organization to Semgrep, please reach out to Semgrep Support for assistance until the fix is complete.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating the cause of the problem
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.