Skip to main content
Lucid

Incident with lucid.app

Partial outage Lasted 33m · started · Lucid's page

Level
confirmed
Worst impact
Partial outage
Components
Document List (US), Document Editor (US)
Regions
us
Down Index
30of 100

What to do

  • Check whether you use Lucid Document List (US), Document Editor (US) 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 33m it lasted.

    Anything that failed between 2023-03-13 16:33 UTC and 2023-03-13 17:07 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 4

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

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

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-5d3e292ab2

Is Lucid still down?

No, this incident was resolved 2023-03-13 17:07 UTC. For Lucid's live state, see https://down.guide/lucid.

How long did it last?

33m, from 2023-03-13 16:33 UTC to 2023-03-13 17:07 UTC, by the times Lucid posted.

What was affected?

Lucid named Document List (US), Document Editor (US) in us.

What caused it?

Lucid hasn't published a root cause. If it does, it shows here.

Where does this come from?

Lucid's official status page, https://status.lucid.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.