1. Summary
On August 19, 2026, some customers experienced slower page loading and data display, as well as delays when starting or completing pull request scans.
The disruption was caused by a managed memory database entering a repeated restart cycle and not recovering automatically. This created a temporary slowdown in processing. Expected service behavior was restored after corrective actions, including replacement and increased capacity for the affected service. The provider is continuing to investigate why the service was unable to return to normal operation automatically.
2. Key Timeline (IDT)
August 19, 2026, 16:10 IDT: We identified performance degradation affecting parts of the platform and pull request scanning.
August 19, 2026, 16:30 IDT: An initial corrective change was applied and service behavior was monitored.
August 19, 2026, 16:46 IDT: We confirmed that some delays were continuing and expanded the investigation.
August 19, 2026, 17:14 IDT: We began working with our service provider to investigate instability in the managed memory database.
August 19, 2026, 18:46 IDT: Recovery actions were in progress, with temporary mitigations in place to reduce customer impact.
August 19, 2026, 19:06 IDT: The managed memory database capacity update completed, and platform responsiveness and pull request scanning returned to expected behavior.
3. Root Cause
The managed memory database entered a repeated restart cycle and was unable to recover automatically. This caused delays in the processing systems that support platform responsiveness and pull request scans.
The affected service underwent a routine replacement process, followed by a capacity increase during the recovery effort. While the capacity increase completed successfully and restored expected behavior, AWS is still researching why the service did not come back up normally after the restart cycle. Their detailed root-cause analysis is pending.
4. Actions Taken
Applied corrective updates to reduce immediate processing demand.
Temporarily adjusted the status update process to reduce reliance on the affected service.
Restarted affected processing components to restore responsiveness.
Worked with the service provider to replace affected capacity and complete a capacity increase.
Monitored platform performance and scan processing until expected behavior was confirmed.
4b. Action Items
Review the service provider’s detailed root-cause analysis when available.
Improve monitoring to detect similar recovery delays earlier.
Add safeguards to reduce the impact of temporary processing slowdowns.
Introduce separate Redis capacity for each service to isolate workloads and reduce the impact of an issue in one service on others.
Resolved
1. Summary
On August 19, 2026, some customers experienced slower page loading and data display, as well as delays when starting or completing pull request scans.
The disruption was caused by a managed memory database entering a repeated restart cycle and not recovering automatically. This created a temporary slowdown in processing. Expected service behavior was restored after corrective actions, including replacement and increased capacity for the affected service. The provider is continuing to investigate why the service was unable to return to normal operation automatically.
2. Key Timeline (IDT)
August 19, 2026, 16:10 IDT: We identified performance degradation affecting parts of the platform and pull request scanning.
August 19, 2026, 16:30 IDT: An initial corrective change was applied and service behavior was monitored.
August 19, 2026, 16:46 IDT: We confirmed that some delays were continuing and expanded the investigation.
August 19, 2026, 17:14 IDT: We began working with our service provider to investigate instability in the managed memory database.
August 19, 2026, 18:46 IDT: Recovery actions were in progress, with temporary mitigations in place to reduce customer impact.
August 19, 2026, 19:06 IDT: The managed memory database capacity update completed, and platform responsiveness and pull request scanning returned to expected behavior.
3. Root Cause
The managed memory database entered a repeated restart cycle and was unable to recover automatically. This caused delays in the processing systems that support platform responsiveness and pull request scans.
The affected service underwent a routine replacement process, followed by a capacity increase during the recovery effort. While the capacity increase completed successfully and restored expected behavior, AWS is still researching why the service did not come back up normally after the restart cycle. Their detailed root-cause analysis is pending.
4. Actions Taken
Applied corrective updates to reduce immediate processing demand.
Temporarily adjusted the status update process to reduce reliance on the affected service.
Restarted affected processing components to restore responsiveness.
Worked with the service provider to replace affected capacity and complete a capacity increase.
Monitored platform performance and scan processing until expected behavior was confirmed.
4b. Action Items
Review the service provider’s detailed root-cause analysis when available.
Improve monitoring to detect similar recovery delays earlier.
Add safeguards to reduce the impact of temporary processing slowdowns.
Introduce separate Redis capacity for each service to isolate workloads and reduce the impact of an issue in one service on others.
Monitoring
The remaining processing delays have cleared, and the Cycode application is operating normally. We are continuing to monitor the service.
Monitoring
The Cycode application remains stable and page loading is operating normally. Some pull request scans may still be delayed while we continue clearing the remaining backlog and monitor recovery.
Monitoring
The Cycode application is stable and page loading is operating normally.
Some pull request scans are still experiencing delays. We are continuing to monitor the service and work to clear the remaining scan backlog.
Monitoring
We are monitoring stability of the affected memory database service. It currently appears stable, but our provider has not yet confirmed full recovery. We will share another update once recovery is confirmed.
Identified
Some customers may continue to experience slower response times across the Cycode application. This can include delays loading pages, viewing data, and starting or completing pull request scans.
We have identified instability in an underlying data service that is affecting request processing. Our infrastructure provider is actively working to restore the affected service; recovery has not yet completed successfully. We have applied temporary changes to reduce demand on the service while we monitor its stability and work with the provider on a permanent resolution.
We will share another update as soon as we have confirmed service stability or have additional information to report.
Investigating
We're investigating potential issue with one of the infrastructural services with infra provider support team.
Monitoring
System response times are back to normal. We're monitoring system state.
Investigating
Cycode experiences increased response time for selected requests. We're investigating the issue.