Ardoq had 14 outages in the last 2 years totaling 5h 52m of downtime — averaging 0.6 incidents per month.
There were 14 Ardoq outages since October 23, 2025 totaling 5h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 19:20 and 20:00 CEST, some users in the US region may have experienced slow loading times or temporary timeouts while working in workspaces. The issue was identified and resolved at 20:00 CEST, and a permanent fix is being released to prevent it from happening again.
We resolved an issue affecting the Gremlin query engine between August 3 and August 4, 2026, where workspace changes (creates, renames, deletes, and field edits) were not updating in real-time. A fix has been deployed, and automatic data synchronization is fully operational.
We are currently investigating reports of significant latency and browser unresponsiveness across the Ardoq platform. While the issue is most pronounced when accessing Workspace views via the Asset Library, some users are reporting slowness across the entire interface.
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.
Summary: From May 8, 15:00 UTC to May 11, 13:00 UTC, the AI advanced query builder within the reporting module was non-functional. Status: Our engineering team identified the root cause and deployed a fix. All reporting services are now fully operational. We apologize for the interruption to your workflow.
We are currently addressing an issue that is preventing the creation of new Workspaces and Scenarios. We are working to restore this functionality as a priority.
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.
Customers experienced intermittent failures when generating or loading AI-powered reports due to a schema validation issue in the AI tools service. A fix has been deployed and the service is stable.
We are currently investigating an issue where file exports from the Reports section are failing. While Workspace exports remain functional, users may receive a "corrupt file" error when attempting to open exported Excel files from Reports. Our engineering team has identified the cause and a fix is currently being deployed to production. We expect a full resolution within the next few minutes.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently experiencing networking issues in the EU region that are impacting graph functionality for some customers. This is related to an upstream AWS issue. Our team is actively investigating and working to restore full service. We will provide updates as we learn more.
We are experiencing networking issues in the EU region due to an ongoing AWS incident affecting EC2 in EU-WEST-1. AWS has confirmed elevated latencies for network change propagation, which is impacting our ability to spawn new nodes and causing degraded graph functionality for some EU customers. We are monitoring the situation and will provide updates as AWS resolves the underlying issue.
The networking issues in the EU region have been resolved. This incident was caused by elevated latencies for network change propagation in AWS EC2 EU-WEST-1, which has now been resolved by AWS. Service has been fully restored and graph functionality is operating normally for all EU customers. For more details on the underlying AWS incident, see: https://health.aws.amazon.com/health/status
Yesterday, customers in Europe may have experienced intermittent failures or errors when attempting to use AI-powered features. This was due to a confirmed upstream outage with Azure’s AI infrastructure in the Sweden Central region. Incident Duration: Jan 27, 2026, 10:22 CET – Jan 27, 2026, 17:12 CET Impacted Services: Lucidchart Visual Importer: Failed to process or import visuals via AI. Add Dataset With AI: Errors when attempting to generate or structure datasets. ShiftX process / step generation: Intermittent timeouts or failures during automated step creation. Azure mitigated the issue by scaling cluster nodes and adjusting memory to resolve pod crashes in the affected region.
We are currently investigating an issue where the "Chat with us" button in the application menu is unresponsive. We are working to restore the Intercom connection as quickly as possible. Please contact our support team via email if you require immediate assistance.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating a critical issue that is preventing access to all shared presentation links. When these links are opened, they incorrectly show a "Presentation not found" message. We are working to resolve this as quickly as possible.
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.
This incident has been resolved.
We identified and resolved an intermittent issue where newly created presentation slides were consistently showing "No Data" or appearing blank when played. This primarily affected presentations created from scratch. While existing presentations were less impacted, some users may have intermittently seen this issue when adding new slides to them as well.
We are currently investigating an issue where contributor users are incorrectly getting a "Request access" message when trying to answer a survey.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some users experienced an error when attempting to open any existing ShiftX Process. This globally prevented users from viewing or interacting with their key process models. The issue was quickly identified and fully resolved. We apologize for the disruption this caused to your modeling workflow.