Backlog for .org is caught up. Everything is back to operational.
Posted Apr 22, 2015 - 03:47 UTC
Update
We have caught up with the .com back log.
Posted Apr 22, 2015 - 01:06 UTC
Update
.org build capacity is back to normal. We are working through the back logs.
Posted Apr 22, 2015 - 00:26 UTC
Update
.com build capacity is back to normal. We are working through the back logs. Also, we are working to bring .org build capacity back to normal.
Posted Apr 21, 2015 - 23:45 UTC
Update
we are working to bring full capacity back online.
Posted Apr 21, 2015 - 22:33 UTC
Monitoring
The errors have subsided, and we’re working through the backlog.
Posted Apr 21, 2015 - 21:12 UTC
Update
Our infrastructure provider has implemented a fix for the issues we’ve been seeing, and the errors have subsided. We’re running a few cleanup routines to make sure everything is working as expected.
Posted Apr 21, 2015 - 21:00 UTC
Update
Our infrastructure provider is still working on the problem. Unfortunately part of the work is taking longer than expected.
Posted Apr 21, 2015 - 19:42 UTC
Identified
Our service provider has isolated the cause of errors, and is working on a fix.
Posted Apr 21, 2015 - 18:39 UTC
Investigating
The current issue may cause a wrong build image to be chosen during the virtual machine creation. If affected, this manifests in random build failures for PHP, Python, Perl, Java, Android, Haskell, Erlang/Elixir.
Posted Apr 21, 2015 - 16:52 UTC
Identified
We are receiving errors at higher rate from our infrastructure service provider, leading to issues creating virtual machines. We are working with the provider to address issues. This issue affects both .org and .com builds.