Keboola Status

Please review the entire post carefully to determine whether your use of the services will be affected.

As of 12:00 AM PDT April 30, 2015, we will discontinue support of RC4 cipher for securing connections to connection.keboola.com. 

Last night(10.4) we've got issues with our transformation server that caused failing of transformations(and so orchestrations), we fixed the issue and restarted all affected orchestrations. Sorry for the inconvenience.

We're announcing few security improvements:

• All our servers, facing to clients, are using EV security certificates (what is EV?) 
  

  
• All our servers have encrypted disks by using Amazon AWS KMS.
• All our Elasticsearch clusters encrypt all events.
• Amazon Redshift backends are encrypted by default. Existing customers can request to be moved to encrypted backends.
  
• Storage API employ native Amazon S3 file encryption by default
  

  
• All our Multi-AZ RDS metadata servers have encrypted data by default.
• New Amazon RDS servers are encrypted by default. Existing customers can request to be moved to encrypted backends.

Long story short: if you're connecting to Keboola Connection, client facing servers are covered by strong encryption SSL with displayed identity in browser's address bar + all client's data in Keboola Connection are encrypted by default.

• Bucket description is optional when creating new bucket
• Tables including columns can now be listed by one API call. 
• Fixed updating of Redshift alias SQL in Firefox

After June 1st 2015 we'll be enforcing strict limits on MySQL queries. All queries longer than 30 minutes (1800 seconds) will be terminated and the transformation will fail. You can now see duration of all queries longer than 2 minutes (120 seconds) in event log of any Transformation job so you can take optimization steps in advance.

We're introducing this limit to prevent errors like forgotten indexes and also to balance load on the shared MySQL Transformation database.

If your queries take significantly longer time than 30 minutes, please consider migrating your project to Redshift.

Our MySQL sandbox server (tapi-ovh.keboola.com) is down. We're firing up another server, will be up shortly.

UPDATE 4.43pm PST: Our backup sandbox server (tapi-sandbox.keboola.com) is up and running.

The Database Extractor now supports Oracle. 

We're experiencing very slow connection between our workers and the sandbox DB server. Please bear with us, we'll keep this post updated.

UPDATE 9.30pm PST: Looks like the connectivity is back at full speed. Thanks for your patience.

AdWords Extractor has been updated to AdWords API 2015.02, see http://googleadsdeveloper.blogspot.cz/2015/03/announcing-v201502-of-adwords-api.html for list of new features. 

Some AWQL queries configured in the Extractor will stop working because there have been few changes in column names (the most visible is probably renaming of Conversions to ConvertedClicks).

We are experiencing mysql transformations processes to be running much slower than usually. We are working on fixing this issue. However, this does not affect the redshift based transformations which should be running normally.

Sorry for any incovience. 

Update (11:30am PST): Issue has been resolved, everything is running fine now.