Back to overview

Frontend Performance Degradation Post-Mortem: High Availability Configuration Issue

Feb 26 at 01:00pm CET
Affected services
Front end

Resolved
Feb 26 at 01:00pm CET

Post-Mortem Report

Issue Description

We experienced a significant performance degradation on our frontend services due to an unintended side effect of enabling a "High Availability" feature on one of our providers. This configuration change resulted in increased routing latency to our servers.

Impact

  • Response times increased to ~4 seconds (normal response time is few milliseconds)
  • All requests were completing successfully but with significant delay
  • No automatic alerts were triggered as the services remained technically available

Root Cause Analysis

The performance degradation was caused by a misconfiguration in the High Availability settings, which introduced unnecessary routing overhead. Since our monitoring system was primarily focused on service availability rather than performance metrics, the increased latency went undetected by our automated systems. This made it challenging for our team to promptly identify the root cause, as requests were still successfully completing despite the significant delay.

Resolution

  • Our technical team investigated the anomaly
  • The High Availability configuration has been adjusted
  • Service performance has returned to normal levels

Action Items

  1. Implement latency monitoring and alerting
  2. Review High Availability configuration changes process
  3. Add performance baseline monitoring
  4. Enhance monitoring system to include performance thresholds
  5. Set up real-time latency tracking dashboards

We appreciate your patience during this incident. For any additional details, please contact us at support@teyuto.com.