Lusha incident

Conversational Intelligence returning 504 errors

Critical Resolved View vendor source →

Lusha experienced a critical incident on June 1, 2026 affecting Engage, lasting 1h 9m. The incident has been resolved; the full update timeline is below.

Started
Jun 01, 2026, 08:36 AM UTC
Resolved
Jun 01, 2026, 09:46 AM UTC
Duration
1h 9m
Detected by Pingoru
Jun 01, 2026, 08:36 AM UTC

Affected components

Engage

Update timeline

  1. investigating Jun 01, 2026, 08:36 AM UTC

    We are currently investigating disruptions to CI service.

  2. identified Jun 01, 2026, 09:09 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 01, 2026, 09:14 AM UTC

    between 08:33–09:05 UTC users saw errors loading CI features (calendar, meetings, snippets); root cause was an internal routing certificate mismatch, traffic has fully recovered and we are adding monitoring to prevent recurrence.

  4. resolved Jun 01, 2026, 09:46 AM UTC

    Conversational Intelligence (EU) is fully restored — the routing issue that caused errors between 07:45–09:05 UTC has been fixed and monitoring is in place to prevent recurrence.