Qubole incident

Jupyter Notebook Launch issue on us and api qubole environment

Critical Resolved View vendor source →

Qubole experienced a critical incident on January 4, 2022 affecting Notebooks and Notebooks, lasting 15h 18m. The incident has been resolved; the full update timeline is below.

Started
Jan 04, 2022, 10:48 PM UTC
Resolved
Jan 05, 2022, 02:07 PM UTC
Duration
15h 18m
Detected by Pingoru
Jan 04, 2022, 10:48 PM UTC

Affected components

NotebooksNotebooks

Update timeline

  1. investigating Jan 04, 2022, 10:48 PM UTC

    We have identified a Jupyter Notebook launch issue on the us and api qubole environments. Our DevOps team is investigating this issue and will be providing progress updates.

  2. identified Jan 05, 2022, 01:01 PM UTC

    DevOps team identified there is an issue with the Asterix cluster while processing the request of the jupyter notebooks. they are suggesting a workaround to disable the Asterix flag.

  3. resolved Jan 05, 2022, 02:07 PM UTC

    DevOps provided a workaround by disabling the offline edit option via asterix in the account level and the jupyter seems to be working fine without any issues.