According to the Jelastic support investigation, the fix for this kernel-related issue will be included in the upcoming kernel update. We now hope that it will not occur again until this release, and we are monitoring the development very closely.
One of the hardware nodes has rebooted after a crash. Affected containers were therefore also restarted. We are currently investigating the incident.