» Published on Tue, 07 Dec 2021 13:52:00 +0000

• Resolved

  The root cause of the incident is that a lack of memory in an internal component. Our team is working on a long term solution to this issue.

  The incident is considered over, please contact the support if you still experience some issues.

  » Updated Tue, 07 Dec 2021 14:35:00 +0000

• Update

  The osc-secnum-fr1 region is not impacted by this incident.

  Users seem to be able to start one-off again on the osc-fr1 region. We are still investigating the root cause of the incident, and monitoring the status.

  » Updated Tue, 07 Dec 2021 14:11:00 +0000

• Investigating

  Some users report issues to start one-off containers on the osc-fr1 region. The osc-secnum-fr1 region might also be impacted. Our team is investigating.

  » Updated Tue, 07 Dec 2021 13:52:00 +0000