- Level
- confirmed
- Worst impact
- Degraded
- Components
- Document Editor (US)
- Regions
- us
- Down Index
- 19of 100
What to do
Check whether you use Lucid 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 25m it lasted.
Anything that failed between 2019-02-26 09:50 UTC and 2019-02-26 10: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 2
- investigating
Our document service slowed down for a few seconds and then recovered. We are investigating the root cause.
provider
- resolved
This issue resolved itself a few seconds after the slowdown occurred. The root cause of this issue is from an increase in requests from one of our internal jobs. We are tuning the endpoints to paginate requests more aggressively.
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-acaaedc783
Is Lucid still down?
No, this incident was resolved 2019-02-26 10:15 UTC. For Lucid's live state, see https://down.guide/lucid.
How long did it last?
25m, from 2019-02-26 09:50 UTC to 2019-02-26 10:15 UTC, by the times Lucid posted.
What was affected?
Lucid named 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.