Our developers have been monitoring this issue for 48 hours and this incident is being updated to resolved.
May 6, 14:27 PDT
We have confirmation that the root cause of the SSL issues have been resolved by the appropriate vendors. Our internal testing aligns with that confirmation. Data Analysis and Standalone Looker statuses are being updated to operational!
Our developers are closely monitoring our systems. Monitoring related to this incident will continue into the weekend.
May 4, 13:30 PDT
Overnight, our developers met the targeted progress toward a permanent solution in the test environment. Work to apply and test the solution in the live environment will continue throughout the day. Please expect intermittent impact to access for Data Analysis and Standalone Looker throughout the day today on all browsers as our developers prioritize delivery of the permanent fix.
We will provide another update here no later than 4:00pm ET this afternoon.
May 4, 05:35 PDT
Work to attend to this issue for Google Chrome browsers will continue into the evening and overnight. We will provide an update here asap Wednesday morning (5/4/22).
There is no reported issue when accessing Data Analysis and Standalone Looker using a browser other than Google Chrome; such as Firefox or Safari.
May 3, 16:00 PDT
In response to the ongoing incident titled "SSL Issues on Looker Nodes Being Investigated" - our developers have communicated the need for immediate maintenance to attend to intermittent issues being reported and experienced and to mitigate future occurrences.
The maintenance will begin immediately and may last throughout the day. Some users may experience intermittent loss of access to data analysis during the time of this maintenance.
We apologize for any negative impacts while we prioritize a fix.
May 3, 08:45 PDT
We have identified this issue is with our certificate authority and Google Chrome. This should be resolved within a couple hours. In the mean time, you can get around this issue by using a browser other than Google Chrome such as Firefox or Safari.
May 2, 14:49 PDT
We are currently investigating the cause of this issue and will update this page once we have more information.
May 2, 13:15 PDT