Evalink incident

Degradation of Search Functionality in Frankfurt

Minor Resolved View vendor source →

Evalink experienced a minor incident on February 27, 2025 affecting Region Europe, lasting 1h 2m. The incident has been resolved; the full update timeline is below.

Started
Feb 27, 2025, 02:13 PM UTC
Resolved
Feb 27, 2025, 03:15 PM UTC
Duration
1h 2m
Detected by Pingoru
Feb 27, 2025, 02:13 PM UTC

Affected components

Region Europe

Update timeline

  1. investigating Feb 27, 2025, 02:13 PM UTC

    We are currently experiencing an issue with the search functionality in our Frankfurt region. Our team is investigating the cause and working on a resolution. Alarm transmission is not affected.

  2. identified Feb 27, 2025, 02:19 PM UTC

    The issue has been identified as a corrupted index in the database, which is affecting the search functionality. Our team is actively working on recreating the index to restore normal operation. We will provide further updates as the situation progresses.

  3. monitoring Feb 27, 2025, 02:36 PM UTC

    A temporary fix has been deployed to bypass the corrupted index, restoring search functionality. We are continuing work on fully rebuilding the index to ensure long-term stability.

  4. resolved Feb 27, 2025, 03:15 PM UTC

    A corrupted database index impacted search functionality in our Frankfurt region, leading to increased database load and a temporary degradation in overall system performance. We initially deployed a temporary fix to bypass the corrupted index, restoring search functionality and stabilizing performance. A permanent fix has now been implemented to improve search performance independently of the index. Additionally, the index has been recovered to restore optimal system efficiency. Alarm transmission was not affected at any time. The issue is now fully resolved, and no further impact is expected.