Is Semgrep down?

Last checked 4m ago
Current status
Semgrep is up

No incidents right now.

Official status page: https://status.semgrep.dev/?utm_source=embed · Polled every 5 minutes · 16 components tracked

Semgrep is operational right now. Last checked 4m ago; the most recent incident resolved 9h 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 15 incidents in the last 90 days (98.75% uptime). Get email, Slack, Discord, or webhook alerts the moment Semgrep reports a new incident — free for 5 monitors, no credit card.

Users who monitor Semgrep also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Semgrep uptime 98.75% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 9m
    Started Sep 14, 2026, 06:23 PM UTC · Resolved Sep 14, 2026, 07:33 PM UTC
    Scans and CI/CDManaged Scans
    Timeline · 2 updates
    • investigating · Sep 14, 2026, 06:23 PM UTC

      We are currently investigating the issue.

    • resolved · Sep 14, 2026, 07:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 18m
    Started Sep 10, 2026, 04:17 PM UTC · Resolved Sep 10, 2026, 04:36 PM UTC
    Timeline · 3 updates
    • investigating · Sep 10, 2026, 04:17 PM UTC

      We are investigating an increase in traffic causing platform wide issues. The UI, scanning, and API may be affected.

    • monitoring · Sep 10, 2026, 04:21 PM UTC

      We believe we have recovered, we are monitoring for additional impact.

    • resolved · Sep 10, 2026, 04:36 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 24m
    Started Sep 04, 2026, 11:13 PM UTC · Resolved Sep 04, 2026, 11:38 PM UTC
    Timeline · 2 updates
    • investigating · Sep 04, 2026, 11:13 PM UTC

      An incomplete patch release of Semgrep 1.176.1 has left installations of this version using PyPI unable to use the Pro Engine. We recommend explicitly installing version 1.175.1 or 1.176.0 as we work to resolve this issue.

    • resolved · Sep 04, 2026, 11:38 PM UTC

      This issue has been resolved. The Pro Engine can be installed and used normally after installing Semgrep 1.176.1 via PyPI.

    Latest: This issue has been resolved. The Pro Engine can be installed and used normally after installing Semgrep 1.176.1 via PyPI.

  4. Resolved 1h 10m
    Started Sep 03, 2026, 09:35 PM UTC · Resolved Sep 03, 2026, 10:45 PM UTC
    Managed Scans
    Timeline · 4 updates
    • investigating · Sep 03, 2026, 09:35 PM UTC

      We are currently investigating this issue.

    • investigating · Sep 03, 2026, 09:55 PM UTC

      AWS STS outage in us-west-2 is affecting our system. We are investigating mitigations.

    • monitoring · Sep 03, 2026, 10:30 PM UTC

      Early signs of recovery for all Semgrep products. We are actively monitoring AWS updates on the regional, multi-service outage.

    • resolved · Sep 03, 2026, 10:45 PM UTC

      Metrics show full recovery of all Semgrep products. Our engineering team will continue monitoring until the final update from AWS.

    Latest: Metrics show full recovery of all Semgrep products. Our engineering team will continue monitoring until the final update from AWS.

  5. Resolved 1d 1h
    Started Sep 01, 2026, 10:50 PM UTC · Resolved Sep 03, 2026, 12:10 AM UTC
    Managed Scans
    Timeline · 4 updates
    • identified · Sep 01, 2026, 10:50 PM UTC

      A small number (<1%) of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing since August 28, due to rate limiting applied by a public package registry. Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time.

    • identified · Sep 01, 2026, 10:55 PM UTC

      Under one percent of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing, due to rate limiting applied by a third-party package registry. Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time

    • monitoring · Sep 02, 2026, 04:25 PM UTC

      The third party registry's rate limits have been lifted, and impact to scans appears mitigated.

    • resolved · Sep 03, 2026, 12:10 AM UTC

      Dynamic maven & gradle scans are now operating as normal.

    Latest: Dynamic maven & gradle scans are now operating as normal.

See the full Semgrep outage history

9 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

Outage history

Past 90 days · 14 incidents View full outage history →