Service degradation
Timeline · 2 updates
- identified Nov 28, 2025, 11:21 AM UTC
The engine is experiencing some instability. We are already working to resolve the issue.
- resolved Nov 28, 2025, 12:43 PM UTC
Resolved
Checkmarx had 4 outages in the last 2 years totaling 26h 45m of downtime — averaging 0.2 incidents per month.
There were 4 Checkmarx outages since September 8, 2025 totaling 26h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
The engine is experiencing some instability. We are already working to resolve the issue.
Resolved
We are currently experiencing issues due to cloud provider degradation. Our team is actively working to restore it.
Services are back since cloud provider services are operational.
Resolved
Around 17:50 scans started to get slow because of Sast Scan process. It got solved around 19:20, scans started to get to normal behavior. Scans that got stuck on the Sast process will not have that on scans and it will take more time than usual.
The problem is solved new scans have sast and have normal scan time.
Scan Engine fully operational
Slowness in exploitable path scans
Resolved
Due to an autoscaling issue the necessary instances to handle the requests were not available