Status: ScheduledWe will be upgrading a backend component on the US platform. No downtime is expected, the platform will continue to work normally during the maintenance window.Affected components Secrets Detection API (Under maintenance) Dashboard (Under maintenance) MCP Server (beta) (Under maintenance) Webhooks (Under maintenance) Secret Detection - Scan Check Run (Under maintenance)
Status: ScheduledWe will be upgrading a backend component on the EU platform. No downtime is expected, the platform will continue to work normally during the maintenance window.Affected components MCP Server (beta) (Under maintenance) Webhooks (Under maintenance) Secrets Detection API (Under maintenance) Secret Detection - Scan Check Run (Under maintenance) Dashboard (Under maintenance)
Status: ResolvedResolution has been validated.Affected components Secrets Detection API (Operational)
Status: ResolvedSystem is back to normal operations.Affected components Webhooks (Operational) Secret Detection - Scan Check Run (Operational)
Status: ResolvedResolved. Following database query optimizations and reduced load from noisy background jobs, no further performance degradation has been observed. Metrics have been stable since deployment of the fixes.Affected components Secret Detection - Scan Check Run (Operational)
Status: ResolvedThis incident is now resolved. Following fixes deployed by our team, we have not observed further performance degradation, and metrics have been stable since.Affected components Secret Detection - Scan Check Run (Operational)
Status: CompleteMaintenance has completedAffected components Secret Detection - Scan Check Run (Under maintenance) Secrets Detection API (Under maintenance) Dashboard (Under maintenance) MCP Server (beta) (Under maintenance)
Status: ResolvedGitHub has restored their API, and our public ingestion pipeline has fully recovered. Real-time event ingestion and commit retrieval are operating normally again. This incident was caused by an upstream GitHub API outage and is now resolved. Thank you for your patience.Affected components Data Collectors (Operational)
Status: ResolvedThe fix has successfully been deployed and the situation should be back to normal. Sorry for the inconvenience.Affected components Secret Detection - Scan Check Run (Operational)
Status: ResolvedMaintenance is done. All services are back to normal operational mode.Affected components MCP Server (beta) (Operational) Webhooks (Operational) Secrets Detection API (Operational) Secret Detection - Scan Check Run (Operational) Dashboard (Operational)
Status: ResolvedWhat happened:From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messages. Impact:No data was lost. The only impact for customers could have been a delay between the detection of a secret and the moment the corresponding incident was created in the customer's dashboard. The p…
Status: ResolvedWe deployed a fix today that addressed the check run issues. A brief database load increase was observed post-deployment with no impact on check run results.This incident is now resolved.Affected components Secret Detection - Scan Check Run (Operational)
Status: ResolvedMaintenance is over.Affected components MCP Server (beta) (Operational) Webhooks (Operational) Secrets Detection API (Operational) Secret Detection - Scan Check Run (Operational) Dashboard (Operational)
Status: ResolvedBetween April 14, 2026 at 14:02 UTC and April 15, 2026 at 11:04 UTC, this status page was unavailable due to a misconfiguration on our end. During this period, we were unable to publish incident updates here, and you may not have received your usual notifications for any events that occurred within this window. We sincerely apologize for any confusion this may have caused. We are n…