Engine YardErrors in provisioning new instances
Our tests on reprovisioning instances have been successful, and we have not seen the issue recur.
Resolved
Outages and recoveries from the services you depend on.
38 incidents
Our tests on reprovisioning instances have been successful, and we have not seen the issue recur.
Resolved
The issue leading to errors being displayed in the Cloud Dashboard has now been identified and resolved, so the Dashboard is fully functional again.
Resolved
AWS is now reporting that this issue is resolved. If you are experiencing any further difficulties please do open a ticket.
Resolved
This issue has been resolved. If you have any further issues running chef or adding instances at this point please file a ticket with Support.
Resolved
Amazon Web Services has confirmed that the issue is now resolved.
Resolved
The failing platform instance has been replaced. All services are now working normally.
Resolved
An upgrade of an internal component caused errors for plugin authors publishing to the portal. The error has been resolved and our automated testing has been improved to prevent similar errors in the future.
Resolved
AWS have resolved the US-East-1 connectivity issues and the service is operating as normal again. If you see any outstanding issues please contact Engine Yard Support.
Resolved
The underlying issue is fixed. You can now boot and terminate instances on Engine Yard Cloud.
Resolved
This incident has been resolved.
Resolved
We received reports of legacy software being unable to access RubyGems.org. Specifically anyone using TLS 1.1. This is common on older operating systems like Ubuntu Precise 12.04. We quickly realized that our CDN provider had disabled TLS 1.1 today due to a previously announced deprecation of TLS 1.1. Unfortunately we hadn't taken steps to avoid this action today. Once we realized what had happened we migrated back to a configuration that allowed TLS 1.1. I'm sorry if this impacted you today. Everything should be working again now. If you are still having issues please submit a help ticket. The migration today is a short term change, and in the future we will be permanently disabling support for TLS 1.1. We will announce these dates.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
AWS S3 outages was resolved at 4pm yesterday. All issues have been cleared and functionality looks to be restored.
Resolved
We have not seen any other AWS S3 issues. We consider this resolved.
Resolved
This incident has been resolved.
Resolved
At this point we are considering this issue resolved and normal functionality has been restored. If you have any questions or want to discuss, please file a ticket and we are happy to assist
Resolved
This incident has been resolved.
Resolved
Upstream providers have pronounced this issue resolved as of 22:17 UTC. As we have seen no further reports of trouble since that time we are considering this issue resolved.
Resolved
6:36 AM PDT [RESOLVED] Between 4:31 AM and 6:10 AM PDT, we experienced errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region. During the issue, customers may have experienced failures indicating "hostname unknown" or "unknown host exception" when attempting to resolve the hostnames for AWS services and EC2 instances. This issue has been resolved and the service is operating normally.
Resolved
Deployments are working once more.
Resolved
This incident has been resolved.
Resolved
All gems appear to be installing successfully.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We believe the issue is mostly resolved for our customers at this point. If you are encountering any lingering issues please let us know.
Resolved
The issues related to application instance roles should now be resolved. If you do experience any issues at this point feel free to submit a support ticket.
Resolved
We have released =media-gfx/imagemagick-6.7.8.7-r2 and =media-gfx/imagemagick-6.9.0.3-r2 for our Stable V4 stack to resolve both cve vulnerabilities.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The dependency API has been stable, answering all requests, for about two hours. We'll keep an eye on it, but everything seems resolved for now.
Resolved
Error rates have returned to normal. Everything should be working now.
Resolved
This incident has been resolved.
Resolved
High load on our database is causing errors right now.
Resolved