Skip to main content

Is Lucid Software Down?

No — Lucid Software is up

Reachable from all 7 checked regions

Average response time: 448ms

Last checked · checks run every 6 hours

Official status page: https://status.lucid.co

Lucid Software uptime

100%
Last 7 days
Last 30 days
Last 90 days
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 5 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

5-day clean streak
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: 100.00% uptime, 22 checks
Aug 20: 100.00% uptime, 39 checks
Aug 21: 100.00% uptime, 26 checks
Aug 22: 100.00% uptime, 25 checks
Aug 23: 100.00% uptime, 23 checks
Aug 24: no data
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
161ms
DNS 0ms TCP 2ms TLS 11ms TTFB 140ms
arn
347ms
DNS 0ms TCP 0ms TLS 7ms TTFB 333ms
bom
879ms
DNS 0ms TCP 1ms TLS 19ms TTFB 847ms
cdg
HTTP 403 · challenge

Answered in 56ms — the origin is serving traffic, it just refused our client.

dfw
232ms
DNS 0ms TCP 1ms TLS 12ms TTFB 212ms
ewr
108ms
DNS 0ms TCP 1ms TLS 10ms TTFB 81ms
fra
1118ms
DNS 0ms TCP 101ms TLS 211ms TTFB 583ms
syd
HTTP 403 · challenge

Answered in 49ms — the origin is serving traffic, it just refused our client.

yyz
291ms
DNS 0ms TCP 12ms TLS 31ms TTFB 221ms

What Lucid Software does

Lucid Software makes visual collaboration tools: Lucidchart for diagrams and flowcharts, Lucidspark for whiteboarding, and Lucidscale for cloud architecture views. Teams use them for system diagrams, process maps and workshops, often embedded in Confluence, Jira or Google Workspace pages. Documents live in Lucid's cloud rather than on disk, so access depends on the service being reachable.

What an outage looks like

The document list fails to load, so existing diagrams cannot be opened even though they are unharmed. The editor stops saving and shows a connection warning, and collaborators stop seeing each other's cursors. Login fails or loops. Lucid diagrams embedded in Confluence or Jira pages render as empty boxes. One Lucid region can be affected while others are fine.

What to do about it

status.lucid.co reports per region and per surface: Document List, Document Editor, User Login and User Settings each appear for US, EU, AUS and Gov, alongside the Lucidchart, Lucidspark, Lucidscale and Lucid.co homepages. Check the region your account is in. If the editor warns that it cannot save, copy your recent changes somewhere else before closing the tab.

Is it down for everyone, or just you?

If this page says Lucid Software is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Lucid Software outage FAQ

Will I lose work if the editor stops saving?
Recent edits are the risk. Lucid saves to its servers, so changes made after saving stops exist only in your browser tab. If you see a connection warning, do not close or refresh that tab. Copy the affected shapes or text into a local note, then wait for the service to recover and confirm the document reflects your changes before closing it.
Diagrams embedded in Confluence show empty boxes. Which service is broken?
Check Lucid before Confluence. Embedded diagrams are fetched from Lucid when the page renders, so a Lucid incident leaves the surrounding page working while the diagram area stays blank. If Lucid's status page is clear and the rest of the Confluence page also fails to load, the problem sits on the Confluence side instead.
My colleague can open documents and I cannot. Why?
Accounts can sit in different Lucid regions, and the status page reports US, EU, AUS and Gov separately for the document list, the editor and login. Two people on one team can therefore see different behaviour during a regional incident. Compare which region each account belongs to before treating it as a local browser or network problem.
Is Lucidspark affected when Lucidchart is down?
Sometimes, because they share the document list, editor and login services the status page tracks. The product homepages are listed separately from those shared components, so a homepage problem is not the same as an editing one. Read the specific component rather than the product name, since the shared layer decides whether you can open and edit anything at all.

How we measure this

  • We request Lucid Software's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Lucid Software publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Lucid Software goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required