Company Logo

Is there an Qubole outage?

Qubole status: Systems Active

Last checked: 5 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: March 14, 2022, 4:56 a.m.
    Status: Resolved
    Update: The issue has been resolved.
  • Time: March 14, 2022, 4:56 a.m.
    Status: Resolved
    Update: The issue has been resolved.
  • Time: March 14, 2022, 2:04 a.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 14, 2022, 2:04 a.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 11:30 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 11:30 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 8:34 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 8:34 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 5:11 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 5:11 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 12:11 p.m.
    Status: Identified
    Update: DevOps team is actively working on the issue with individual customers and checking with the customers and trying to resolve it at the earliest.
  • Time: March 13, 2022, 8:08 a.m.
    Status: Identified
    Update: DevOps team is actively working on the Clusters and Scheduler issue with individual customers and checking with the customers and trying to resolve it soon.
  • Time: March 13, 2022, 8:08 a.m.
    Status: Identified
    Update: DevOps team is actively working on the Clusters and Scheduler issue with individual customers and checking with the customers and trying to resolve it soon.
  • Time: March 13, 2022, 4:53 a.m.
    Status: Identified
    Update: DevOps team is still working on the Scheduler issue with individual customers and trying to resolve it.
  • Time: March 13, 2022, 4:53 a.m.
    Status: Identified
    Update: DevOps team is still working on the Scheduler issue with individual customers and trying to resolve it.
  • Time: March 13, 2022, 12:43 a.m.
    Status: Identified
    Update: DevOps team has identified the cause of the issue as scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve it.
  • Time: March 13, 2022, 12:43 a.m.
    Status: Identified
    Update: DevOps team has identified the cause of the issue as scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve it.
  • Time: March 12, 2022, 9:34 p.m.
    Status: Identified
    Update: DevOps team is actively working on it and they have identified a secondary issue with scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve the autoscaling issue.
  • Time: March 12, 2022, 9:34 p.m.
    Status: Identified
    Update: DevOps team is actively working on it and they have identified a secondary issue with scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve the autoscaling issue.
  • Time: March 12, 2022, 6:32 p.m.
    Status: Identified
    Update: DevOps team is actively working on it and they have identified a secondary issue with scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve the autoscaling issue.
  • Time: March 12, 2022, 6:32 p.m.
    Status: Identified
    Update: DevOps team is actively working on it and they have identified a secondary issue with scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve the autoscaling issue.
  • Time: March 12, 2022, 3:35 p.m.
    Status: Identified
    Update: Devops has identified a secondary issue with scheduler autoscaling that is contributing to the remaining intermittent issues. They are currently working to resolve the autoscaling issue.
  • Time: March 12, 2022, 11:58 a.m.
    Status: Monitoring
    Update: DevOps team is continuously trying to resolve this issue as soon as possible as they are working on individual customers to resolve it.
  • Time: March 12, 2022, 11:58 a.m.
    Status: Monitoring
    Update: DevOps team is continuously trying to resolve this issue as soon as possible as they are working on individual customers to resolve it.
  • Time: March 12, 2022, 8:45 a.m.
    Status: Monitoring
    Update: DevOps team is continuously trying to resolve this issue as soon as possible as they are working on individual customers to resolve it.
  • Time: March 12, 2022, 8:45 a.m.
    Status: Monitoring
    Update: DevOps team is continuously trying to resolve this issue as soon as possible as they are working on individual customers to resolve it.
  • Time: March 12, 2022, 4:59 a.m.
    Status: Monitoring
    Update: DevOps team is trying to resolve this issue as soon as possible as they are continuing to resolve issues for specific individual customers.
  • Time: March 12, 2022, 4:59 a.m.
    Status: Monitoring
    Update: DevOps team is trying to resolve this issue as soon as possible as they are continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 11:32 p.m.
    Status: Monitoring
    Update: Overall, the 'api.qubole.com' environment seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 11:32 p.m.
    Status: Monitoring
    Update: Overall, the 'api.qubole.com' environment seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 8:42 p.m.
    Status: Monitoring
    Update: Overall, the environment 'api.qubole.com' seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 8:42 p.m.
    Status: Monitoring
    Update: Overall, the environment 'api.qubole.com' seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 5:23 p.m.
    Status: Monitoring
    Update: Overall, the api.qubole.com environment seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 5:23 p.m.
    Status: Monitoring
    Update: Overall, the api.qubole.com environment seems to be stabilizing. DevOps team is continuing to resolve issues for specific individual customers.
  • Time: March 11, 2022, 1:47 p.m.
    Status: Monitoring
    Update: Overall api.q environment seems to be stabilizing. Devops team is continuously monitoring the environment
  • Time: March 11, 2022, 1:47 p.m.
    Status: Monitoring
    Update: Overall api.q environment seems to be stabilizing. Devops team is continuously monitoring the environment
  • Time: March 11, 2022, 3:56 a.m.
    Status: Identified
    Update: New ASG has been created under classic and added a couple of nodes and those are serving traffic. Now DevOps is working on the Redis connection issue and also, still they are working on the root cause of this issue to resolve it.
  • Time: March 11, 2022, 3:56 a.m.
    Status: Identified
    Update: New ASG has been created under classic and added a couple of nodes and those are serving traffic. Now DevOps is working on the Redis connection issue and also, still they are working on the root cause of this issue to resolve it.
  • Time: March 10, 2022, 8:31 p.m.
    Status: Identified
    Update: New ASG has been created under classic and added a couple of nodes and those are serving traffic. Scheduler nodes and the connectivity issues between worker and memcache are fixed. Now Devops try to run a sample jobs and observing the stability.
  • Time: March 10, 2022, 8:31 p.m.
    Status: Identified
    Update: New ASG has been created under classic and added a couple of nodes and those are serving traffic. Scheduler nodes and the connectivity issues between worker and memcache are fixed. Now Devops try to run a sample jobs and observing the stability.
  • Time: March 10, 2022, 4:18 p.m.
    Status: Identified
    Update: The scheduler tier on api.q is not allowing to create a new instances. Devops team has created a new non-vpc ASG and trying to add and scale up scheduler nodes. Once it is done we could switch from existing ASG to the new ASG.
  • Time: March 10, 2022, 4:18 p.m.
    Status: Identified
    Update: The scheduler tier on api.q is not allowing to create a new instances. Devops team has created a new non-vpc ASG and trying to add and scale up scheduler nodes. Once it is done we could switch from existing ASG to the new ASG.
  • Time: March 10, 2022, 11:26 a.m.
    Status: Identified
    Update: Our internal team has resolved the issue with worker nodes. The team is working on auto scaling of the nodes under scheduler ELB.
  • Time: March 10, 2022, 11:26 a.m.
    Status: Identified
    Update: Our internal team has resolved the issue with worker nodes. The team is working on auto scaling of the nodes under scheduler ELB.
  • Time: March 10, 2022, 1:19 a.m.
    Status: Identified
    Update: DevOps had identified that there is an issue with memcache and redis in api.qubole.com. Devops team is investigating further.
  • Time: March 10, 2022, 1:19 a.m.
    Status: Identified
    Update: DevOps had identified that there is an issue with memcache and redis in api.qubole.com. Devops team is investigating further.
  • Time: March 9, 2022, 10:05 p.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands and UI. At this time issue appears to be intermittent.
  • Time: March 9, 2022, 10:05 p.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands and UI. At this time issue appears to be intermittent.

Updates:

  • Time: Feb. 11, 2022, 4:07 p.m.
    Status: Resolved
    Update: It seems that the tunnel server node issue is resolved as api.qubole.com is now working fine.
  • Time: Feb. 11, 2022, 4:07 p.m.
    Status: Resolved
    Update: It seems that the tunnel server node issue is resolved as api.qubole.com is now working fine.
  • Time: Feb. 11, 2022, 1:03 p.m.
    Status: Monitoring
    Update: Replacement of bad nodes is completed and now we are monitoring on it.
  • Time: Feb. 11, 2022, 1:03 p.m.
    Status: Monitoring
    Update: Replacement of bad nodes is completed and now we are monitoring on it.
  • Time: Feb. 11, 2022, 11:04 a.m.
    Status: Identified
    Update: DevOps had identified that there is an issue with tunnel servers in api.qubole.com, and after creating new tunnels & doing sanity tests, faulty tunnels have been removed from the backend.
  • Time: Feb. 11, 2022, 11:04 a.m.
    Status: Identified
    Update: DevOps had identified that there is an issue with tunnel servers in api.qubole.com, and after creating new tunnels & doing sanity tests, faulty tunnels have been removed from the backend.
  • Time: Feb. 11, 2022, 8:53 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Feb. 11, 2022, 8:53 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Feb. 11, 2022, 8:52 a.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands. At this time issue appears to be partial, but DevOps is investigating on it.
  • Time: Feb. 11, 2022, 8:52 a.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands. At this time issue appears to be partial, but DevOps is investigating on it.

Updates:

  • Time: Jan. 29, 2022, 10:39 a.m.
    Status: Resolved
    Update: DevOps has confirmed that the issue has been resolved, the environment gcp.qubole.com is up and running now.
  • Time: Jan. 29, 2022, 10:39 a.m.
    Status: Resolved
    Update: DevOps has confirmed that the issue has been resolved, the environment gcp.qubole.com is up and running now.
  • Time: Jan. 29, 2022, 8:22 a.m.
    Status: Identified
    Update: Dev team is investigating this issue and this is due to nginx container name resolution is not happening in the service (consul-master-cluster-ip). The team is suspecting that this is due to incorrect Deployment configurations and that is what is being investigated right now.
  • Time: Jan. 29, 2022, 8:22 a.m.
    Status: Identified
    Update: Dev team is investigating this issue and this is due to nginx container name resolution is not happening in the service (consul-master-cluster-ip). The team is suspecting that this is due to incorrect Deployment configurations and that is what is being investigated right now.
  • Time: Jan. 29, 2022, 2:56 a.m.
    Status: Identified
    Update: Our Dev ops team is currently working with nginx-tugboatand. The Nginx-tugboat is trying to connect to the consul-master.
  • Time: Jan. 29, 2022, 2:56 a.m.
    Status: Identified
    Update: Our Dev ops team is currently working with nginx-tugboatand. The Nginx-tugboat is trying to connect to the consul-master.
  • Time: Jan. 28, 2022, 11:23 p.m.
    Status: Identified
    Update: DevOps team currently comparing few yml files to make sure the certificates are properly installed. Currently they are working on it.
  • Time: Jan. 28, 2022, 3:51 p.m.
    Status: Identified
    Update: DevOps has restored the certificate for 2022 in the config map and all other places but it's still picking the older certificate (2021). they are currently reviewing all settings to see if there are any other places where we need to update the config.
  • Time: Jan. 28, 2022, 3:51 p.m.
    Status: Identified
    Update: DevOps has restored the certificate for 2022 in the config map and all other places but it's still picking the older certificate (2021). they are currently reviewing all settings to see if there are any other places where we need to update the config.
  • Time: Jan. 28, 2022, 11:47 a.m.
    Status: Identified
    Update: DevOps is still trying to find the validity of the TLS certificate due to which UI is picking up the old certificate, Hence failing to load
  • Time: Jan. 28, 2022, 11:47 a.m.
    Status: Identified
    Update: DevOps is still trying to find the validity of the TLS certificate due to which UI is picking up the old certificate, Hence failing to load
  • Time: Jan. 28, 2022, 9:23 a.m.
    Status: Identified
    Update: DevOps has identified the issue with the Certificate update and also found the location of the old cert to revert it. The team is actively analyzing and working on it to revert it back.
  • Time: Jan. 28, 2022, 9:23 a.m.
    Status: Identified
    Update: DevOps has identified the issue with the Certificate update and also found the location of the old cert to revert it. The team is actively analyzing and working on it to revert it back.
  • Time: Jan. 28, 2022, 5:53 a.m.
    Status: Identified
    Update: Devops has identified some issue with certificate update. Currently they are working on it.
  • Time: Jan. 28, 2022, 5:53 a.m.
    Status: Identified
    Update: Devops has identified some issue with certificate update. Currently they are working on it.
  • Time: Jan. 28, 2022, 3:49 a.m.
    Status: Investigating
    Update: Currently gcp.qubole.com environment web page is not loading. We are actively working on this issue.
  • Time: Jan. 28, 2022, 3:49 a.m.
    Status: Investigating
    Update: Currently gcp.qubole.com environment web page is not loading. We are actively working on this issue.

Updates:

  • Time: Jan. 19, 2022, 9:53 a.m.
    Status: Resolved
    Update: DevOps has confirmed that the issue has been resolved and processing commands are working fine in api.qubole.com.
  • Time: Jan. 19, 2022, 8:23 a.m.
    Status: Monitoring
    Update: Our internal team has resolved the tunnel issue. The team continues to monitor the status.
  • Time: Jan. 19, 2022, 8:19 a.m.
    Status: Identified
    Update: We have identified that there was tunnel issue in api.qubole environment. Our Devops team is working on it.
  • Time: Jan. 19, 2022, 2:23 a.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands. At this time issue appears to be partial, but DevOps is investigating on it.

Updates:

  • Time: Jan. 19, 2022, 9:53 a.m.
    Status: Resolved
    Update: DevOps has confirmed that the issue has been resolved and processing commands are working fine in api.qubole.com.
  • Time: Jan. 19, 2022, 8:23 a.m.
    Status: Monitoring
    Update: Our internal team has resolved the tunnel issue. The team continues to monitor the status.
  • Time: Jan. 19, 2022, 8:19 a.m.
    Status: Identified
    Update: We have identified that there was tunnel issue in api.qubole environment. Our Devops team is working on it.
  • Time: Jan. 19, 2022, 2:23 a.m.
    Status: Investigating
    Update: api.qubole.com is currently seeing some degraded performance while processing commands. At this time issue appears to be partial, but DevOps is investigating on it.

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