Gcore - Cloud | Frankfurt am Main-1 | Managed PostgreSQL incident details – Incident details

**Incident Description:** A bug was introduced in an update that caused the `monitor_port` option to be ignored for some Load Balancer members, resulting DBaaS customers in the Frankfurt region being unable to access their databases. **Root Cause:** A defect from update affecting Load Balancer configurations. **Preventative Measures**: Increased test coverage for Load Balancers, integration of end-to-end and Terraform tests into deployment pipelines.

We'd like to inform you that the issue has been resolved, and we are closely monitoring the performance to ensure there are no further disruptions. We will provide a Root Cause Analysis (RCA) report in the coming days to help you understand what caused the incident and the steps we have taken to prevent it from happening again in the future. We apologize for any inconvenience this may have caused you, and want to thank you for your patience and understanding throughout this process.

We'd like to let you know that our engineering team has successfully located the issue affecting Managed PostgreSQL. The service is unavailable because of the broken health check mechanism in the database's cloud load balancer. Our team is now fully focused on rectifying the situation.

We are pleased to inform you that our engineering team has implemented a fix to resolve degradation in performance. However, we are still closely monitoring the situation to ensure stable performance.  We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.