This incident has been resolved.
The issue affecting front end display updates has been fully addressed, and all systems are operating normally.
If you continue to experience any problems, please contact our support team.
Thank you for your patience while we worked to resolve this issue.
Resolved
This incident has been resolved.
The issue affecting front end display updates has been fully addressed, and all systems are operating normally.
If you continue to experience any problems, please contact our support team.
Thank you for your patience while we worked to resolve this issue.
Identified
We've identified some lingering issues from the earlier database performance issue, specifically as it related to our Graphql API. Specially when new items are created (like new knowledge sources or import tasks) they may not immediately show in the UI despite being created.
We are currently working to relieve this issue.
Resolved
Due to the performance degradation, managed integrations were also affected. Runs importing data into Element sporadically experienced timeout errors, including Ethos-to-Element and CFNC-to-Element integrations. No action is needed as the Element451 Integrations team will be rerunning failed runs for these managed integrations.
Resolved
This incident has been resolved.
The issue affecting web servers has been fully addressed, and all systems are operating normally.
If you continue to experience any problems, please contact our support team.
Thank you for your patience while we worked to resolve this issue.
Identified
We have identified the root cause of the issue affecting our servers.
The issue is caused by an incorrect process change that writes the database on reads, inflating our worker pools. Our team is implementing a fix and working to restore full functionality as quickly as possible.
We will continue to share updates on our progress.
Investigating
We are currently investigating an issue affecting our database.
Users may experience slow load times or failed page loads. Our team has identified the issue and is actively working to determine the root cause.
We will provide an update as soon as we have more information.