Identified - We've identified the issue with the advisory update and are working to resolve the problem.
Sep 18, 2024 - 17:17 UTC
Investigating - We've observed that Supply Chain Advisories created since August 1st 2024 are not consistently populating in Semgrep. We are investigating this issue and will provide an update once we've identified the problem.
Sep 17, 2024 - 19:39 UTC
Welcome to the status page where you can see the current and historical health of semgrep.dev and all the related 3rd-party services such as GitHub and AWS. For support, please reach out on slack: https://r2c.dev/slack or submit a Support request if it is part of your Semgrep plan.
semgrep.dev
Degraded Performance
90 days ago
99.86
% uptime
Today
Login/SSO
Operational
90 days ago
99.93
% uptime
Today
Dashboard
Operational
90 days ago
99.99
% uptime
Today
API
Operational
90 days ago
100.0
% uptime
Today
Registry
Degraded Performance
90 days ago
100.0
% uptime
Today
Scans and CI/CD
?
Operational
90 days ago
99.44
% uptime
Today
Managed Scans
?
Operational
90 days ago
99.6
% 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.
Related
No incidents or maintenance related to this downtime.
Resolved -
This incident has been resolved.
Sep 13, 20:53 UTC
Identified -
Pull requests are still being scanned, but since 5 pm PST on Thursday, Sep 12, scheduled full scans have failed to run. We have identified the source of the problem and will have a fix up shortly.
Sep 13, 18:17 UTC
Resolved -
We've backfilled associations between findings and Jira tickets, and have gathered a list of duplicate Jira tickets created during the outage for affected deployments.
We will reach out to affected customers for next steps.
Sep 13, 01:29 UTC
Update -
We've been monitoring and are seeing Jira tickets being successfully linked to associated findings.
We've determined that Jira tickets created within the last five days were not associated with findings, and have prepared a backfill job to reassociate these tickets with the appropriate findings. We intend on running this backfill job tomorrow.
Sep 12, 06:05 UTC
Monitoring -
We've deployed a fix and are monitoring results.
Sep 11, 19:26 UTC
Identified -
We're seeing Jira tickets being successfully created, but not being linked to associated findings. We've identified the root cause and are deploying a fix.
We're looking into how to reassociate Jira tickets with findings for associations that were not created.
We will reach out to affected customers for next steps, and we will continue to update the status page as we release the fix and monitor.
Sep 11, 19:03 UTC