Lexer incident

Hub.lexer.io performance degraded

Resolved after 1 day 5 hours, affecting Hub, on February 17, 2025.

monitoring Feb 18, 2025, 04:57 AM UTC

A fix has been implemented and we are monitoring the results.

Started
Feb 17, 2025, 11:43 PM UTC
Resolved
Feb 19, 2025, 05:24 AM UTC
Duration
1d 5h
Detected by Pingoru
Feb 17, 2025, 11:43 PM UTC

Affected components

Hub

Update timeline

  1. investigating Feb 17, 2025, 11:43 PM UTC

    We're investigating reports of degraded performance for hub.lexer.io.

  2. investigating Feb 17, 2025, 11:43 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 17, 2025, 11:55 PM UTC

    We are experiencing a high rate of search timeout errors when loading conversations in Listen and Respond. Our team is continuing to investigate the root cause.

  4. identified Feb 18, 2025, 02:28 AM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Feb 18, 2025, 04:57 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Feb 19, 2025, 05:24 AM UTC

    This incident has been resolved.

Your product runs on more than Lexer

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →