Company Logo

Is there an Qubole outage?

Qubole status: Systems Active

Last checked: 4 minutes ago

Get notified about any outages, downtime or incidents for Qubole and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Qubole outages and incidents

Outage and incident data over the last 30 days for Qubole.

There have been 0 outages or incidents for Qubole in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Qubole

Outlogger tracks the status of these components for Xero:

Cluster Operations Active
Cluster Operations Active
Command Processing Active
Command Processing Active
Notebooks Active
Notebooks Active
QDS API Active
QDS API Active
Qubole Community & Support Portal Active
Qubole Scheduler Active
Qubole Scheduler Active
Site Availability Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Quantum Active
Qubole Scheduler Active
Site Availability Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Component Status
Cluster Operations Active
Cluster Operations Active
Command Processing Active
Command Processing Active
Notebooks Active
Notebooks Active
QDS API Active
QDS API Active
Qubole Community & Support Portal Active
Qubole Scheduler Active
Qubole Scheduler Active
Site Availability Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Quantum Active
Qubole Scheduler Active
Site Availability Active
Active
Cluster Operations Active
Command Processing Active
Notebooks Active
QDS API Active
Qubole Scheduler Active
Site Availability Active

Latest Qubole outages and incidents.

View the latest incidents for Qubole and check for official updates:

Updates:

  • Time: April 29, 2021, 1:06 p.m.
    Status: Resolved
    Update: Devops considers the issue resolved at this time.
  • Time: April 27, 2021, 8:49 p.m.
    Status: Monitoring
    Update: Devops is still reviewing a few remaining concerns to ensure this issue is fully resolved.
  • Time: April 23, 2021, 2:55 p.m.
    Status: Monitoring
    Update: Devops has implemented a change as a part of the fix for the Notebooks outage that they believe will also resolve this issue. They are currently monitoring and testing API calls to ensure that all use cases have been covered.
  • Time: April 22, 2021, 1:55 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 22, 2021, 1:47 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: April 15, 2021, 2:13 p.m.
    Status: Investigating
    Update: Devops is currently investigating a potential capacity issue on api.qubole.com that may cause some workloads to stall or fail. Amazon reported an outage on AWS on 4/15/2021 that may be a contributor and which they have since resolved. Devops is still researching the Qubole environment, ongoing, to determine if further correction is needed.

Updates:

  • Time: April 1, 2021, 11:15 a.m.
    Status: Resolved
    Update: Devops has updated the wellness environment to correct this issue.
  • Time: April 1, 2021, 11:15 a.m.
    Status: Resolved
    Update: Devops has updated the wellness environment to correct this issue.
  • Time: March 31, 2021, 8:19 p.m.
    Status: Identified
    Update: Devops is currently implementing a server change on the affected wellness environment that should resolve this issue. This incident will be updated again as soon as that is complete.
  • Time: March 31, 2021, 8:19 p.m.
    Status: Identified
    Update: Devops is currently implementing a server change on the affected wellness environment that should resolve this issue. This incident will be updated again as soon as that is complete.
  • Time: March 30, 2021, 6:34 p.m.
    Status: Identified
    Update: This issue may only impact a small subset of customers on wellness.qubole.com. Devops is confirming a change to get those customers back online.
  • Time: March 29, 2021, 7:19 p.m.
    Status: Identified
    Update: Devops has confirmed the cluster issue with the wellness environment. We're working on gathering internal resources to correct it.
  • Time: March 29, 2021, 7:19 p.m.
    Status: Identified
    Update: Devops has confirmed the cluster issue with the wellness environment. We're working on gathering internal resources to correct it.
  • Time: March 27, 2021, 11:08 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: March 27, 2021, 11:08 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: April 21, 2021, 6:10 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 21, 2021, 6:08 p.m.
    Status: Identified
    Update: Significant progress has been made in resolving the Notebook outage. Each environment that serves Notebooks has been refreshed with new nodes and the Notebooks functionality is successfully responding in AWS. AWS customers will now see Notebooks as available and functional while, in parallel, the Qubole team continues its production testing to confirm stability and true resolution to the outage. We continue to work to restore Notebooks on GCP and will be updating the status page regularly
  • Time: April 19, 2021, 5:43 p.m.
    Status: Identified
    Update: Devops has passed some additional hurdles in final testing of the redeployment on QA. The new deployment is undergoing retesting before being rolled to production.
  • Time: April 15, 2021, 8:32 p.m.
    Status: Identified
    Update: Redeployment is still in process, and expected to finish between today (4/15) and tomorrow. This entry will be updated again as redeployment is finished, or as Devops provides further information.
  • Time: April 14, 2021, 2:20 a.m.
    Status: Identified
    Update: Devops encountered a dependency issue in their attempted fix. They are performing a package rebuild, which will need to be tested tomorrow, Wednesday, before deployment. Devops is attempting to finalize both testing and deployment tomorrow, though deployment may occur on Thursday, 4/15/2021.
  • Time: April 12, 2021, 1:12 p.m.
    Status: Investigating
    Update: Devops resolved a blocking reference error over the weekend. They continue to investigate specific notebook failures on us.qubole.com. At this time a few notebooks appear to be opening normally, though the vast majority still have an issue. Devops is investigating specific failure instances to determine a root cause that will resolve all ongoing failures.
  • Time: April 9, 2021, 2:01 a.m.
    Status: Identified
    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.
  • Time: April 6, 2021, 7:42 p.m.
    Status: Identified
    Update: Devops has confirmed the issue has been resolved for all environments except us.qubole, for which their ETA is still Thursday.
  • Time: April 6, 2021, 6 p.m.
    Status: Identified
    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.
  • Time: April 2, 2021, 10:32 p.m.
    Status: Identified
    Update: 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.
  • Time: March 31, 2021, 8:18 p.m.
    Status: Investigating
    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.
  • Time: March 30, 2021, 6:35 p.m.
    Status: Investigating
    Update: Devops is continuing to investigate this issue, with the intent to find an immediate workaround.
  • Time: March 23, 2021, 2:13 p.m.
    Status: Investigating
    Update: Customers attempting to access notebooks will encounter a "500 Internal Server" error.

Updates:

  • Time: April 21, 2021, 6:10 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 21, 2021, 6:08 p.m.
    Status: Identified
    Update: Significant progress has been made in resolving the Notebook outage. Each environment that serves Notebooks has been refreshed with new nodes and the Notebooks functionality is successfully responding in AWS. AWS customers will now see Notebooks as available and functional while, in parallel, the Qubole team continues its production testing to confirm stability and true resolution to the outage. We continue to work to restore Notebooks on GCP and will be updating the status page regularly
  • Time: April 19, 2021, 5:43 p.m.
    Status: Identified
    Update: Devops has passed some additional hurdles in final testing of the redeployment on QA. The new deployment is undergoing retesting before being rolled to production.
  • Time: April 15, 2021, 8:32 p.m.
    Status: Identified
    Update: Redeployment is still in process, and expected to finish between today (4/15) and tomorrow. This entry will be updated again as redeployment is finished, or as Devops provides further information.
  • Time: April 14, 2021, 2:20 a.m.
    Status: Identified
    Update: Devops encountered a dependency issue in their attempted fix. They are performing a package rebuild, which will need to be tested tomorrow, Wednesday, before deployment. Devops is attempting to finalize both testing and deployment tomorrow, though deployment may occur on Thursday, 4/15/2021.
  • Time: April 12, 2021, 1:12 p.m.
    Status: Investigating
    Update: Devops resolved a blocking reference error over the weekend. They continue to investigate specific notebook failures on us.qubole.com. At this time a few notebooks appear to be opening normally, though the vast majority still have an issue. Devops is investigating specific failure instances to determine a root cause that will resolve all ongoing failures.
  • Time: April 9, 2021, 2:01 a.m.
    Status: Identified
    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.
  • Time: April 6, 2021, 7:42 p.m.
    Status: Identified
    Update: Devops has confirmed the issue has been resolved for all environments except us.qubole, for which their ETA is still Thursday.
  • Time: April 6, 2021, 6 p.m.
    Status: Identified
    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.
  • Time: April 2, 2021, 10:32 p.m.
    Status: Identified
    Update: 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.
  • Time: March 31, 2021, 8:18 p.m.
    Status: Investigating
    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.
  • Time: March 30, 2021, 6:35 p.m.
    Status: Investigating
    Update: Devops is continuing to investigate this issue, with the intent to find an immediate workaround.
  • Time: March 23, 2021, 2:13 p.m.
    Status: Investigating
    Update: Customers attempting to access notebooks will encounter a "500 Internal Server" error.

Updates:

  • Time: March 18, 2021, 10:32 a.m.
    Status: Resolved
    Update: Restarting and updating tunnel servers has resolved this issue.
  • Time: March 17, 2021, 11:38 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: March 17, 2021, 10:49 p.m.
    Status: Identified
    Update: A resolution path appears to be valid and is currently progressing.
  • Time: March 17, 2021, 6:02 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.

Check the status of similar companies and alternatives to Qubole

Smartsheet
Smartsheet

Systems Active

ESS (Public)
ESS (Public)

Systems Active

ESS (Public)
ESS (Public)

Systems Active

Cloudera
Cloudera

Systems Active

New Relic
New Relic

Systems Active

Boomi
Boomi

Systems Active

AppsFlyer
AppsFlyer

Systems Active

Imperva
Imperva

Systems Active

Bazaarvoice
Bazaarvoice

Issues Detected

Optimizely
Optimizely

Systems Active

Electric
Electric

Systems Active

ABBYY
ABBYY

Systems Active

Frequently Asked Questions - Qubole

Is there a Qubole outage?
The current status of Qubole is: Systems Active
Where can I find the official status page of Qubole?
The official status page for Qubole is here
How can I get notified if Qubole is down or experiencing an outage?
To get notified of any status changes to Qubole, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Qubole every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free