Displayr incident
Displayr Documents that use Custom Fonts are failing to load
Displayr experienced a major incident on January 8, 2026 affecting app.displayr.com and australiaeast.displayr.com and 1 more component, lasting 1h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.
- 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.
- resolved Jan 08, 2026, 08:10 AM UTC
This incident has been resolved with the completion of our rollback process.