Update - Devops is continuing component deployment to resolve this issue. We will update status again as we have a new ETA, or confirmation of resolution.
Apr 8, 19:01 PDT
Update - Devops has confirmed the issue has been resolved for all environments except us.qubole, for which their ETA is still Thursday.
Apr 6, 12:42 PDT
Update - Devops has implemented several fixes in the Qubole environment during the last 4 days in order to resolve this ongoing outage. At this point they believe there's one component deployment still pending, where they have sorted out the issues related to deployment and will be performing a rigorous testing.
Devops anticipate to get this fix rolled out by Thursday (4/8). This page will continue to be updated as the implementation is completed.
Apr 6, 11:00 PDT
Identified - Devops is implementing several fixes in the Qubole environment today (4.2.2021) and tomorrow (4.3.2021) in order to resolve this ongoing outage. This page will continue to be updated as the implementation is completed.
Apr 2, 15:32 PDT
Update - Devops has identified a potential cause for this issue and is testing a fix in an internal environment. If the fix is successful, this ticket will be updated to reflect the plan to implement the change across Qubole environments.
Mar 31, 13:18 PDT
Update - Devops is continuing to investigate this issue, with the intent to find an immediate workaround.
Mar 30, 11:35 PDT
Investigating - Customers attempting to access notebooks will encounter a "500 Internal Server" error.
Mar 23, 07:13 PDT