Semgrep Outage History

Semgrep is up right now

There were 19 Semgrep outages since February 11, 2026 totaling 146h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.semgrep.dev/?utm_source=embed

Minor April 30, 2026

Degraded Scan Performance

Detected by Pingoru
Apr 30, 2026, 10:29 PM UTC
Resolved
Apr 30, 2026, 10:00 PM UTC
Duration
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice April 28, 2026

A small subset of users are unable to login

Detected by Pingoru
Apr 28, 2026, 06:16 PM UTC
Resolved
Apr 28, 2026, 07:13 PM UTC
Duration
57m
Affected: Login/SSO
Timeline · 3 updates
  1. identified Apr 28, 2026, 06:16 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 28, 2026, 07:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 28, 2026, 07:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

Failures running diff-aware scans for GitHub.com customers

Detected by Pingoru
Apr 23, 2026, 06:07 PM UTC
Resolved
Apr 23, 2026, 04:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 23, 2026, 06:07 PM UTC

    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.

Read the full incident report →

Critical April 22, 2026

Scans failing to start

Detected by Pingoru
Apr 22, 2026, 06:14 PM UTC
Resolved
Apr 22, 2026, 06:35 PM UTC
Duration
21m
Affected: Scans and CI/CDManaged Scans
Timeline · 2 updates
  1. monitoring Apr 22, 2026, 06:14 PM UTC

    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.

  2. resolved Apr 22, 2026, 06:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 20, 2026

Login and scans are failing for some users

Detected by Pingoru
Apr 20, 2026, 08:37 PM UTC
Resolved
Apr 21, 2026, 12:29 AM UTC
Duration
3h 51m
Affected: Login/SSOManaged Scans
Timeline · 3 updates
  1. investigating Apr 20, 2026, 08:37 PM UTC

    Some users are unable to log in, and some managed scans are failing to start. We're investigating both.

  2. identified Apr 20, 2026, 09:56 PM UTC

    We've identified the cause of the backend issues. Some traffic has resumed but services are still degraded, and we're continuing to remediate.

  3. resolved Apr 21, 2026, 12:29 AM UTC

    The problem is resolved and scans and logins are now processing normally.

Read the full incident report →

Minor April 14, 2026

Delays for Managed scans fail-open process

Detected by Pingoru
Apr 14, 2026, 12:02 AM UTC
Resolved
Apr 14, 2026, 05:23 PM UTC
Duration
17h 21m
Affected: Managed Scans
Timeline · 3 updates
  1. investigating Apr 14, 2026, 12:02 AM UTC

    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.

  2. monitoring Apr 14, 2026, 12:46 AM UTC

    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.

  3. resolved Apr 14, 2026, 05:23 PM UTC

    This issue has been resolved. Fail-open processes for unfinished Managed Scans continue to run normally.

Read the full incident report →

Notice April 13, 2026

Teams configuration is intermittently not loading and logins slow for some users

Detected by Pingoru
Apr 13, 2026, 05:08 PM UTC
Resolved
Apr 13, 2026, 06:13 PM UTC
Duration
1h 5m
Timeline · 3 updates
  1. identified Apr 13, 2026, 05:08 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 13, 2026, 05:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 13, 2026, 06:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Supply chain dependency processing issues

Detected by Pingoru
Apr 08, 2026, 07:35 PM UTC
Resolved
Apr 08, 2026, 09:10 PM UTC
Duration
1h 34m
Affected: DashboardAPIScans and CI/CD
Timeline · 4 updates
  1. investigating Apr 08, 2026, 07:35 PM UTC

    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.

  2. identified Apr 08, 2026, 08:03 PM UTC

    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.

  3. monitoring Apr 08, 2026, 08:20 PM UTC

    We've released a fix and are seeing errors start to resolve.

  4. resolved Apr 08, 2026, 09:10 PM UTC

    This issue has been resolved, and scan processing is completing normally.

Read the full incident report →

Minor March 31, 2026

Semgrep AppSec Platform users with read-only access cannot see their projects

Detected by Pingoru
Mar 31, 2026, 05:14 PM UTC
Resolved
Mar 31, 2026, 09:36 PM UTC
Duration
4h 22m
Affected: Dashboard
Timeline · 3 updates
  1. identified Mar 31, 2026, 05:14 PM UTC

    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.

  2. monitoring Mar 31, 2026, 07:03 PM UTC

    We have released a fix for this issue and access should be restored to normal. We are monitoring to confirm.

  3. resolved Mar 31, 2026, 09:36 PM UTC

    This issue has been resolved, and read-only users should be able to view their projects as normal.

Read the full incident report →

Minor March 26, 2026

Findings data out of date for organizations using combined Code/AI view

Detected by Pingoru
Mar 26, 2026, 03:27 PM UTC
Resolved
Mar 30, 2026, 11:55 PM UTC
Duration
4d 8h
Affected: DashboardAPI
Timeline · 5 updates
  1. monitoring Mar 26, 2026, 03:27 PM UTC

    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.

  2. monitoring Mar 26, 2026, 07:38 PM UTC

    Realtime sync is now healthy. We are continuing to monitor the data backfill.

  3. monitoring Mar 26, 2026, 11:43 PM UTC

    Data backfill is now complete for most organizations. We are continuing to monitor the final syncs.

  4. monitoring Mar 27, 2026, 06:20 PM UTC

    Data backfill continues to progress, and realtime sync remains healthy.

  5. resolved Mar 30, 2026, 11:55 PM UTC

    All data has backfilled and the system is healthy.

Read the full incident report →

Minor March 17, 2026

Elevated error rates in Managed Scans

Detected by Pingoru
Mar 17, 2026, 09:22 PM UTC
Resolved
Mar 17, 2026, 10:37 PM UTC
Duration
1h 14m
Affected: Managed Scans
Timeline · 3 updates
  1. investigating Mar 17, 2026, 09:22 PM UTC

    We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail.

  2. monitoring Mar 17, 2026, 10:21 PM UTC

    We have released a fix for this issue and are monitoring the results.

  3. resolved Mar 17, 2026, 10:37 PM UTC

    This issue has been resolved and scans are behaving normally.

Read the full incident report →

Major March 13, 2026

Elevated errors on managed diff scans

Detected by Pingoru
Mar 13, 2026, 06:10 PM UTC
Resolved
Mar 13, 2026, 07:48 PM UTC
Duration
1h 37m
Affected: Managed Scans
Timeline · 5 updates
  1. investigating Mar 13, 2026, 06:10 PM UTC

    Errors started Mar 12 at 21:30 PST and have been increasing since then.

  2. investigating Mar 13, 2026, 06:15 PM UTC

    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.

  3. identified Mar 13, 2026, 06:55 PM UTC

    We have identified the cause of the problem and are working on a fix.

  4. monitoring Mar 13, 2026, 07:25 PM UTC

    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.

  5. resolved Mar 13, 2026, 07:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 6, 2026

Investigating issues with pull request checks and repository scans

Detected by Pingoru
Mar 06, 2026, 12:04 PM UTC
Resolved
Mar 06, 2026, 04:18 PM UTC
Duration
4h 14m
Affected: GitHub Pull RequestsScans and CI/CDManaged Scans
Timeline · 4 updates
  1. investigating Mar 06, 2026, 12:04 PM UTC

    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.

  2. investigating Mar 06, 2026, 12:24 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 06, 2026, 03:47 PM UTC

    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.

  4. resolved Mar 06, 2026, 04:18 PM UTC

    This issue has been resolved, and scans have returned to normal operation.

Read the full incident report →

Critical March 3, 2026

Semgrep AppSec Platform login page is not working

Detected by Pingoru
Mar 03, 2026, 07:23 PM UTC
Resolved
Mar 03, 2026, 08:05 PM UTC
Duration
41m
Affected: Login/SSO
Timeline · 4 updates
  1. investigating Mar 03, 2026, 07:23 PM UTC

    We are currently investigating a crash on the login page for Semgrep AppSec Platform. Existing sessions in the platform are still operative.

  2. identified Mar 03, 2026, 07:28 PM UTC

    We have identified the source of the issue and are working on a fix.

  3. monitoring Mar 03, 2026, 07:42 PM UTC

    We have released a fix and the login page is now loading. We are monitoring for system stability.

  4. resolved Mar 03, 2026, 08:05 PM UTC

    This issue has been resolved. Login and other platform functions are behaving normally.

Read the full incident report →

Minor February 24, 2026

Newly reported scan results not being processed (CI and Semgrep Managed Scans)

Detected by Pingoru
Feb 24, 2026, 10:38 PM UTC
Resolved
Feb 24, 2026, 11:20 PM UTC
Duration
42m
Affected: Scans and CI/CDManaged Scans
Timeline · 3 updates
  1. investigating Feb 24, 2026, 10:38 PM UTC

    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.

  2. investigating Feb 24, 2026, 11:13 PM UTC

    We have rolled out a fix and are seeing scan results processing resume. We are monitoring the system for stability.

  3. resolved Feb 24, 2026, 11:20 PM UTC

    This issue has been resolved, and the system is now processing scans normally.

Read the full incident report →

Minor February 23, 2026

Degraded scan start and completion performance

Detected by Pingoru
Feb 23, 2026, 06:09 PM UTC
Resolved
Feb 23, 2026, 08:13 PM UTC
Duration
2h 4m
Affected: Scans and CI/CDManaged Scans
Timeline · 3 updates
  1. identified Feb 23, 2026, 06:09 PM UTC

    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.

  2. monitoring Feb 23, 2026, 07:50 PM UTC

    Scan start and completion performance is now normal and we are continuing to monitor.

  3. resolved Feb 23, 2026, 08:13 PM UTC

    This issue has been resolved, and the services are currently behaving normally.

Read the full incident report →

Minor February 12, 2026

Degraded scan start and completion performance in CI and Semgrep Managed Scans

Detected by Pingoru
Feb 12, 2026, 05:09 PM UTC
Resolved
Feb 12, 2026, 05:54 PM UTC
Duration
45m
Affected: Scans and CI/CDManaged Scans
Timeline · 3 updates
  1. investigating Feb 12, 2026, 05:09 PM UTC

    We are currently investigating an issue with degraded performance of scan start and completion in CI and Semgrep Managed Scans.

  2. monitoring Feb 12, 2026, 05:29 PM UTC

    We have made changes to improve service availability and scans are now able to start and complete as expected. We will continue to monitor.

  3. resolved Feb 12, 2026, 05:54 PM UTC

    This issue has been resolved, and scans are starting and completing normally.

Read the full incident report →

Minor February 11, 2026

Semgrep AppSec platform slow to load

Detected by Pingoru
Feb 11, 2026, 09:49 PM UTC
Resolved
Feb 11, 2026, 11:05 PM UTC
Duration
1h 16m
Affected: Login/SSODashboardAPIRegistry
Timeline · 3 updates
  1. investigating Feb 11, 2026, 09:49 PM UTC

    Semgrep AppSec platform is slow to load or returning errors, and we're currently investigating the issue.

  2. monitoring Feb 11, 2026, 10:09 PM UTC

    The platform appears to be stable now, and we're currently monitoring the results.

  3. resolved Feb 11, 2026, 11:05 PM UTC

    The platform has remained stable, and this issue is considered resolved.

Read the full incident report →

Looking to track Semgrep downtime and outages?

Pingoru polls Semgrep's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Semgrep reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Semgrep alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Semgrep for free

5 free monitors · No credit card required