Displayr Outage History

Displayr is up right now

Displayr had 30 outages in the last 2 years totaling 28h 47m of downtime — averaging 1.2 incidents per month.

There were 30 Displayr outages since June 27, 2024 totaling 28h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.displayr.com

Minor August 7, 2024

Some users have reported Displayr is slow to use

Detected by Pingoru
Aug 07, 2024, 08:06 PM UTC
Resolved
Aug 08, 2024, 07:52 AM UTC
Duration
11h 46m
Affected: app.displayr.comaustraliaeast.displayr.comcanadacentral.displayr.comsoutheastasia.displayr.comwesteurope.displayr.comdisplayr.comR ServersFile Uploads To Displayr
Timeline · 3 updates
  1. investigating Aug 07, 2024, 08:06 PM UTC

    We are investigating the slowness reported by some users.

  2. identified Aug 07, 2024, 11:06 PM UTC

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

  3. resolved Aug 08, 2024, 07:52 AM UTC

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

Read the full incident report →

Minor August 6, 2024

Upload document is failing for some users

Detected by Pingoru
Aug 06, 2024, 10:18 AM UTC
Resolved
Aug 06, 2024, 08:37 PM UTC
Duration
10h 19m
Affected: app.displayr.comaustraliaeast.displayr.comcanadacentral.displayr.comsoutheastasia.displayr.comwesteurope.displayr.comdisplayr.comFile Uploads To Displayr
Timeline · 6 updates
  1. investigating Aug 06, 2024, 10:18 AM UTC

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

  2. investigating Aug 06, 2024, 10:22 AM UTC

    We are continuing to investigate this issue.

  3. identified Aug 06, 2024, 10:34 AM UTC

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

  4. identified Aug 06, 2024, 10:45 AM UTC

    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.

  5. identified Aug 06, 2024, 11:00 AM UTC

    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.

  6. resolved Aug 06, 2024, 08:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2024

Degraded services in all regions

Detected by Pingoru
Jul 30, 2024, 01:44 PM UTC
Resolved
Jul 30, 2024, 03:08 PM UTC
Duration
1h 24m
Affected: app.displayr.comaustraliaeast.displayr.comcanadacentral.displayr.comsoutheastasia.displayr.comwesteurope.displayr.comdisplayr.comR ServersFile Uploads To Displayr
Timeline · 7 updates
  1. monitoring Jul 30, 2024, 01:44 PM UTC

    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.

  2. monitoring Jul 30, 2024, 01:44 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Jul 30, 2024, 02:00 PM UTC

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

  4. monitoring Jul 30, 2024, 02:02 PM UTC

    Microsoft are initiating failover procedures to mitigate impacted workstreams.

  5. monitoring Jul 30, 2024, 02:23 PM UTC

    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.

  6. monitoring Jul 30, 2024, 02:43 PM UTC

    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.

  7. resolved Jul 30, 2024, 03:08 PM UTC

    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.

Read the full incident report →

Notice July 8, 2024

Slow documents and timeout errors in Displayr

Detected by Pingoru
Jul 08, 2024, 06:01 AM UTC
Resolved
Jul 08, 2024, 09:26 AM UTC
Duration
3h 24m
Affected: app.displayr.comcanadacentral.displayr.comsoutheastasia.displayr.comwesteurope.displayr.com
Timeline · 5 updates
  1. investigating Jul 08, 2024, 06:01 AM UTC

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

  2. identified Jul 08, 2024, 06:52 AM UTC

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

  3. identified Jul 08, 2024, 07:54 AM UTC

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

  4. monitoring Jul 08, 2024, 08:54 AM UTC

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

  5. resolved Jul 08, 2024, 09:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 27, 2024

Outage for Displayr customers in the Australia East region

Detected by Pingoru
Jun 27, 2024, 01:32 AM UTC
Resolved
Jun 27, 2024, 03:25 AM UTC
Duration
1h 53m
Affected: australiaeast.displayr.com
Timeline · 3 updates
  1. investigating Jun 27, 2024, 01:32 AM UTC

    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.

  2. monitoring Jun 27, 2024, 01:52 AM UTC

    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.

  3. resolved Jun 27, 2024, 03:25 AM UTC

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

Read the full incident report →