http://status.bigml.com/ 2026-09-11T20:43:10+00:00 BigML Status http://status.bigml.com/incident/48/

The issue with ML queues has been identified and corrected.

]]>

2018-11-03T21:32:00+00:00 BigML Status http://status.bigml.com/incident/47/

Batch outputs are running normally again

]]>

2018-02-27T06:05:00+00:00 BigML Status http://status.bigml.com/incident/46/

Batch outputs (predictions, centroids, anomalyscores, etc) are currently failing

]]>

2018-02-27T01:42:00+00:00 BigML Status http://status.bigml.com/incident/45/

we're experimenting some issues with the API databases. We're investigating...

]]>

2018-01-19T09:01:00+00:00 BigML Status http://status.bigml.com/incident/44/

The problem has been identified and processing times have returned to normal.

]]>

2018-01-11T19:42:00+00:00 BigML Status http://status.bigml.com/incident/43/

We are seeing increased rates of queued jobs even though there is excess capacity.

]]>

2018-01-11T17:16:00+00:00 BigML Status http://status.bigml.com/incident/42/

The issue has been resolved

]]>

2018-01-01T18:27:00+00:00 BigML Status http://status.bigml.com/incident/41/

Batch predictions are incurring intermittent failures

]]>

2018-01-01T18:00:00+00:00 BigML Status http://status.bigml.com/incident/40/

WhizzML is working normally and the backlog of tasks has finished processing.

]]>

2017-12-29T18:20:00+00:00 BigML Status http://status.bigml.com/incident/39/

The problem with WhizzML has been identified and fixed. We are watching the performance to ensure that things are working 100%

]]>

2017-12-29T17:58:00+00:00 BigML Status http://status.bigml.com/incident/38/

WhizzML scripts are currently not operating correctly and are not progressing past 10%. We are investigating the cause.

]]>

2017-12-29T09:13:00+00:00 BigML Status http://status.bigml.com/incident/37/

BigML Backend Outage

]]>

2017-10-21T08:29:00+00:00 BigML Status http://status.bigml.com/incident/36/

Dataset jobs are stuck

]]>

2017-10-03T15:46:00+00:00 BigML Status http://status.bigml.com/incident/35/

The queue for batch predictions/centroid/anomalyscores has cleared and jobs are progressing normally.

]]>

2017-10-02T06:59:00+00:00 BigML Status http://status.bigml.com/incident/34/

There is an unusual delay in processing batch prediction/centroid/anomalyscores jobs.

]]>

2017-10-02T06:32:00+00:00 BigML Status http://status.bigml.com/incident/33/

BigML is experiencing issues with one of the backend databases

]]>

2017-09-28T11:35:00+00:00 BigML Status http://status.bigml.com/incident/32/

Creation of models/ensembles is failing

]]>

2017-09-20T22:22:00+00:00 BigML Status http://status.bigml.com/incident/30/

The issue has been repaired and model jobs are progressing normally.

]]>

2017-09-09T17:26:00+00:00 BigML Status http://status.bigml.com/incident/29/

We are currently investigating an issue where 1/5 of the model servers are not taking jobs, causing delays.

]]>

2017-09-09T16:00:00+00:00 BigML Status http://status.bigml.com/incident/28/

We're investigating...

]]>

2017-09-08T12:54:00+00:00 BigML Status http://status.bigml.com/incident/27/

The issue with the batch processing queue has been resolved and tasks are completing normally.

]]>

2017-08-01T04:00:00+00:00 BigML Status http://status.bigml.com/incident/26/

The servers that handle batch outputs are currently backlogged on processing tasks. We are fixing the underlying problem.

]]>

2017-08-01T03:07:00+00:00 BigML Status http://status.bigml.com/incident/25/

MongoDB hiccup

]]>

2017-07-27T14:38:14+00:00 BigML Status http://status.bigml.com/incident/24/

WhizzML is operating at full capacity

]]>

2017-07-22T00:48:00+00:00 BigML Status http://status.bigml.com/incident/23/

.... and we are watching things...

]]>

2017-07-21T23:00:00+00:00 BigML Status http://status.bigml.com/incident/21/

There is a problem with WhizzML that has required us to temporarily stop the execution of all WhizzML scripts. We are investigating the issue and expect to have a fix very soon.

]]>

2017-07-21T19:02:00+00:00 BigML Status http://status.bigml.com/incident/20/

We are still cleaning up some older tasks

]]>

2017-07-20T18:53:00+00:00 BigML Status http://status.bigml.com/incident/19/

The release today has impacted the model servers and new jobs are currently queueing. We are fixing it...

]]>

2017-07-20T17:21:00+00:00 BigML Status http://status.bigml.com/incident/18/

The issue with the autoscaler has been resolved...

]]>

2017-05-30T17:51:00+00:00 BigML Status http://status.bigml.com/incident/17/

We are investigating issues with the autoscaler, which is impacting performance.

]]>

2017-05-30T15:08:00+00:00 BigML Status http://status.bigml.com/incident/16/

The autoscaler issues have been resolved and everything is run full speed once again...

]]>

2017-04-19T00:45:00+00:00 BigML Status http://status.bigml.com/incident/15/

BigML is experiencing some processing delays due to an autoscaling issue.

]]>

2017-04-18T23:20:00+00:00 BigML Status http://status.bigml.com/incident/14/

The performance issue with the model servers has been corrected and jobs are progressing normally...

]]>

2017-03-24T18:05:00+00:00 BigML Status http://status.bigml.com/incident/11/

The issue with the performance of model servers has been identified and a workaround has been implemented. We are still investigating the root cause.

]]>

2017-03-24T17:27:00+00:00 BigML Status http://status.bigml.com/incident/10/

Some tasks are being delayed in completion. We are investigating the cause...

]]>

2017-03-24T16:15:00+00:00 BigML Status http://status.bigml.com/incident/2/

AWS has resolved the issues with S3 and as a result BigML is fully operational.

]]>

2017-02-28T22:19:00+00:00 BigML Status http://status.bigml.com/incident/1/

BigML is experiencing an outage that impacts all resource access and creation. The underlying problem is an AWS outage, the details and status of which can be found at the AWS Service Health Dashboard for the us-east-1 region.

]]>

2017-02-28T17:59:00+00:00