- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Lucid. 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-12 12:15 UTC and 2019-02-12 12: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
- resolved
At 2:22 p.m. Mountain Time one of our central load balancers entered into a degraded state causing 1/12 of our internal network traffic to be impacted. We identified the degraded load balancer and have removed it out of service. We have also created additional monitoring to ensure that this type of issue does not happen again.
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-ff8f379781
Is Lucid still down?
No, this incident was resolved 2019-02-12 12:15 UTC. For Lucid's live state, see https://down.guide/lucid.
How long did it last?
0m, from 2019-02-12 12:15 UTC to 2019-02-12 12:15 UTC, by the times Lucid posted.
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.