Document service instability

What to do

• Check whether you use Lucid in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2019-02-13 14:15 UTC and 2019-02-13 14:15 UTC may need a replay.

• Subscribe to Lucid's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=lucid works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Lucid 1

1. resolvedFeb 13, 2019, 2:15 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.