Displayr Outage History

Displayr is up right now

Pingoru has recorded 50 incidents for Displayr: 11 in the last 12 months and 0 in the last 90 days.

Source: status.displayr.com

50incidents recorded
11last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Displayr in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202633 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Critical May 26, 2026 Service Disruption – Australia East 3m australiaeast.displayr.com

Started May 26, 2026, 06:49 AM UTC· resolved May 26, 2026, 06:52 AM UTC

  1. investigating May 26, 2026, 06:49 AM UTC

    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.

  2. resolved May 26, 2026, 06:52 AM UTC

    The issue has been resolved. We apologise for the inconvenience.

Read the full incident report →

Major April 20, 2026 Displayr is currently experiencing a service degradation in US regions 46m app.displayr.com

Started Apr 20, 2026, 11:00 AM UTC· resolved Apr 20, 2026, 11:46 AM UTC

  1. investigating Apr 20, 2026, 11:00 AM UTC

    We are currently experiencing a service degradation in US regions. Our team is aware and actively investigating. Updates to follow.

  2. resolved Apr 20, 2026, 11:46 AM UTC

    We have applied mitigating changes and can confirm that Displayr is now operating normally across US regions.

Read the full incident report →

Critical April 17, 2026 Displayr is currently experiencing a service disruption in US regions 1h 51m app.displayr.com, displayr.com

Started Apr 17, 2026, 05:09 PM UTC· resolved Apr 17, 2026, 07:00 PM UTC

  1. investigating Apr 17, 2026, 05:09 PM UTC

    We’re working on a fix for customers in the US region.

  2. monitoring Apr 17, 2026, 05:47 PM UTC

    Fix has been applied and we’re monitoring the situation to ensure services remain stable.

  3. resolved Apr 17, 2026, 07:00 PM UTC

    All systems are functioning as expected.

Read the full incident report →

Major February 5, 2026 File upload slow and timing out 1h 7m File Uploads To Displayr

Started Feb 05, 2026, 12:51 PM UTC· resolved Feb 05, 2026, 01:58 PM UTC

  1. investigating Feb 05, 2026, 12:51 PM UTC

    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.

  2. investigating Feb 05, 2026, 01:13 PM UTC

    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.

  3. monitoring Feb 05, 2026, 01:22 PM UTC

    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.

  4. resolved Feb 05, 2026, 01:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 8, 2026 Displayr Documents that use Custom Fonts are failing to load 1h 11m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Jan 08, 2026, 06:58 AM UTC· resolved Jan 08, 2026, 08:10 AM UTC

  1. investigating Jan 08, 2026, 06:58 AM UTC

    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.

  2. identified Jan 08, 2026, 07:03 AM UTC

    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.

  3. identified Jan 08, 2026, 07:24 AM UTC

    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.

  4. identified Jan 08, 2026, 07:56 AM UTC

    The rollback is now complete. We’re continuing to monitor, and investigating any dashboards that may still be experiencing loading issues.

  5. resolved Jan 08, 2026, 08:10 AM UTC

    This incident has been resolved with the completion of our rollback process.

Read the full incident report →

Critical December 25, 2025 Unable to edit or view documents in Displayr 1h 57m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Dec 25, 2025, 06:10 PM UTC· resolved Dec 25, 2025, 08:07 PM UTC

  1. investigating Dec 25, 2025, 06:10 PM UTC

    We are currently investigating this issue. Users are unable to edit or view documents. We have identified a database issue and are investigating further.

  2. investigating Dec 25, 2025, 06:36 PM UTC

    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.

  3. investigating Dec 25, 2025, 07:04 PM UTC

    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.

  4. investigating Dec 25, 2025, 07:51 PM UTC

    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.

  5. investigating Dec 25, 2025, 07:55 PM UTC

    Canada Central, South East Asia and West Europe are fully functioning again. Australia East is expected to released within the next 20 minutes.

  6. resolved Dec 25, 2025, 08:07 PM UTC

    Australia East is fully functioning. A Displayr release with a permanent fix has now been released to all regions. The incident is resolved.

Read the full incident report →

Major December 5, 2025 app.displayr.com is having intermittent outages 2h 3m app.displayr.com

Started Dec 05, 2025, 11:56 AM UTC· resolved Dec 05, 2025, 02:00 PM UTC

  1. investigating Dec 05, 2025, 11:56 AM UTC

    We are currently investigating this issue, intermittent outages of app.displayr.com resulting in degraded performance and longer loading times, and frequent restarts.

  2. monitoring Dec 05, 2025, 01:16 PM UTC

    A fix has been implemented; we are seeing recoveries across the system with reduced latencies. We are continuing to monitor.

  3. resolved Dec 05, 2025, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 6, 2025 Research Agent Outage 1h 52m AI Servers

Started Nov 06, 2025, 12:55 AM UTC· resolved Nov 06, 2025, 02:47 AM UTC

  1. investigating Nov 06, 2025, 12:55 AM UTC

    We are investigating an issue where the Research Agent’s chart generation is intermittently failing.

  2. monitoring Nov 06, 2025, 01:03 AM UTC

    A fix has been implemented, and we are currently monitoring system performance to ensure stability and full recovery.

  3. resolved Nov 06, 2025, 02:47 AM UTC

    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.

Read the full incident report →

Minor October 29, 2025 Problems loading Displayr 7h 45m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Oct 29, 2025, 04:16 PM UTC· resolved Oct 30, 2025, 12:02 AM UTC

  1. investigating Oct 29, 2025, 04:16 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 29, 2025, 04:22 PM UTC

    There appears to be an issue with Azure Front Door, a CDN used by Displayr. This affects all geographic regions and will result in the following message appearing in Displayr: "Parts of this web page have failed to load due to a problem with your Internet connection." Microsoft has acknowledged an issue and is starting investigation: https://azure.status.microsoft/en-us/status

  3. investigating Oct 29, 2025, 04:39 PM UTC

    Displayr continues to be affected. The latest status update from Microsoft Azure indicates a broad issue with DNS that they are investigating and are starting to take mitigation actions. "Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner." https://azure.status.microsoft/en-us/status

  4. investigating Oct 29, 2025, 05:25 PM UTC

    Microsoft has found the issue is related to a bad change to Azure Front Door (the CDN that Displayr uses) and is rolling back to a last good configuration. "Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update."

  5. investigating Oct 29, 2025, 07:25 PM UTC

    Microsoft has issued another update with an expected resolution time: "At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted." https://azure.status.microsoft/en-us/status

  6. monitoring Oct 29, 2025, 08:31 PM UTC

    We are seeing systems recover. You should be able to log in and edit or view documents. However, there are still issues with specific systems. In particular, you may not be able to view visualizations as these also have a reliance on Azure Front Door and are still experiencing issues. The status from Azure has not changed, and we expect a full recovery by 23:20 UTC on 29 October 2025.

  7. monitoring Oct 29, 2025, 08:40 PM UTC

    Systems are recovering more widely. You should be able to log in and edit or view documents, and also visualizations now work. There are still intermittent issues. Occasionally you may still see "Parts of this web page have failed to load" however it should occur less often. The status from Azure has not changed, and we expect a full recovery by 23:20 UTC on 29 October 2025.

  8. resolved Oct 30, 2025, 12:02 AM UTC

    We have observed that all Azure Front Door (AFD) instances used by Displayr have now recovered. Microsoft continues to roll out fixes to all customers. However based on their advice since our specific Azure Front Door instances have now recovered they should continue to operate reliably. The incident is now resolved for Displayr. "The AFD service is now operating above 98% availability. While the majority of customers and services are mitigated or seeing strong improvement across affected regions, we are continuing to work on tail-end recovery for remaining impacted customers and services. We have revised our mitigation time and are currently tracking toward full mitigation by 00:40 UTC on 30 October 2025, though we will communicate if mitigation is achieved sooner." https://azure.status.microsoft/en-us/status

Read the full incident report →

Major October 24, 2025 R calculations in Canada and East US regions have degraded performance 8h 42m R Servers

Started Oct 24, 2025, 01:44 PM UTC· resolved Oct 24, 2025, 10:26 PM UTC

  1. investigating Oct 24, 2025, 01:44 PM UTC

    We are currently investigating the issue.

  2. investigating Oct 24, 2025, 07:28 PM UTC

    Service has been restored for East US. We are continuing to investigate this issue for Canada.

  3. investigating Oct 24, 2025, 07:49 PM UTC

    East US has been reported to still have issues. Our engineers are currently working towards a solution.

  4. resolved Oct 24, 2025, 10:26 PM UTC

    We've implemented a fix across regions that has resolved the instability in R calculations. We'll continue to monitor.

Read the full incident report →

Minor October 1, 2025 AI Servers experiencing degraded service 4h 11m AI Servers

Started Oct 01, 2025, 07:49 AM UTC· resolved Oct 01, 2025, 12:01 PM UTC

  1. identified Oct 01, 2025, 07:49 AM UTC

    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.\

  2. identified Oct 01, 2025, 10:52 AM UTC

    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.

  3. resolved Oct 01, 2025, 12:01 PM UTC

    This incident has now been resolved.

Read the full incident report →

Major September 28, 2025 Displayr is currently experiencing a reduction service 14m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Sep 28, 2025, 10:23 PM UTC· resolved Sep 28, 2025, 10:38 PM UTC

  1. investigating Sep 28, 2025, 10:23 PM UTC

    Root cause has been found and remediation work is underway.

  2. identified Sep 28, 2025, 10:25 PM UTC

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

  3. resolved Sep 28, 2025, 10:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 26, 2025 Research Agent and other AI Related Features not working 39m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Aug 26, 2025, 03:31 PM UTC· resolved Aug 26, 2025, 04:10 PM UTC

  1. investigating Aug 26, 2025, 03:31 PM UTC

    Triggering functionality within Displayr that leverages AI is experiencing errors. We are investigating.

  2. resolved Aug 26, 2025, 04:10 PM UTC

    We identified the issue and made the necessary changes to amend it. All AI features (including Research Agent) are back to being operational.

Read the full incident report →

Major August 5, 2025 Documents fail to open when ZIP files are used as data sets 1h 3m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Aug 05, 2025, 09:37 AM UTC· resolved Aug 05, 2025, 10:40 AM UTC

  1. investigating Aug 05, 2025, 09:37 AM UTC

    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.

  2. identified Aug 05, 2025, 09:44 AM UTC

    The issue has been identified and a fix is currently being implemented. We’ll share more details once the resolution is confirmed.

  3. resolved Aug 05, 2025, 10:40 AM UTC

    The issue has been successfully resolved. All systems are functioning as expected. Thank you for your patience and support throughout the process.

Read the full incident report →

Major July 31, 2025 R calculations in Australia returning errors 40m australiaeast.displayr.com, R Servers, R Servers

Started Jul 31, 2025, 07:14 AM UTC· resolved Jul 31, 2025, 07:55 AM UTC

  1. investigating Jul 31, 2025, 07:14 AM UTC

    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.

  2. monitoring Jul 31, 2025, 07:35 AM UTC

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

  3. resolved Jul 31, 2025, 07:55 AM UTC

    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.

Read the full incident report →

Critical July 31, 2025 Unauthorized Error on R Servers 1h 23m R Servers, R Servers

Started Jul 31, 2025, 03:59 AM UTC· resolved Jul 31, 2025, 05:23 AM UTC

  1. investigating Jul 31, 2025, 03:59 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 31, 2025, 04:00 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 31, 2025, 04:03 AM UTC

    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.

  4. identified Jul 31, 2025, 04:04 AM UTC

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

  5. identified Jul 31, 2025, 04:30 AM UTC

    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.

  6. monitoring Jul 31, 2025, 04:46 AM UTC

    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.

  7. resolved Jul 31, 2025, 05:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2025 File uploads intermittently failing 7h 37m File Uploads To Displayr

Started Jul 07, 2025, 12:49 AM UTC· resolved Jul 07, 2025, 08:26 AM UTC

  1. investigating Jul 07, 2025, 12:49 AM UTC

    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.

  2. monitoring Jul 07, 2025, 12:49 AM UTC

    Our team is actively monitoring the situation.

  3. resolved Jul 07, 2025, 08:26 AM UTC

    This incident has now been resolved.

Read the full incident report →

Notice May 26, 2025 Displayr is not operational in Canada Central region 17m canadacentral.displayr.com

Started May 26, 2025, 03:51 AM UTC· resolved May 26, 2025, 04:08 AM UTC

  1. investigating May 26, 2025, 03:51 AM UTC

    We are currently investigating this issue.

  2. investigating May 26, 2025, 04:08 AM UTC

    We are continuing to investigate this issue.

  3. resolved May 26, 2025, 04:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2025 Degraded performance for Comments in Displayr across all regions 10m app.displayr.com, Displayr Wiki, Q Wiki, australiaeast.displayr.com and 3 more

Started Mar 18, 2025, 11:59 PM UTC· resolved Mar 19, 2025, 12:10 AM UTC

  1. investigating Mar 18, 2025, 11:59 PM UTC

    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.

  2. investigating Mar 19, 2025, 12:09 AM UTC

    Services have now been restored.

  3. resolved Mar 19, 2025, 12:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 27, 2025 Displayr Documents failing to load 1h app.displayr.com

Started Jan 27, 2025, 04:30 AM UTC· resolved Jan 27, 2025, 05:30 AM UTC

  1. resolved Jan 27, 2025, 04:40 AM UTC

    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.

Read the full incident report →

Major January 21, 2025 Q Licensing Page Unavailable 1h 48m Q Licensing

Started Jan 21, 2025, 10:53 AM UTC· resolved Jan 21, 2025, 12:41 PM UTC

  1. investigating Jan 21, 2025, 10:53 AM UTC

    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.

  2. resolved Jan 21, 2025, 12:41 PM UTC

    The Q Licensing is now fully operational.

Read the full incident report →

Notice November 20, 2024 R calculations were not working for Q users – R Servers

Started Nov 20, 2024, 04:49 PM UTC· resolved Nov 20, 2024, 04:49 PM UTC

  1. resolved Nov 20, 2024, 04:49 PM UTC

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

Read the full incident report →

Minor November 19, 2024 View mode in Displayr doesn't render certain items properly 2h 17m app.displayr.com, australiaeast.displayr.com, canadacentral.displayr.com, southeastasia.displayr.com and 1 more

Started Nov 19, 2024, 06:33 PM UTC· resolved Nov 19, 2024, 08:51 PM UTC

  1. identified Nov 19, 2024, 06:33 PM UTC

    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.

  2. identified Nov 19, 2024, 07:49 PM UTC

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

  3. resolved Nov 19, 2024, 08:51 PM UTC

    This incident has been resolved.

Read the full incident report →