Vendor-reported status observed by INTERNETMON
Lucid status
Lucid · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
24
Retained
24
Affected retained
0
Projection scope: complete · 24 retained of 24 reported components across 5 source groups.
Document List (US)
Group: US Region
Operational
Lucidchart Homepage
Group: Homepage
Operational
Document List (EU)
Group: European Region
Operational
Document List (AUS)
Group: Australian Region
Operational
Document List (Gov)
Group: US Government Environment (lucidgov.app)
Operational
Document Editor (US)
Group: US Region
Operational
Document Editor (EU)
Group: European Region
Operational
Document Editor (AUS)
Group: Australian Region
Operational
Lucidspark Homepage
Group: Homepage
Operational
Document Editor (Gov)
Group: US Government Environment (lucidgov.app)
Operational
User Login (US)
Group: US Region
Operational
User Login (EU)
Group: European Region
Operational
User Login (AUS)
Group: Australian Region
Operational
Lucidscale Homepage
Group: Homepage
Operational
User Login (Gov)
Group: US Government Environment (lucidgov.app)
Operational
Lucid.co Homepage
Group: Homepage
Operational
User Settings Page (Gov)
Group: US Government Environment (lucidgov.app)
Operational
User Settings Page (US)
Group: US Region
Operational
User Settings Page (EU)
Group: European Region
Operational
User Settings Page (AUS)
Group: Australian Region
Operational
Showing 20 of 24 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 177.67 ms feed latency
Operational
HTTP 200 · 298.51 ms feed latency
Partial Outage
HTTP 200 · 88.72 ms feed latency
Operational
HTTP 200 · 92.77 ms feed latency
Operational
HTTP 200 · 152.01 ms feed latency
Operational
HTTP 200 · 214.58 ms feed latency
Operational
HTTP 200 · 201.38 ms feed latency
Operational
HTTP 200 · 200.97 ms feed latency
Operational
HTTP 200 · 288.08 ms feed latency
Operational
HTTP 200 · 225.32 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
223.69 ms
JSON source