8 Lucidchart incidents · Cʼhwevrer 2019 — official updates, affected components, duration and resolution details.
We are currently investigating an incident affecting lucid.app
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating the issue.
We have identified the root cause of the issue and are working to resolve it.
A fix has been implemented and we are monitoring the results.
After monitoring, the fix has partially resolved the incident. We are actively working to fully resolve the incident.
A second fix is implemented and we are monitoring for further issues.
This incident has been resolved.
We are currently investigating instability with lucid.app
We have identified the root cause for the instability and are working on a fix.
A fix has been implemented and we are monitoring to make sure the incident is fully resolved.
This incident has been resolved
Our document service slowed down for a few seconds and then recovered. We are investigating the root cause.
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.
At 4:56 a.m. Mountain Time our Lucidchart services entered into a degraded state, causing users to be inconsistently able to access or edit diagrams. Our system immediately alerted us to these errors and our engineers began working on a fix until we were able to get our document services up and running again within 2 hours. We have identified the root cause as a misconfigured thread pool. We have fixed the thread pool and have also started an internal audit to ensure that we do not have any other thread pools in a similar state.
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.