Displayr had 17 outages in the last 2 years totaling 43h 12m of downtime — averaging 0.7 incidents per month.
There were 17 Displayr outages since July 7, 2025 totaling 43h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are aware of an issue affecting the Australia East environment where users are seeing the message "System is being upgraded." We are currently investigating the cause.
The issue has been resolved. We apologise for the inconvenience.
We are currently experiencing a service degradation in US regions. Our team is aware and actively investigating. Updates to follow.
We have applied mitigating changes and can confirm that Displayr is now operating normally across US regions.
We’re working on a fix for customers in the US region.
Fix has been applied and we’re monitoring the situation to ensure services remain stable.
All systems are functioning as expected.
We’re investigating an issue where file uploads may take an unusually long time and eventually time out when uploading files to Displayr. This affects both local files uploads as well as impact image uploads. We’ll share updates as we learn more.
We’ve identified that the file upload issue appears to be intermittent and isolated to some users and regions, and may not affect everyone. We’re continuing to scope the impact and are actively monitoring the situation. We’ll continue to provide updates as we learn more.
File uploads are now succeeding for most users, with reliability continuing to improve. We’re downgrading this issue to monitoring while we continue to observe performance.
This incident has been resolved.
Displayr Documents that make use of Custom Fonts from the Displayr Cloud Drive are currently failing to load with an error message that mentions "An item with the same key has already been added.". We are currently investigating the issue and will post another update shortly.
We’ve identified the issue and are rolling back the current release, which we believe will restore normal loading for Displayr documents using custom fonts from the Displayr Cloud Drive. We’ll confirm once the rollback is complete and continue monitoring. Rollback is estimated to be completed within the next 40 minutes.
We believe this issue is triggered when a company’s cloud drive contains duplicate custom font files, which can prevent affected Displayr documents from loading. Our rollback process is continuing.
The rollback is now complete. We’re continuing to monitor, and investigating any dashboards that may still be experiencing loading issues.
This incident has been resolved with the completion of our rollback process.
We are currently investigating this issue. Users are unable to edit or view documents. We have identified a database issue and are investigating further.
We have identified the issue with the database and are making a temporary fix to allow users to edit documents. We expect to have a temporary fix available within 30 minutes.
We have identified the root cause of the issue and are preparing a new release of Displayr with a permanent fix. We expect the release to occur within 60 minutes.
app.displayr.com / East US is fully available again, able to edit and view documents. Other regions are coming online within the next 10 minutes.
Canada Central, South East Asia and West Europe are fully functioning again. Australia East is expected to released within the next 20 minutes.
Australia East is fully functioning. A Displayr release with a permanent fix has now been released to all regions. The incident is resolved.
We are currently investigating this issue, intermittent outages of app.displayr.com resulting in degraded performance and longer loading times, and frequent restarts.
A fix has been implemented; we are seeing recoveries across the system with reduced latencies. We are continuing to monitor.
This incident has been resolved.
We are investigating an issue where the Research Agent’s chart generation is intermittently failing.
A fix has been implemented, and we are currently monitoring system performance to ensure stability and full recovery.
Monitoring confirms that the Research Agent’s chart generation has stabilized and is operating normally. Thank you for your patience while we resolved this issue.
We are currently investigating the issue.
Service has been restored for East US. We are continuing to investigate this issue for Canada.
East US has been reported to still have issues. Our engineers are currently working towards a solution.
We've implemented a fix across regions that has resolved the instability in R calculations. We'll continue to monitor.
We are currently investigating an issue where some of our AI traffic is being flagged by Google as bot traffic. This is causing a small percentage of requests to be rejected. First known occurrence Monday, 6:30pm (AEST) Impact: A limited number of customers may experience rejected requests. Next steps: Our engineering team is actively investigating paths forward. We will provide updates here as we learn more.\
A fix is underway. We've found the impact to be limited for most users, but for a small number of users there will be a noticable impact on the reliability of AI features.
This incident has now been resolved.
Root cause has been found and remediation work is underway.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Triggering functionality within Displayr that leverages AI is experiencing errors. We are investigating.
We identified the issue and made the necessary changes to amend it. All AI features (including Research Agent) are back to being operational.
The team is actively working to resolve the issue where documents fail to open when ZIP files are used as data sets. We appreciate your patience and will share further updates as progress is made.
The issue has been identified and a fix is currently being implemented. We’ll share more details once the resolution is confirmed.
The issue has been successfully resolved. All systems are functioning as expected. Thank you for your patience and support throughout the process.
All R calculations in Australia are returning server errors. Other regions are not affected. We are investigating the issue. We have identified the possible cause of the error and are experimenting with a solution in a test environment before applying this to the production environment in Australia.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. We have modified a cloud resource used by R Servers (Azure Cache for Redis) to enable it to function again. Furthermore we have identified an opportunity to improve cloud alerting so our engineers are notified of this issue in advance and can proactively address the issue prior to affecting customers.
We are currently investigating this issue.
We are continuing to investigate this issue.
We have identified that the unauthorized errors affecting R Server requests are likely caused by an issue with our authorization function. Our team is actively investigating to determine the specific endpoint impacted. We will provide further updates as soon as more information becomes available.
We are continuing to work on a fix for this issue.
We have rolled back the recent R Server promotion in an effort to restore access for users while we continue to investigate the root cause.
We’ve deployed a fix and are currently monitoring to ensure R Server access is fully restored. We will provide another update once stability is confirmed.
This incident has been resolved.
File uploads are intermittently failing due to an incident with one of our third-party providers filestack. Their incident status is reported here: https://status.filestack.com/. Our team is actively monitoring the situation and working closely with the provider to resolve the problem as quickly as possible. We will provide updates as soon as we have more information.
Our team is actively monitoring the situation.
This incident has now been resolved.