enum GmbH Status - Incident history https://status.enum.co enum GmbH Thu, 16 Apr 2026 19:00:00 +0000 Scheduled Network Maintenance Type: Maintenance Duration: 3 days and 14 hours Affected Components: DNS, Cloud NAT, Identity & Access, API, Network, Compute, Object Storage, Load Balancer, Firewall, Kubernetes, Block Storage Apr 16, 19:00:00 GMT+0 - Identified - We will perform a planned network maintenance. During this window, brief connectivity interruptions may occur for workloads in the `fra` region. Existing TCP connections may be reset. Kubernetes workloads will recover automatically. No action is required on your side. **Expected impact:** < 1 minute of connectivity interruption **Region:** fra (Frankfurt) **Duration:** 120 minutes (maintenance window) For questions, reach us at [support@enum.co](mailto:support@enum.co) Apr 16, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 16, 20:26:00 GMT+0 - Completed - Maintenance has completed successfully Apr 16, 20:27:00 GMT+0 - Completed - **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](mailto:support@enum.co) Type: Maintenance

Duration: 3 days and 14 hours

Affected Components: , , , , , , , , , ,

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will perform a planned network maintenance. During this window, brief connectivity interruptions may occur for workloads in the `fra` region. Existing TCP connections may be reset. Kubernetes workloads will recover automatically. No action is required on your side. **Expected impact:** < 1 minute of connectivity interruption **Region:** fra (Frankfurt) **Duration:** 120 minutes (maintenance window) For questions, reach us at [support@enum.co](mailto:support@enum.co).</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>20:26:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>20:27:00</var> GMT+0</small><br><strong>Completed</strong> - **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](mailto:support@enum.co).</p> ]]> Thu, 16 Apr 2026 19:00:00 +0000 https://status.enum.co/maintenance/cmnx605j7014ph1870skr961v https://status.enum.co/maintenance/cmnx605j7014ph1870skr961v Identity & Access Type: Maintenance Duration: 3 hours Affected Components: Identity & Access Mar 14, 15:30:01 GMT+0 - Identified - Maintenance is now in progress Mar 14, 18:30:00 GMT+0 - Completed - Maintenance has completed successfully Mar 14, 15:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 3 hours

Affected Components:

<p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>15:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> ]]> Sat, 14 Mar 2026 15:30:00 +0000 https://status.enum.co/maintenance/cmmlfb9wd02p7i854hb1696jv https://status.enum.co/maintenance/cmmlfb9wd02p7i854hb1696jv Datacenter power supply Type: Maintenance Duration: 1 day and 2 hours Affected Components: DNS, Identity & Access, Network, Compute, Object Storage, Load Balancer, Firewall, Kubernetes, Block Storage Feb 9, 02:00:00 GMT+0 - Identified - Due to scheduled work by the local power grid operator, the data center location will temporarily operate on backup power systems (generator supply) during the above-mentioned period. Power will be supplied by fully redundant diesel generators (at least N+1). The transition to backup power and the return to normal operation will be carried out in a controlled, step-by-step manner under continuous monitoring by the data center operator. The data center provider does not expect any impact on services during these works. However, as a precaution, we would like to note that operations will be running outside of the regular normal state. The data center operator will have additional specialized personnel on site throughout the entire maintenance window and will provide building-specific updates regarding each power transition. Feb 9, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 10, 04:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 day and 2 hours

Affected Components: , , , , , , , ,

<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - Due to scheduled work by the local power grid operator, the data center location will temporarily operate on backup power systems (generator supply) during the above-mentioned period. Power will be supplied by fully redundant diesel generators (at least N+1). The transition to backup power and the return to normal operation will be carried out in a controlled, step-by-step manner under continuous monitoring by the data center operator. The data center provider does not expect any impact on services during these works. However, as a precaution, we would like to note that operations will be running outside of the regular normal state. The data center operator will have additional specialized personnel on site throughout the entire maintenance window and will provide building-specific updates regarding each power transition..</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 9 Feb 2026 02:00:00 +0000 https://status.enum.co/maintenance/cmlatllep006crykygu3mdw46 https://status.enum.co/maintenance/cmlatllep006crykygu3mdw46