YorkHost - Client Area – Degraded Performance – Incident details

The issue has been fully resolved and the Client Area is now functioning normally.
We apologize for the disruption experienced. The recent deployment of our new high-availability HAProxy setup caused an unexpected configuration issue, which temporarily affected access through Cloudflare.

While high availability improves resilience, it can occasionally create unexpected behavior during synchronization. Our team has fine-tuned the configuration to avoid future occurrences and continues to monitor performance closely.

We are aware that the Client Area may still experience slow response times (around 3–4 seconds per refresh).
We continue to work on optimizing this, but debugging remains complex since we are not the developers or owners of the CMS (HostBill).
As a result, our main efforts are focused on the new Client Area Beta, which, being built entirely in Node.js, is far more stable, resilient, and easier to maintain.

Thank you for your continued patience and trust.

The degraded performance detected earlier was caused by an incorrect HAProxy configuration following last night’s infrastructure enhancement.
After recovering backups, we introduced multi-replica synchronization between the master and several secondary nodes.
An error in the configuration caused the HAProxy service to stop, leading Cloudflare to detect the backend as unavailable.

The issue has now been corrected, and all systems are operational.
We continue to monitor performance to ensure stability.