Is Displayr Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

Services have now been restored.

We are currently investigating a problem which has resulted in: * Degraded performance for the Comments system in Displayr (ability to add comments to pages) * Inability to access the Wiki portion of the Displayr documentation. * Inability to access the Wiki portion oft the Q documentation. We will provide more information as it becomes available.

We identified an issue where for US based Displayr customers, documents failed to load and new documents could not be created. The incident was identified at 2.30pm AEST and resolved by 3.30pm AEST.

The Q Licensing is now fully operational.

We are currently experiencing an issue that has rendered the Q Licensing unavailable. Our team of engineers is actively investigating the problem and working diligently to resolve it as quickly as possible.

Due to a network configuration error, some Q users in the US regions were not able to execute R calculations. This is now resolved.

This incident has been resolved.

We're continuing to roll out a fix for the issue across regions.

We have identified that, in some cases, visualisations and R results do not render correctly in view mode. We have discovered a root cause and we're working to fix this.

We have identified that the issue is related to the specific data sets used in two customer documents, and is not affecting the general Displayr application.

Some users are reporting documents are taking a long time to load. We are currently investigating this issue.

We have resolved the issue, and ready-made variables are able to be created as expected.

We've identified the issue, fix in progress. ETA is 1hr.

An error is thrown when creating ready-made variables from a selection in the data tree. We are currently putting a fix in place.

This incident has been resolved.

We are continuing investigation. It appears that the issue is for documents that use the Scheduler feature.

We have received reports of documents not loading in Displayr and are investigating. We will update this message as soon as we have identified the extent of the problem.

We have released a fix for the slowness issue observed. This incident is now resolved.

We have identified the root cause of the slowness and our engineering teams are working on a fix

We are investigating the slowness reported by some users.

This incident has been resolved.

The issue affects only European users. The workaround would be to use a URL to upload files. Uploading to Google Drive, Dropbox can also provide a direct URL. Use this URL to upload files to Displayr. Instructions here - https://help.displayr.com/hc/en-us/articles/360003480616-How-to-Import-Data-or-Tables-via-URL We will update the status page as soon as we hear from Filestack.

We have raised the issue with Filestack; in the interim, the workaround would be to upload files using URL, R Code, API and Survey Platforms.

The issue has been identified with Filestack, a third-party service that Displayr uses to upload files.

We are continuing to investigate this issue.

Some customers have reported that they are unable to upload QPacks and datasets. We are investigating this.

This incident appears to be resolved. Microsoft will continue to monitor impacts to Azure but our data suggests that our services are stable, and operational.

We've found that the greatest impacts have been on page load/route changes and data suggests that degradation has improved. We will monitor further for confirmation that this has been resolved.

We are beginning to see signs of recovery for this issue. We will continue to monitor until Microsoft confirms that the issue has been resolved.

Microsoft are initiating failover procedures to mitigate impacted workstreams.

We have identified increased error rates in communications on our servers. This can lead to issues when interacting with and loading dashboards.

We are continuing to monitor for any further issues.

Azure is reporting a widespread network issue globally. This is impacting our Displayr services and you may encounter situations where pages don't load correctly, or are missing assets.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The team encountered an unexpected delay and should know about the status of the fix within around 40 minutes.

We are currently attempting a fix for the above issue. We should know more about the progress in roughly 50 minutes.

We are currently investigating reports of actions in Displayr documents taking much longer than usual and customers encountering timeout errors.

Microsoft Azure had network problem for our region which has now been resolved.

Customers in Australia East should be able to access documents again, but some pages may take longer to load than normal. We are continuing to monitor the situation.

Displayr is not currently accessible for customers on the Australia East Displayr region. It looks to be related to an network problem with Microsoft Azure.

No further connection problems for Displayr in South East Asia have been detected.

We have detected some intermittent connection problems with Displayr in South East Asia. The situation looks to be improving and we are monitoring.

The incident has been resolved.

A fix has been implemented and we are monitoring

We are continuing to investigate this issue.

We are currently investigating a Displayr outage, which is affecting customers in all Displayr regions.

Microsoft have confirmed that they service has been restored to normal and there should be no further disruption to Displayr users as a result of this outage.

Microsoft Azure, who host the Displayr application and supporting infrastructure, have reported an outage. There are signs that Microsoft is recovering, and that Displayr users are able to access documents again. We are monitoring the progress from Microsoft, and are preparing a contingency plan if Microsoft are not able to fully restore the service soon.

We have identified a problem with the Displayr database. The team is attempting to fix this issue. We expect the fix to be complete within two hours.

We are currently investigating a Displayr outage which is affecting customers in all Displayr regions.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This problem has now been resolved.

We have identified the cause of the problem and are working on a fix. We expect the problem to be resolved within 20 minutes.

We are investigating a problem with R Calculations that is affecting Displayr and Q customers who use our Southeast Asia regional servers.

The problem has now been resolved and all documents are loading.

Problems with document loading are still persisting for some documents. We are attempting an alternative fix to this issue.

A fix has been implemented and published documents are opening now. We are monitoring to ensure there are no more issues.

We are attempting a fix for the above issue and expect it to be resolved within 15 minutes

We are currently investigating a problem that is preventing some Displayr documents from opening in View mode (that is, published reports and dashboards. Some documents in Edit mode may also be affected.

Users should no loner experience time-outs on the My Reports and Settings pages.

We are investigating slowness in the loading of the My Reports and Settings pages, which lists the documents in an account, for users in Western Europe.

Displayr functionality is back to normal.

Displayr documents are loading for users in Western Europe again.

We are continuing to work on a fix for this issue.

Users on Western Europe Displayr users are currently unable to access Displayr. The team is investigating now.

This issue has been resolved.

The team is attempting to implement a measure to alleviate this problem.

We are continuing to investigate this issue.

Displayr is currently experiencing degraded service in all regions. Users may intermittently not be able to access documents or pages. The team is currently investigating.

Service has been returned to normal.

Displayr users in our West Europe and Southeast Asian regions are currently experiencing intermittent degraded service. The Displayr team are currently working on a fix and we expect the issue to be resolved within 30 minutes.

Displayr experienced an outage in all regions from approximately 2:25AM UTC through 2:35AM UTC. All services have been restored.

Documents were unable to be viewed or edited in Displayr. The problem occurred due to an upstream problem with our feature flagging provider: https://flagsmith.statuspage.io/incidents/3c4k9hpz7m3z The issue was automatically resolved after approximately 20 minutes when the upstream problem was fixed. An engineering ticket has been created to improve our error handling so such an issue will not prevent documents from being edited or viewed in future.

This incident has been resolved.

A workaround has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

The fix has been applied to all regions. We will continue to monitor the issue until it has been confirmed that exporting works for the affected users.

We have begun rolling out the fix one region at a time, all regions are expected to be resolved within 20 minutes.

Documents are unable to be exported to Excel, PowerPoint, or PDF. Our engineers have identified the cause of the issue and have a solution. Our engineers are working on releasing a new version of Displayr with the solution within the next few hours.

Documents are able to be exported again. Please note that we are aware of a separate issue with regards to exported file names. Typically when Displayr exports a file, the file will be named after the document title or the page title, however at the moment they are named using a randomly generated ID. This will be addressed in a future release of Displayr.

The release is still pending, our current estimate is it will be released in 30 minutes.

A new version of Displayr is being released with a solution, and will be available in approximately 1 hour.

Documents are unable to be exported to Excel, PowerPoint, or PDF in Chrome and Safari browsers. Our engineers have identified the cause of the issue and have a solution. A workaround is to export in Edge or Firefox. Our engineers are working on releasing a new version of Displayr with the solution within the next few hours.

Due to system maintenance, the public IP address of Displayr East US (app.displayr.com) has changed from 40.76.201.22 to 74.235.1.135 If you rely on the public IP address for firewall rules in your database servers (if those databases are imported as SQL data sets into Displayr), please update your firewall rules to use the new IP address. Further information can be found at https://docs.displayr.com/wiki/Displayr_Outbound_IP_Address

The issue with Single Sign On is now resolved.

Customers with a custom subdomain that use Single Sign On are currently unable to re-authenticate. If customers have already signed in for a session prior to now, they will remain logged in. This will be resolved in approximately 30 minutes.

This incident has been resolved.

All virtual machines used for document editing and viewing are online and functioning again. Normal operations have resumed in West Europe.

We have identified an issue in the cloud infrastructure that hosts documents for editing and viewing. All virtual machines were not responding. We are manually bringing more virtual machines online. Documents will be available for editing and viewing now, however the performance will be degraded for another 10-20 minutes.

Users in West Europe are unable to edit or view documents. We are investigating the issue.

Microsoft have resolved the issue, and documents are now loading in the Australia East region.

Since 6:30pm 2023/08/23 AEST Azure has been experiencing intermittent issues in the Australia East region. This is preventing displayr documents from being loaded in that region. Microsoft is working to resolve this issue.

Our storage provider has resolved the issue. Internal testing confirms this.

We are aware of errors when attempting to upload datasets and/or files to Displayr. This issue is being investigated and updates will be posted here.

app.displayr.com was taking 30+ seconds or more to load web pages or to respond to actions within documents. The problem was due to Azure CDN infrastructure. The problem was resolved by passing Azure CDN while the root cause is resolved in Azure CDN. The issue was resolved within 20 minutes.

This incident with the Microsoft Azure CDN was resolved in the background by Microsoft without intervention of Displayr. Displayr will conduct a review of what can be improved regarding our use of Azure CDN to help discover more information on these types of issue in future and to optimize our ability to escalate the issue within Microsoft Azure.

If you are experiencing a "connection problem" or "internal server error" with error code 500 when accessing Displayr in the East US region, this is due to a Microsoft Azure CDN issue. Retrying may help as the CDN should repair over time. To bypass the CDN, when you open a Document in the address bar can may use https://displayr-app.displayr.com/ instead of https://app.displayr.com/ If you continue to experience errors, using Google Chrome or Edge, please capture a HAR file of the error using the instructions contained in this article and send it to support@displayr.com https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting

The R Servers in South East Asia region have now automatically recovered thanks to Microsoft Azure repairing the data center. This work is still on-going however Displayr's Azure resources in the data center have recovered and there is little risk that they will revert. In terms of what Displayr could do to avoid this type of incident in future: our typical disaster recovery option would to have been to move the R Servers to an alternative region or zone in Azure that is within the same country (Singapore). Unfortunately there are no other Azure data centers available that could be used as a disaster recovery option, and all zones within the data center were affected. An incident affecting an entire data center is highly unusual. This is the first time this incident has occurred since Displayr launched the South East Asia region in February 22, 2022. We have determined the risk of a similar incident occurring in future as very low.

In regards to the South East Asia issue with R calculations, we are waiting for Azure to resolve the issue in the data center. All attempts to create separate R Servers in the same region have failed due to issues that impact the entire region. Please monitor the event "Datacenter Cooling Event - Southeast Asia" at https://azure.status.microsoft/en-gb/status A workaround is available for customers that are affected in South East Asia and are not concerned with data sovereignty or data locality. The following steps will cause your data to leave South East Asia and be sent to the Australia East region. Only follow these steps if you accept the consequences of the data leaving your region. 1. Edit your Displayr document. 2. Wait for your document to load. 3. In the address bar of your browser, copy and paste the following line and press Enter javascript:SeleniumTesting.QServerRequestsCommon.SetRServer({Request:"SetRServer",ServerName:"reausprod.displayr.com"}) 4. The R Server for your document will have been temporarily changed to the Australia East region R Server. Any R calculations will now work. 5. You may have to repeat these steps after 10 minutes of inactivity.

The issue is occurring due to an incident in the Azure South East Asia Data Center. Azure is still working on restoring services and they currently do not have an ETA. Here is a copy of their message: > We do not have an exact ETA at this time, we currently expect an extended period of time to fully restore all cooling capacity. The Azure service recovery process will commence at this time and is expected to progressively return over a number of hours https://azure.status.microsoft/en-gb/status In the meantime, we are experimenting with a possible workaround.

R calculations in the South East Asia region are taking a long time and then returning an error such as "There is a problem with your Internet connection that prevented the calculation from completing." We are investigating the cause of the errors. Other regions are not affected.

This incident has been resolved.

We have applied a workaround to bypass the Azure CDN. Performance should now be back to normal. We continue to work with Microsoft Azure to identify the issue with the Azure CDN so we can return to using it in future.

We are investigating a work-around for the issue via bypassing the Microsoft Azure CDN.

We are continuing to investigate this issue.

Since 8am CST this morning we have received reports with web pages on app.displayr.com being slow to load. We have isolated the issue to the Microsoft Azure CDN that is used to load our website assets. The CDN is operating very slowly for customers in North America and South America. Other regions do not appear to be affected at this time. We are working with Microsoft Azure to resolve this issue. Our current advice is that you should wait (up to 4 minutes) and the web page should eventually load and then it will continue to work after that, as it falls back to a working resource. So for example, if you edit a document, it may take several minutes to load, but after loading, the editing of the document will be unaffected.

This incident has been resolved in all regions.

Editing documents should now function as normal.

A fix has been implemented and service is being restored.

The issue has been identified and a fix is being implemented. All existing published documents/dashboards remain accessible for users to view, however they cannot be edited or re-published.

We are currently investigating this issue.

A new version of Displayr has been released which ensures that documents with custom fonts can again be edited without issue. We will be conducting a post incident review to improve our systems and avoid problems of this same nature from occurring again.

The temporary fix has been rolled out to all regions. All documents with custom fonts should be working again now. Please refresh your web browser if experiencing errors. A new release of Displayr is planned within the next hour with a permanent fix.

The temporary workaround is currently being rolled out to all regions. Please refresh your web browser if experiencing errors.

We are preparing a temporary workaround within the next hour that will fix this issue for the majority of documents. A new release of Displayr with a permanent solution is being prepared for release within the next several hours.

A problem is occurring when editing documents that use custom fonts.

We are currently investigating this issue.

This incident has been resolved.

The Displayr home page search bar (https://www.displayr.com/search/) is not returning any search results. This is under investigation. The home page search bar searches blog posts, the Help Center, and the Displayr wiki. In the meantime, please search our resources in the following ways: <h2>Help Center</h2> Please search directly in the Help Center until the issue is resolved: https://help.displayr.com/hc/en-us <h2>Blog Posts</h2> Please perform a Google search with the prefix <tt>site:www.displayr.com</tt>. So to search for statistical testing, you would search for <tt>site:www.displayr.com statistical testing</tt> <h2>Wiki</h2> Please perform a Google search with the prefix <tt>site:docs.displayr.com</tt>. So to search for statistical testing, you would search for <tt>site:docs.displayr.com statistical testing</tt>

This incident has been resolved.

We have a known issue with our Australian PayPal account and we are working hard to get it resolved. This issue is preventing customers from paying us via PayPal. Bank transfers and other alternative payments continue to operate. Our support and accounts department are doing their best to ensure you continue to have access to your licenses during this time. If you have been affected by being unable to pay, please contact us at https://help.displayr.com/hc/en-us/requests/new

This issue has been resolved and was related to a temporary outage in our upload infrastructure providers.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

A new version of Displayr has been released with a fix. All documents are opening again.

The Displayr release process has started, so a new version with a fix should be available shortly. Please contact support@displayr.com if you have any critical documents that cannot be opened, as there is a manual process our support team can perform to repair your document. However, the new version should be available within 1.5 hours, and any documents should be automatically fixed afterwards.

The issue has been identified. The problem occurs when opening documents containing a table which had its text alignment or vertical alignment modified from the default setting. A fix is being prepared and we will release a fixed version of Displayr soon.

We are currently investigating this issue.

The incident has been resolved. There was an issue affecting roughly 13% of documents in Displayr (both editing and published documents) in the US region. There would be long waiting times followed by "A connection error has occurred". There was an issue with an Azure API that was reporting wrong information, causing documents to be stuck. Engineers will track diagnostic information about this API in the short term to more quickly identify when the problem occurs and resolve it manually, and in the long term we are making a technical plan to move to a more reliable Azure service.

We are currently investigating this issue.

Microsoft has put backup DNS servers into operation, and this appears to have resolved the problem.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Serious problems on all services. The problems appear to be related to a DNS problem, which Microsoft Azure is investigating.

A new version of Displayr has been released and the affected buttons are working again.

When inserting a new data set, the following buttons do not work: Google Drive, Dropbox, Box, OneDrive. We have a fix for this issue that is planned to be released within a few hours. In the meantime, please use the My Computer button to upload these files.

This incident has been resolved.

We are continuing to investigate this issue.

app.displayr.com is experiencing a slowdown

This incident has been resolved.

We are continuing to investigate this issue.

Some web pages on www.displayr.com are experiencing errors, particularly blog posts and guides. This does not affect the Displayr app (app.displayr.com), which is fully functional as it runs on a separate server.

This incident has been resolved.

We are currently investigating this issue.