[status] Resolved: We've handled all of backlog. This means that new runs will start quickly again. Note that some users may still have runs queued due to concurrency limits on their account. https://t.co/yUmXpr7FEu
[status] Monitoring: We've identified the bottleneck and have made changes. It will take some time before the backlog will be fully processed though. https://t.co/i58axTCh39
[status] Monitoring: We had a brief outage on https://t.co/vqdgskeC23 between 7.10am and 9.10am New York time (12.10pm - 2.10pm GMT) this morning. Builds were failing with the error "Get https://t.co/R3buz9KnjV: net/http: TLS handshake t… https://t.co/xU97sK1Yxy
[status] Resolved: There was a temporary outage on the https://t.co/vqdgskeC23 website from 1406 UTC to 1545 on Friday 5th October 2018 which caused some web pages to return a 500 error for users who were not already logged-in. This only … https://t.co/AHCMCWT9Lo
[status] Resolved: This issue seems to be resolved now. We will continue to monitor and will open a new incident if there are additional problems. We apologize for the inconvenience. Thank you for building with Wercker! https://t.co/QdGPUt1bcy
[status] Investigating: We currently have a number of users experiencing seemingly random timeouts in their builds. Some builds will work, and others will timeout, with the same code (no changes). From what we can tell so far, the only commonality see… https://t.co/QdGPUt1bcy
[status] Resolved: We have identified the root cause of this issue. It was an update to one of our microservices. We have rolled back to the previous version and now everything is working fine again. Please accept our apologies for the inconvenience … https://t.co/TYuIpfXBfO
[status] Resolved: The root cause has been identified and a corrective fix was deployed. Users have confirmed that the problem is no longer affecting them. We apologize for any inconvenience this brief outage may have caused. If you notice any issues… https://t.co/XJyVetVcF9
[status] Investigating: Some users were experiencing build failures. This seems to be restricted to pipelines which use services with long names containing hyphens. This behavior started around 7am ET this morning. https://t.co/XJyVetVcF9