Because this incident affected our primary ingress controller, all services hosted on our OVH platform were unreachable, including:

• Bots, Widgets / Chat Interfaces
• User Login & Authentication
• EGPT
• Dashboards & AI Insights

What Happened:
The instability was caused by our traffic controller entering a restart loop due to resource constraints. This prevented any external traffic from reaching our services.

Resolution & Prevention:
Our team stabilized the environment by allocating dedicated resources and isolating the traffic controller to its own node. To prevent a recurrence, we are accelerating the migration to a new cluster architecture that implements strict resource isolation for all core components.

We apologize for the impact on your operations.

We have resolved the intermittent connectivity issues affecting our platform. After a period of instability, our team implemented a configuration change that has successfully restored full access to all services.

Systems are back online and performing as expected. We are continuing to monitor the environment closely to ensure continued stability.

After a short period of stability, we are seeing a recurrence of the connectivity issues identified earlier. Our engineers are back on the case and treating this as a high-priority regression.

ebbot.eu went down.