All Systems Operational

About This Site

Welcome to the status page where you can see the current and historical health of the Semgrep AppSec Platform (https://semgrep.dev) and the related 3rd-party services such as GitHub and AWS. For support, please reach out on Slack: https://go.semgrep.dev/slack, or submit a Support request if it is part of your Semgrep plan.

Uptime over the past 90 days. View historical uptime.
semgrep.dev Operational
90 days ago
99.95 % uptime
Today
Login/SSO Operational
90 days ago
99.95 % uptime
Today
Dashboard Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Registry Operational
90 days ago
100.0 % uptime
Today
Scans and CI/CD Operational
90 days ago
99.93 % uptime
Today
Managed Scans Operational
90 days ago
99.86 % uptime
Today
AWS Operational
AWS ecr-us-west-2 Operational
AWS ec2-us-west-2 Operational
AWS eks-us-west-2 Operational
AWS firehose-us-west-2 Operational
GitHub Operational
GitHub GitHub Actions Operational
GitHub Visit www.githubstatus.com for more information Operational
GitHub API Requests Operational
GitHub Pull Requests Operational
Slack Operational
Slack Apps/Integrations Operational
Slack Apps/Integrations/APIs Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Database Maintenance for all tenants May 30, 2026 00:00-03:00 UTC

Scheduled - During this window, each customer's Semgrep database will experience a brief interruption:
- Single tenant customers: ~30-90 seconds of unavailability
- All customers (multi-tenant): ~1-2 minutes of unavailability

During this brief outage, the Semgrep web app and API may return connection errors. API clients and CI integrations with normal retry/reconnect logic will resume automatically - no action required from customers.
May 27, 2026 - 14:38 UTC
May 29, 2026

No incidents reported today.

May 28, 2026

No incidents reported.

May 27, 2026

No incidents reported.

May 26, 2026

No incidents reported.

May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026

No incidents reported.

May 22, 2026

No incidents reported.

May 21, 2026

No incidents reported.

May 20, 2026
Logins are failing for users via GitHub auth
Resolved - This incident has been resolved.
May 20, 18:18 UTC
Update - This incident has been resolved.
May 20, 18:17 UTC
Monitoring - We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability.
May 20, 17:49 UTC
Identified - We are currently observing login issues using GitHub auth. Our team has identified the issue and is currently working on a fix. SSO logins are working as expected and are not impacted.
May 20, 17:34 UTC
Managed Scans: full project scans being associated with HEAD instead of the default branch name
Resolved - This incident has been resolved.
May 20, 02:52 UTC
Monitoring - We have deployed the fix and are monitoring.
May 20, 02:47 UTC
Identified - We have identified the issue and are working on a resolution.
May 20, 02:08 UTC
Investigating - We are currently investigating an issue where full project scans in Managed Scans are being associated with HEAD rather than the name of the default branch. This issue started around 16:00 UTC on May 19 and may result in unexpected new findings notifications, and some findings not being closed as expected.
May 20, 01:18 UTC
May 19, 2026
Scheduling delays for Semgrep Managed Scanning (SMS)
Resolved - This incident has been resolved. We are continuing to monitor the system.
May 19, 21:33 UTC
Monitoring - The scan success rate is recovering. We are continuing to monitor the system.
May 19, 21:26 UTC
Update - Since the beginning of the incident, a portion of SMS scans have failed to execute.

We have deployed a change to the system. We are seeing scheduling queues begin to recover, and we're continuing to monitor the situation.
May 19, 21:07 UTC
Identified - We have identified a likely cause of this incident. We are currently rolling out a change to address it.
May 19, 19:47 UTC
Update - We are continuing to investigate the issue. We will post updates when further information is available.
May 19, 19:21 UTC
Investigating - We are investigating delays scheduling SMS scans. This issue began at approximately 18:30 UTC today.
May 19, 18:54 UTC
May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage