← Back to Okta History
unknown✓ Resolved

Resolved Service Degradation

Okta•
Status
resolved
Duration
Duration unavailable
Updates
1
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
We are aware of slow dashboard load times on Google Chrome version 77. We are investigating this issue and will update this message with more information as soon as we have it. ========================== Resolved: The issue with Google Chrome version 77 (on both desktop and Android) which was due to a change introduced in Google Chrome version 77 is now resolved on all Cells. Additional root cause information will be provided within 48 business hours. ========================== Root Cause Analysis: On Sept 30th, at approximately 3:39PM PDT, customers reported experiencing longer than expected load times for application logos in the Okta end-user dashboard and catalog. Upon investigation, Okta determined users in all cells experienced the longer load times after updating their Chrome browser to version 77.0.3865.75 (Official Build) (64-bit). Users of browsers other than Chrome, and users of Chrome earlier than version 77, were not impacted. Okta discovered that Chrome version 77 caused a performance regression with some HTML Canvas operations when the hardware acceleration setting was available and enabled. This behavior is also discussed in the Chromium bug forum as Issue 1001845. At approximately 8:40PM PDT on Sept 30th, Okta started the phased deployment of a workaround, per-cell basis, which was completed on all cells by 10/1/2019 at 6:40 PM PDT. During the incident, users were advised to workaround the issue by disabling Hardware Acceleration. This workaround is no longer necessary and Hardware Acceleration in Chrome can be re-enabled.

📊 TECHNICAL DETAILS

Internal ID
86cb3c4e-aed0-4ca5-8ae0-93e1531417e1
External ID
https://www.salesforce.com/a9C1Y0000004DyLUAU
🕐 First reported
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
Duration unavailable
Total Duration
1
Recorded Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed