Incident Summary: On Saturday June 1st 10:31 AM CEST, GatewayAPI.EU experienced an issue that affected the functionality of our REST API, leading to the platform being inaccessible. This incident was a result of a configuration issue that became apparent following an unexpected restart of the EU cluster.

Root Cause: The root cause of the incident was traced to a code cleanup that removed an integration. This change inadvertently left our internal system API with a broken configuration. The issue was not immediately apparent and only surfaced when the pods restarted. For unknown reasons, the entire EU cluster had to restart, triggering a cascade of failures across our interconnected services.

Impact:

• Users Affected: All
• Duration of Impact: 10:30 - 11:32 CEST
• Services Affected: REST API, message delivery

Resolution and Recovery: Our engineering team corrected the configuration issue in the internal system API and successfully restarted the affected services. The REST API functionality was restored, and message delivery resumed normal operations.

Preventive Measures: To prevent a recurrence of this issue, we are implementing the following measures:

1. Configuration Management: Enhance our configuration validation processes to catch such issues before deployment.
2. Pod Restart Protocols: Investigate and address the cause of the unexpected EU cluster restart.
3. Service Dependency Monitoring: Improve monitoring of service dependencies to quickly identify and resolve cascading failures.

We apologize for any inconvenience this incident may have caused. Our team is committed to ensuring the reliability and robustness of our services.