Is Semgrep down?

Last checked 9m ago
Current status
Semgrep is up

No incidents right now.

Get alerts when Semgrep breaks →

Free · no credit card

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

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 18 incidents in the last 90 days (97.05% 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 97.05% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. A small subset of users are unable to login
    Resolved 57m
    Started Apr 28, 2026, 06:16 PM UTC · Resolved Apr 28, 2026, 07:13 PM UTC
    Login/SSO
    3 updates · show timeline
    • identified · Apr 28, 2026, 06:16 PM UTC

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

    • monitoring · Apr 28, 2026, 07:11 PM UTC

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

    • resolved · Apr 28, 2026, 07:13 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Failure to start scans from 14:35 to 14:52 UTC
    Resolved —
    Started Apr 24, 2026, 04:37 PM UTC · Resolved Apr 24, 2026, 12:30 PM UTC
    1 update · show timeline
    • resolved · Apr 24, 2026, 04:37 PM UTC

      From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.

    Latest: From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.

  3. Failures running diff-aware scans for GitHub.com customers
    Resolved —
    Started Apr 23, 2026, 06:07 PM UTC · Resolved Apr 23, 2026, 04:00 PM UTC
    1 update · show timeline
    • 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.

    Latest: 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…

  4. Scans failing to start
    Resolved 21m
    Started Apr 22, 2026, 06:14 PM UTC · Resolved Apr 22, 2026, 06:35 PM UTC
    Scans and CI/CDManaged Scans
    2 updates · show timeline
    • 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.

    • resolved · Apr 22, 2026, 06:35 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Semgrep outage history

14 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 10 incidents
  • A small subset of users are unable to login Resolved
    Started Apr 28, 2026, 06:16 PM UTC · Resolved Apr 28, 2026, 07:13 PM UTC · 57m
  • Failure to start scans from 14:35 to 14:52 UTC Resolved
    Started Apr 24, 2026, 04:37 PM UTC · Resolved Apr 24, 2026, 12:30 PM UTC · —
  • Failures running diff-aware scans for GitHub.com customers Resolved
    Started Apr 23, 2026, 06:07 PM UTC · Resolved Apr 23, 2026, 04:00 PM UTC · —
  • Scans failing to start Resolved
    Started Apr 22, 2026, 06:14 PM UTC · Resolved Apr 22, 2026, 06:35 PM UTC · 21m
  • Login and scans are failing for some users Resolved
    Started Apr 20, 2026, 08:37 PM UTC · Resolved Apr 21, 2026, 12:29 AM UTC · 3h 51m
  • Delays for Managed scans fail-open process Resolved
    Started Apr 14, 2026, 12:02 AM UTC · Resolved Apr 14, 2026, 05:23 PM UTC · 17h 21m
  • Teams configuration is intermittently not loading and logins slow for some users Resolved
    Started Apr 13, 2026, 05:08 PM UTC · Resolved Apr 13, 2026, 06:13 PM UTC · 1h 5m
  • Supply chain dependency processing issues Resolved
    Started Apr 08, 2026, 07:35 PM UTC · Resolved Apr 08, 2026, 09:10 PM UTC · 1h 34m

See Semgrep in your Pingoru dashboard

Monitor Semgrep alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Semgrep to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Semgrep incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Semgrep or see every provider at once.

Maintenance calendar

Scheduled Semgrep maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Semgrep status change, one inbox

Pingoru watches Semgrep's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Semgrep reports on 16 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Semgrep alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Semgrep maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Semgrep services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Semgrep from the same account, with per-user notification preferences for any monitor.

Get notified on Semgrep status changes

Pingoru watches Semgrep's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Semgrep free

Monitor Semgrep along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Semgrep and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Semgrep uptime & incident history

See 90 days of Semgrep uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Semgrep uptime history

Frequently asked questions

What is Semgrep's uptime?
Over the last 90 days, Semgrep reported 97.05% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.semgrep.dev/?utm_source=embed — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Semgrep's uptime history rolling forward in real time.
Has Semgrep had outages in 2026?
Yes — Semgrep has had 18 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Semgrep outage?
The most recent Semgrep incident was "A small subset of users are unable to login", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.semgrep.dev/?utm_source=embed. See the full incident card above for affected components and the update timeline.
How often does Semgrep have outages?
Based on the last 90 days, Semgrep averages 6.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Semgrep's status page?
Semgrep's official status page is https://status.semgrep.dev/?utm_source=embed. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Semgrep down right now?
Semgrep is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Semgrep reports a change. Current status is based on 16 tracked services.
How does Pingoru know if Semgrep is down?
We read https://status.semgrep.dev/?utm_source=embed directly, using Semgrep's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Semgrep has an outage?
Create a free Pingoru account and add Semgrep as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Semgrep's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Semgrep incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Semgrep issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Semgrep status?
We use Semgrep's own status page at https://status.semgrep.dev/?utm_source=embed. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Semgrep components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Semgrep's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Semgrep free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →