enum GmbH - Notice history

What happened

During the planned network maintenance, the pre-provisioning of a new NAT Gateway pair did not match the expected configuration. The mismatch only surfaced during the cutover, which extended the connectivity interruption in the fra region from the planned sub-minute window to approximately 32 minutes.

Kubernetes workloads recovered automatically once connectivity was restored. No customer action was or is required.

What we got wrong

We announced a < 1 minute impact window based on the procedure and a pre-provisioned NAT Gateway that had not been validated against our target configuration. We should have caught this before the cutover.

What changes

Any maintenance with upstream-provisioned components now requires a documented pre-cutover validation against the target configuration.

If you have questions or want to discuss impact on your workloads, reach us at support@enum.co