Lucid incident

Document service instability

Notice Resolved View vendor source →

Lucid experienced a notice incident on February 13, 2019, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2019, 02:15 PM UTC
Resolved
Feb 13, 2019, 02:15 PM UTC
Duration
Detected by Pingoru
Feb 13, 2019, 02:15 PM UTC

Update timeline

  1. resolved Feb 13, 2019, 11:50 PM UTC

    At 4:56 a.m. Mountain Time our Lucidchart services entered into a degraded state, causing users to be inconsistently able to access or edit diagrams. Our system immediately alerted us to these errors and our engineers began working on a fix until we were able to get our document services up and running again within 2 hours. We have identified the root cause as a misconfigured thread pool. We have fixed the thread pool and have also started an internal audit to ensure that we do not have any other thread pools in a similar state.