CloudStatus

Engineyard Status Alerts

Engineyard
Errors when provisioning new instances

Nov 21, 15:37 UTC Resolved - The provisioning issues have now been identified and resolved. Should you still see any issues, or require any assistance recovering a failed instance, please submit a support ticket.Nov 21, 14:29 UTC Investigating - Some customers are experiencing issues when provisioning instances. Our engineers are investigating.

Engineyard
Errors when provisioning new instances

Nov 21, 14:29 UTC Investigating - Some customers are experiencing issues when provisioning instances. Our engineers are investigating.

Engineyard
Errors in provisioning new instances

Nov 21, 04:04 UTC Resolved - Our tests on reprovisioning instances have been successful, and we have not seen the issue recur.Nov 21, 03:33 UTC Monitoring - Our engineers identified the issue and have deployed a fix. We are monitoring the situation. If you have encountered the error, please retry provisioning again.Nov 21, 03:15 UTC Investigating - Our engineers are investigating an issue that some customers have encountered while provisioning new instances.

Engineyard
Errors in provisioning new instances

Nov 21, 03:33 UTC Monitoring - Our engineers identified the issue and have deployed a fix. We are monitoring the situation. If you have encountered the error, please retry provisioning again.Nov 21, 03:15 UTC Investigating - Our engineers are investigating an issue that some customers have encountered while provisioning new instances.

Engineyard
Errors in provisioning new instances

Nov 21, 03:15 UTC Investigating - Our engineers are investigating an issue that some customers have encountered while provisioning new instances.

Engineyard
Dashboard LaBrea errors

Nov 11, 14:16 UTC 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.Nov 11, 13:47 UTC Investigating - We are aware of requests in the Cloud Dashboard returning errors at this time, this is under investigation and we apologise for any inconvenience.

Engineyard
Dashboard LaBrea errors

Nov 11, 13:47 UTC Investigating - We are aware of requests in the Cloud Dashboard returning errors at this time, this is under investigation and we apologise for any inconvenience.

Engineyard
us-west-2 network issue

Oct 18, 21:38 UTC Resolved - AWS is now reporting that this issue is resolved. If you are experiencing any further difficulties please do open a ticket.Oct 18, 21:17 UTC Identified - Amazon is reporting network issues in the us-west-2 (Oregon). This is being investigated, but if you are seeing any connection issues in the us-west-2 region this may be impacting you. If so please feel free to file a ticket ticket to track the issue.

Engineyard
us-west-2 network issue

Oct 18, 21:17 UTC Identified - Amazon is reporting network issues in the us-west-2 (Oregon). This is being investigated, but if you are seeing any connection issues in the us-west-2 region this may be impacting you. If so please feel free to file a ticket ticket to track the issue.

Engineyard
S3 related issues

Sep 14, 20:15 UTC 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.Sep 14, 19:43 UTC Monitoring - We are currently monitoring a situation with access to AWS S3 buckets. AWS is working to resolve this issue, but this may lead to trouble with chef runs, or with provisioning of new instances.

Engineyard
S3 related issues

Sep 14, 19:43 UTC Monitoring - We are currently monitoring a situation with access to AWS S3 buckets. AWS is working to resolve this issue, but this may lead to trouble with chef runs, or with provisioning of new instances.

Engineyard
Amazon Web Services Network Connectivity

Aug 3, 00:31 UTC Resolved - Amazon Web Services has confirmed that the issue is now resolved.Aug 3, 00:09 UTC Monitoring - Amazon Web Services has reported that they have identified the root cause and are beginning to see recovery for instances and EBS volumes in the affected Availability Zone in the US-EAST-1 Region. We continue to work toward full resolution.Aug 3, 00:06 UTC Identified - Amazon Web Services have confirmed that some instances are unreachable and some EBS volumes are experiencing degraded performance in a single Availability Zone in the US-EAST-1 Region. Engineers are engaged and we are working to resolve the issue.Aug 2, 23:39 UTC Investigating - Amazon Web Services is currently reporting that they are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region.

Engineyard
Amazon Web Services Network Connectivity

Aug 3, 00:09 UTC Monitoring - Amazon Web Services has reported that they have identified the root cause and are beginning to see recovery for instances and EBS volumes in the affected Availability Zone in the US-EAST-1 Region. We continue to work toward full resolution.Aug 3, 00:06 UTC Identified - Amazon Web Services have confirmed that some instances are unreachable and some EBS volumes are experiencing degraded performance in a single Availability Zone in the US-EAST-1 Region. Engineers are engaged and we are working to resolve the issue.Aug 2, 23:39 UTC Investigating - Amazon Web Services is currently reporting that they are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region.

Engineyard
Amazon Web Services Network Connectivity

Aug 3, 00:06 UTC Identified - Amazon Web Services have confirmed that some instances are unreachable and some EBS volumes are experiencing degraded performance in a single Availability Zone in the US-EAST-1 Region. Engineers are engaged and we are working to resolve the issue.Aug 2, 23:39 UTC Investigating - Amazon Web Services is currently reporting that they are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region.

Engineyard
Amazon Web Services Network Connectivity

Aug 2, 23:39 UTC Investigating - Amazon Web Services is currently reporting that they are investigating network connectivity issues for some instances in a single Availability Zone in the US-EAST-1 Region.

Engineyard
ey-core commands and billing page are failing intermittently

Aug 1, 06:44 UTC Resolved - The failing platform instance has been replaced. All services are now working normally.Aug 1, 05:45 UTC Investigating - ey-core commands and billing page are failing intermittently. Deploys and chef runs through the dashboard are unaffected. We have identified the failing platform instance and are working to resolve the issue.

Engineyard
ey-core commands and billing page are failing intermittently

Aug 1, 05:45 UTC Investigating - ey-core commands and billing page are failing intermittently. Deploys and chef runs through the dashboard are unaffected. We have identified the failing platform instance and are working to resolve the issue.

Engineyard
ey-core commands and billing page are failing intermittently

Aug 1, 05:45 UTC Investigating - ey-core commands and billing page are failing intermittently. Deploys and chef runs through the dashboard are unaffected. We have identified the failing platform instance and are working to resolve the issue.

Engineyard
AWS US-East-1 connectivity issues

Jul 27, 14:20 UTC 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.Jul 27, 14:11 UTC Identified - AWS are currently experiencing connectivity issues in a single availability zone in the US-East-1 region. This issue is causing issues with communication between instances and may negatively effect applications with key instances running in the affected AZ. Please monitor our status page for updates and contact Support should you require further assistance.

Engineyard
AWS US-East-1 connectivity issues

Jul 27, 14:11 UTC Identified - AWS are currently experiencing connectivity issues in a single availability zone in the US-East-1 region. This issue is causing issues with communication between instances and may negatively effect applications with key instances running in the affected AZ. Please monitor our status page for updates and contact Support should you require further assistance.

Engineyard
Booting and Terminating Instance Failure

Jun 27, 03:55 UTC Resolved - The underlying issue is fixed. You can now boot and terminate instances on Engine Yard Cloud.Jun 27, 03:16 UTC Investigating - We are investigating an issue where booting and terminating instances fail. We will give you an update when you can retry booting or terminating instances.

Engineyard
Booting and Terminating Instance Failure

Jun 27, 03:16 UTC Investigating - We are investigating an issue where booting and terminating instances fail. We will give you an update when you can retry booting or terminating instances.

Engineyard
cloud.engineyard.com not responding

Mar 28, 18:40 UTC Resolved - This incident has been resolved.Mar 28, 18:29 UTC Monitoring - We have found the culprit leading to the inaccessibility of cloud.engineyard.com. cloud.engineyard.com should be accessible at this time.Mar 28, 18:07 UTC Investigating - We are currently investigating cloud.engineyard.com availability

Engineyard
Amazon S3 Error Rates

Mar 1, 07:00 UTC Resolved - We have not seen any other AWS S3 issues. We consider this resolved.Feb 28, 22:19 UTC Update - AWS is fully recovered for operations for adding new objects in S3. The Amazon S3 service is operating normally.Feb 28, 21:06 UTC Monitoring - We are seeing access to S3 buckets located in US East 1 start to resume normal operation. We are monitoring their status and any lingering issues caused by the outage.Feb 28, 19:00 UTC Update - AWS is continuing work to remediate the availability issues for Amazon S3 in US-EAST-1. AWS services and customer applications depending on S3 will continue to experience high error rates as they are actively working to remediate the errors in Amazon S3.Feb 28, 18:11 UTC Investigating - Amazon has reported increased error rates. They are currently investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.

Engineyard
Amazon S3 Error Rates

Feb 28, 22:19 UTC Update - AWS is fully recovered for operations for adding new objects in S3. The Amazon S3 service is operating normally.Feb 28, 21:06 UTC Monitoring - We are seeing access to S3 buckets located in US East 1 start to resume normal operation. We are monitoring their status and any lingering issues caused by the outage.Feb 28, 19:00 UTC Update - AWS is continuing work to remediate the availability issues for Amazon S3 in US-EAST-1. AWS services and customer applications depending on S3 will continue to experience high error rates as they are actively working to remediate the errors in Amazon S3.Feb 28, 18:11 UTC Investigating - Amazon has reported increased error rates. They are currently investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.

Engineyard
Amazon S3 Error Rates

Feb 28, 21:06 UTC Monitoring - We are seeing access to S3 buckets located in US East 1 start to resume normal operation. We are monitoring their status and any lingering issues caused by the outage.Feb 28, 19:00 UTC Update - AWS is continuing work to remediate the availability issues for Amazon S3 in US-EAST-1. AWS services and customer applications depending on S3 will continue to experience high error rates as they are actively working to remediate the errors in Amazon S3.Feb 28, 18:11 UTC Investigating - Amazon has reported increased error rates. They are currently investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.

Engineyard
Amazon S3 Error Rates

Feb 28, 19:00 UTC Update - AWS is continuing work to remediate the availability issues for Amazon S3 in US-EAST-1. AWS services and customer applications depending on S3 will continue to experience high error rates as they are actively working to remediate the errors in Amazon S3.Feb 28, 18:11 UTC Investigating - Amazon has reported increased error rates. They are currently investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.

Engineyard
Amazon S3 Error Rates

Feb 28, 18:11 UTC Investigating - Amazon has reported increased error rates. They are currently investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.

Engineyard
Degraded performance for EBS in us-east-1

Feb 23, 21:34 UTC 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 assistFeb 23, 20:45 UTC Monitoring - AWS has reported that they have resolved the underlying issue and the majority of EBS volumes should now be working with the rest repaired shortly. We are continuing to monitor the situation. If you have any questions or want to discuss, please file a ticket and we are happy to assistFeb 23, 20:17 UTC Identified - AWS has reported degraded performance on a small number of EBS volumes in the us-east region. AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist

Engineyard
Degraded performance for EBS in us-east-1

Feb 23, 20:45 UTC Monitoring - AWS has reported that they have resolved the underlying issue and the majority of EBS volumes should now be working with the rest repaired shortly. We are continuing to monitor the situation. If you have any questions or want to discuss, please file a ticket and we are happy to assistFeb 23, 20:17 UTC Identified - AWS has reported degraded performance on a small number of EBS volumes in the us-east region. AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist

Engineyard
Degraded performance for EBS in us-east-1

Feb 23, 20:45 UTC Monitoring - AWS has reported that they have resolved the underlying issue has been resolved and the majority of EBS volumes should now be working with the rest repaired shortly. We are continuing to monitor the situation. If you have any questions or want to discuss, please file a ticket and we are happy to assistFeb 23, 20:17 UTC Identified - AWS has reported degraded performance on a small number of EBS volumes in the us-east region. AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist

Engineyard
Degraded performance for EBS in us-east-1

Feb 23, 20:17 UTC Identified - AWS has reported degraded performance on a small number of EBS volumes in the us-east region. AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist

Engineyard
Degraded performance for EBS in us-east 1

Feb 23, 20:15 UTC Identified - AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist

Engineyard
StatusCheck Alerts

Feb 17, 02:50 UTC Resolved - This incident has been resolved.Feb 16, 04:30 UTC Monitoring - Between 3:23 AM UTC and 3:42 AM UTC , our system generated old StatusCheck alerts for some instances. These are real alerts but were only delivered today due to an issue on our end which we have already fixed. The alerts affected are StatusCheckFailed_Instance, StatusCheckFailed_System, and CpuCreditBalance. The last one is only for T2 instances. In most cases, the alerts were automatically resolved and no action is needed on your part. If you see an alert that is not resolved, please check that you can ssh to the instance. If you have any questions, please log in to your account to file a ticket.

Engineyard
StatusCheck Alerts

Feb 16, 04:30 UTC Monitoring - Between 3:23 AM UTC and 3:42 AM UTC , our system generated old StatusCheck alerts for some instances. These are real alerts but were only delivered today due to an issue on our end which we have already fixed. The alerts affected are StatusCheckFailed_Instance, StatusCheckFailed_System, and CpuCreditBalance. The last one is only for T2 instances. In most cases, the alerts were automatically resolved and no action is needed on your part. If you see an alert that is not resolved, please check that you can ssh to the instance. If you have any questions, please log in to your account to file a ticket.

Engineyard
Dashboard Maintenance

Jan 8, 05:25 UTC Completed - Scheduled maintenance has been completed.Jan 8, 05:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Initially this status was posted a day earlier but maintenance is now in progress on the announced schedule.Jan 5, 20:53 UTC Scheduled - On January 7, 2017 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 9pm PT - 9:30pm PT (5am UTC - 5:30am UTC ) and will not have a negative impact to your applications.

Engineyard
Dashboard Maintenance

Jan 8, 05:15 UTC Completed - Scheduled maintenance is currently in progress.Jan 8, 05:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Initially this status was posted a day earlier but maintenance is now in progress on the announced schedule.Jan 5, 20:53 UTC Scheduled - On January 7, 2017 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 9pm PT - 9:30pm PT (5am UTC - 5:30am UTC ) and will not have a negative impact to your applications.

Engineyard
Dashboard Maintenance

Jan 7, 05:30 UTC Completed - The scheduled maintenance has been completed.Jan 7, 05:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan 5, 20:53 UTC Scheduled - On January 7, 2017 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 9pm PT - 9:30pm PT (5am UTC - 5:30am UTC ) and will not have a negative impact to your applications.

Engineyard
Dashboard Maintenance

Jan 7, 05:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan 5, 20:53 UTC Scheduled - On January 7, 2017 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 9pm PT - 9:30pm PT (5am UTC - 5:30am UTC ) and will not have a negative impact to your applications.

Engineyard
Dashboard Maintenance

Jan 5, 20:53 UTC Scheduled - On January 7, 2017 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 9pm PT - 9:30pm PT (5am UTC - 5:30am UTC ) and will not have a negative impact to your applications.

Engineyard
November 19th, 2016 Platform Maintenance

Nov 21, 18:42 UTC Completed - The scheduled maintenance has been completed.Nov 16, 01:00 UTC Scheduled - Maintenance Notice: On November 19th, 2016 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled from 8pm-8:30pm Pacific Time and will and will not have an impact to your applications. Please note that during this time, should you have any questions please call in to 866-518-9273 tel:866-518-9273 or you can come to IRC (https://webchat.freenode.net/ ) and type #eyhelp. As usual, both of those are covered 24x7.

Engineyard
November 19th, 2016 Platform Maintenance

Nov 16, 01:00 UTC Scheduled - Maintenance Notice: On November 19th, 2016 Engine Yard will be doing some maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled from 8pm-8:30pm Pacific Time and will and will not have an impact to your applications. Please note that during this time, should you have any questions please call in to 866-518-9273 tel:866-518-9273 or you can come to IRC (https://webchat.freenode.net/ ) and type #eyhelp. As usual, both of those are covered 24x7.

Engineyard
Engine Yard Cloud Maintenance

Oct 31, 11:00 UTC Completed - The scheduled maintenance has been completed.Oct 31, 08:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct 26, 23:57 UTC Scheduled - On October 31, 2016 Engine Yard will be doing maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 1am PT - 3am PT (8am UTC - 11am UTC ) and will not have a negative impact to your applications. Please note that during this time, should you have any questions please call in to 866-518-9273 or you can come to IRC (https://webchat.freenode.net/) and type #eyhelp. As usual, both of those are covered 24x7.

Engineyard
Engine Yard Cloud Maintenance

Oct 31, 08:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct 26, 23:57 UTC Scheduled - On October 31, 2016 Engine Yard will be doing maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 1am PT - 3am PT (8am UTC - 11am UTC ) and will not have a negative impact to your applications. Please note that during this time, should you have any questions please call in to 866-518-9273 or you can come to IRC (https://webchat.freenode.net/) and type #eyhelp. As usual, both of those are covered 24x7.

Engineyard
Engine Yard Cloud Maintenance

Oct 26, 23:57 UTC Scheduled - On October 31, 2016 Engine Yard will be doing maintenance to our own Platform that will prohibit access to your Dashboard and the ability to File a Ticket. This Maintenance is scheduled for 1am PT - 3am PT (8am UTC - 11am UTC ) and will not have a negative impact to your applications. Please note that during this time, should you have any questions please call in to 866-518-9273 or you can come to IRC (https://webchat.freenode.net/) and type #eyhelp. As usual, both of those are covered 24x7.

Engineyard
Cloud.engineyard.com Reporting Down

Oct 22, 01:11 UTC 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.Oct 21, 20:42 UTC Monitoring - We are seeing the issue resolved for the moment but will continue to monitorOct 21, 17:14 UTC Update - This is related to a ddos at an upstream provider. For some customers it may be working once more.Oct 21, 16:37 UTC Investigating - We are investigating the root cause of the dashboard not being resolvable.

Engineyard
Cloud.engineyard.com Reporting Down

Oct 21, 20:42 UTC Monitoring - We are seeing the issue resolved for the moment but will continue to monitorOct 21, 17:14 UTC Update - This is related to a ddos at an upstream provider. For some customers it may be working once more.Oct 21, 16:37 UTC Investigating - We are investigating the root cause of the dashboard not being resolvable.

Engineyard
Cloud.engineyard.com Reporting Down

Oct 21, 17:14 UTC Update - This is related to a ddos at an upstream provider. For some customers it may be working once more.Oct 21, 16:37 UTC Investigating - We are investigating the root cause of the dashboard not being resolvable.

Engineyard
Cloud.engineyard.com Reporting Down

Oct 21, 16:37 UTC Investigating - We are investigating the root cause of the dashboard not being resolvable.

Engineyard
Cloud Dashboard currently not working

Oct 21, 14:02 UTC 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.Oct 21, 13:19 UTC Monitoring - AWS continue to work to resolve the issue and we are now seeing the Cloud Dashboard and ZenDesk support portal back online. We are yet to receive an official all clear, so please monitor the situation and contact us via the support board or IRC should you require further assistance.Oct 21, 13:04 UTC Update - AWS are working to resolve the DNS resolution failures at this time (http://status.aws.amazon.com/).Oct 21, 12:36 UTC Update - AWs has identified the root cause of the issue causing errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region, and are currently working to resolve.Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 13:19 UTC Monitoring - AWS continue to work to resolve the issue and we are now seeing the Cloud Dashboard and ZenDesk support portal back online. We are yet to receive an official all clear, so please monitor the situation and contact us via the support board or IRC should you require further assistance.Oct 21, 13:04 UTC Update - AWS are working to resolve the DNS resolution failures at this time (http://status.aws.amazon.com/).Oct 21, 12:36 UTC Update - AWs has identified the root cause of the issue causing errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region, and are currently working to resolve.Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 13:19 UTC Monitoring - AWS continue to work to resolve the issue and we are now seeing the Cloud Dashboard and ZenDesk support portal back online. We are yet to receive an official all clear, so please monitor the situation and contact us via the support board or IRC should you require further assistance.Oct 21, 13:04 UTC Update - AWS are working to resolve the DNS resolution failures at this time (http://status.aws.amazon.com/).Oct 21, 12:36 UTC Update - AWS have identified the source of the issues to be a DDOS attack against the DNS provider Dyn (https://www.dynstatus.com/incidents/nlr4yrr162t8). This is causing resolution failures for AWS EC2 API calls (http://status.aws.amazon.com/).Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 13:04 UTC Update - AWS are working to resolve the DNS resolution failures at this time (http://status.aws.amazon.com/).Oct 21, 12:36 UTC Update - AWS have identified the source of the issues to be a DDOS attack against the DNS provider Dyn (https://www.dynstatus.com/incidents/nlr4yrr162t8). This is causing resolution failures for AWS EC2 API calls (http://status.aws.amazon.com/).Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 12:36 UTC Update - AWS have identified the source of the issues to be a DDOS attack against the DNS provider Dyn (https://www.dynstatus.com/incidents/nlr4yrr162t8). This is causing resolution failures for AWS EC2 API calls (http://status.aws.amazon.com/).Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 12:17 UTC Update - The networking issues are also affecting our ZenDesk support portal (https://support.cloud.engineyard.com) so customers may find they are unable to submit tickets at this time. Please contact support via irc.freenode.net channel #engineyard for urgent support if required.Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 11:59 UTC Identified - We have identified an issue with networking at AWS and continue to investigate.Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 11:40 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 11:30 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/). Platform engineers are currently investigating the issue.

Engineyard
Cloud Dashboard currently not working

Oct 21, 11:30 UTC Investigating - We are currently seeing failures to load the Cloud Dashboard (https://cloud.engineyard.com/admin/accounts/6224). Platform engineers are currently investigating the issue.

Engineyard
Deployment Failures

Oct 4, 17:55 UTC Resolved - Deployments are working once more.Oct 4, 17:35 UTC Investigating - We have received reports of failed deployments. We are currently investigating the issue and will update as the issue gets resolved.

Engineyard
Deployment Failures

Oct 4, 17:35 UTC Investigating - We have received reports of failed deployments. We are currently investigating the issue and will update as the issue gets resolved.

Engineyard
Environment Dashboard and other features not working

Oct 4, 04:32 UTC Resolved - This incident has been resolved.Oct 4, 03:40 UTC Monitoring - We've identified the problem and applied a fix. We're currently monitoring if we see any more issues.Oct 4, 03:30 UTC Investigating - The Environment Dashboard is not loading and other features may be affected. We're investigating the problem at this time.

Engineyard
Environment Dashboard and other features not working

Oct 4, 03:40 UTC Monitoring - We've identified the problem and applied a fix. We're currently monitoring if we see any more issues.Oct 4, 03:30 UTC Investigating - The Environment Dashboard is not loading and other features may be affected. We're investigating the problem at this time.

Engineyard
Environment Dashboard and other features not working

Oct 4, 03:30 UTC Investigating - The Environment Dashboard is not loading and other features may be affected. We're investigating the problem at this time.

Engineyard
Environment Dashboard and other features not working

Oct 4, 03:30 UTC Investigating - The Environment Dashboard is not loading and other features may be affected. We're investigating the problem at this time.

Engineyard
Network slowness

Aug 30, 04:46 UTC Resolved - We believe the issue is now resolved. If you are encountering any lingering issues please let us know.Aug 29, 23:15 UTC Investigating - We are currently investigating reports of network slowness in the US regions. If you believe you may be impacted please file a ticket with support.

Engineyard
Network slowness

Aug 30, 04:46 UTC 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.Aug 29, 23:15 UTC Investigating - We are currently investigating reports of network slowness in the US regions. If you believe you may be impacted please file a ticket with support.

Engineyard
Network slowness

Aug 29, 23:15 UTC Investigating - We are currently investigating reports of network slowness in the US regions. If you believe you may be impacted please file a ticket with support.

Engineyard
Network slowness

Aug 29, 23:15 UTC Investigating - We are currently investigating reports of network slowness in the us-east-1 region. If you believe you may be impacted please file a ticket with support.

Engineyard
Environments with incorrect app master label

Aug 25, 00:46 UTC 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.Aug 25, 00:19 UTC Monitoring - A fix has been implemented and we are monitoring the results.Aug 24, 23:59 UTC Identified - We have identified the underlying issue and the platform should again be operating normally. If you do experience further issues please do reach out to us.Aug 24, 22:57 UTC Investigating - We are currently investigating an issue with the labeling of the app master instances. An environment should have 1 and only 1 app master instance. If your clustered environment has more or less than 1 app master instance you will be unable to deploy currently. We are currently working to resolve this issue. If you are impacted please submit a ticket. If impacted please do NOT add instances or apply changes at this point.

Engineyard
Environments with incorrect app master label

Aug 25, 00:19 UTC Monitoring - A fix has been implemented and we are monitoring the results.Aug 24, 23:59 UTC Identified - We have identified the underlying issue and the platform should again be operating normally. If you do experience further issues please do reach out to us.Aug 24, 22:57 UTC Investigating - We are currently investigating an issue with the labeling of the app master instances. An environment should have 1 and only 1 app master instance. If your clustered environment has more or less than 1 app master instance you will be unable to deploy currently. We are currently working to resolve this issue. If you are impacted please submit a ticket. If impacted please do NOT add instances or apply changes at this point.

Engineyard
Environments with incorrect app master label

Aug 24, 23:59 UTC Identified - We have identified the underlying issue and the platform should again be operating normally. If you do experience further issues please do reach out to us.Aug 24, 22:57 UTC Investigating - We are currently investigating an issue with the labeling of the app master instances. An environment should have 1 and only 1 app master instance. If your clustered environment has more or less than 1 app master instance you will be unable to deploy currently. We are currently working to resolve this issue. If you are impacted please submit a ticket. If impacted please do NOT add instances or apply changes at this point.

Engineyard
Environments with incorrect app master label

Aug 24, 22:57 UTC Investigating - We are currently investigating an issue with the labeling of the app master instances. An environment should have 1 and only 1 app master instance. If your clustered environment has more or less than 1 app master instance you will be unable to deploy currently. We are currently working to resolve this issue. If you are impacted please submit a ticket. If impacted please do NOT add instances or apply changes at this point.

Engineyard
Environments with incorrect app master label

Aug 24, 22:57 UTC Investigating - We are currently investigating an issue with the labeling of the app master instances. An environment should have 1 and only 1 app master instance. If your clustered environment has more or less than 1 app master instance you will be unable to deploy currently. We are currently working to resolve this issue. If you are impacted please submit a ticket.

Engineyard
ImageMagick vulnerability CVE-2016-3714

Aug 18, 16:39 UTC 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.Jun 30, 16:52 UTC Update - New packages for CVE-2016-5118 have been released.Jun 8, 15:16 UTC Update - We are tracking CVE-2016-5118 and CVE-2016-3714 together. We will update this status page when a fix is released.May 4, 15:16 UTC Investigating - ImageMagick vulnerability CVE-2016-3714 announced. There is currently no patch available. However, you can protect your application by following the steps listed at: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&p=132726&sid=6b961f8b680a0c18189de528bd53504a#p132726 We will continue to monitor the situation as it develops.

Engineyard
Dashboard not responding

Aug 15, 21:47 UTC Resolved - This incident has been resolved.Aug 15, 17:34 UTC Monitoring - Our dashboard is working once more. We are monitoring to make sure there aren't any lingering effects.Aug 15, 17:04 UTC Investigating - We are currently investigating reports of our dashboard not responding.

Engineyard
Dashboard not responding

Aug 15, 17:34 UTC Monitoring - Our dashboard is working once more. We are monitoring to make sure there aren't any lingering effects.Aug 15, 17:04 UTC Investigating - We are currently investigating reports of our dashboard not responding.

Engineyard
Dashboard not responding

Aug 15, 17:04 UTC Investigating - We are currently investigating reports of our dashboard not responding.

Engineyard
Dashboard not responding

Aug 15, 17:04 UTC Investigating - We are currently investigating reports of our dashboard not responding.

Engineyard
Unexpected Platform Maintenance due to underlying hardware

Aug 15, 14:58 UTC Resolved - At 6:20 AM PDT we had unexpected maintenance due to underlying hardware from our infrastructure provider. The maintenance was resolved at 6:35 AM PDT

Engineyard
Deploy hooks issue

Aug 12, 11:08 UTC Resolved - A fix has now been issued for this issue, so deploy hooks now execute successfully on deploys. Should you see any further issues please submit a ticket at https://support.cloud.engineyard.com.Aug 12, 07:29 UTC Investigating - We have been alerted to an issue that is causing some application deployments that use deploy hooks to fail. We are already working on a fix. Running instances are unaffected, and chef runs should still work.

Engineyard
Deploy hooks issue

Aug 12, 07:29 UTC Investigating - We have been alerted to an issue that is causing some application deployments that use deploy hooks to fail. We are already working on a fix. Running instances are unaffected, and chef runs should still work.

Engineyard
Deploy hooks issue

Aug 12, 07:29 UTC Investigating - We have been alerted to an issue that is causing some application deployments that use deploy hooks to fail. We are already working on a fix. Running instances are unaffected, and chef runs should still work.

Engineyard
AWS Services Increased EC2 Error Rates and ELB Provisioning Times

Jul 30, 02:22 UTC Resolved - AWS has reported that they have Resolved the increased EC2 API Error Rates, and ELB Provisioning times in N. Virginia Region.Jul 30, 01:59 UTC Investigating - AWS has reported increased EC2 Error Rates and ELB Provisioning Times in the US East N. Virginia Region.

Engineyard
AWS Services Increased EC2 Error Rates and ELB Provisioning Times

Jul 30, 01:59 UTC Investigating - AWS has reported increased EC2 Error Rates and ELB Provisioning Times in the US East N. Virginia Region.

Engineyard
http://cloud.engineyard.com is down and being investigated

Jul 20, 02:38 UTC Resolved - We have resolved the issue, and the platform is working normally again.Jul 20, 02:28 UTC Investigating - Our platform is currently down, and our engineers are investigating the issue. We'll post updates again soon.

Engineyard
http://cloud.engineyard.com is down and being investigated

Jul 20, 02:28 UTC Investigating - Our platform is currently down, and our engineers are investigating the issue. We'll post updates again soon.

Engineyard
Problems with Booting Instances and Clicking Apply

Jul 11, 04:12 UTC Resolved - The issue has been fixed. Clicking Apply and booting new instances are working again.Jul 11, 03:54 UTC Investigating - We're investigating issues with failing chef runs. You will encounter this issues when clicking Apply on existing environments and instances and when booting new instances.

Engineyard
Problems with Booting Instances and Clicking Apply

Jul 11, 03:54 UTC Investigating - We're investigating issues with failing chef runs. You will encounter this issues when clicking Apply on existing environments and instances and when booting new instances.

Engineyard
Problems with Booting Instances and Clicking Apply

Jul 11, 03:54 UTC Investigating - We're investigating issues with failing chef runs. You will encounter this issues when clicking Apply on existing environments and instances and when booting new instances.

Engineyard
ImageMagick vulnerability CVE-2016-3714

Jun 30, 16:52 UTC Update - New packages for CVE-2016-5118 have been released.Jun 8, 15:16 UTC Update - We are tracking CVE-2016-5118 and CVE-2016-3714 together. We will update this status page when a fix is released.May 4, 15:16 UTC Investigating - ImageMagick vulnerability CVE-2016-3714 announced. There is currently no patch available. However, you can protect your application by following the steps listed at: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&p=132726&sid=6b961f8b680a0c18189de528bd53504a#p132726 We will continue to monitor the situation as it develops.

Engineyard
Platform task failures

Jun 23, 04:39 UTC Resolved - The platform issue has been solved. You can now boot and terminate instances successfully. If you see any other issues, please submit a ticket.Jun 22, 14:49 UTC Monitoring - Platform tasks are succeeding again at this time, but we continue to monitor for issues. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.Jun 22, 13:11 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com

Engineyard
Platform task failures

Jun 22, 14:49 UTC Monitoring - Platform tasks are succeeding again at this time, but we continue to monitor for issues. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.Jun 22, 13:11 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com

Engineyard
Platform task failures

Jun 22, 13:11 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com

Engineyard
ImageMagick vulnerability CVE-2016-3714

Jun 8, 15:16 UTC Update - We are tracking CVE-2016-5118 and CVE-2016-3714 together. We will update this status page when a fix is released.May 4, 15:16 UTC Investigating - ImageMagick vulnerability CVE-2016-3714 announced. There is currently no patch available. However, you can protect your application by following the steps listed at: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&p=132726&sid=6b961f8b680a0c18189de528bd53504a#p132726 We will continue to monitor the situation as it develops.

Engineyard
Provisioning Issues in US East 1

Jun 9, 21:14 UTC Resolved - This has been resolvedJun 9, 20:36 UTC Investigating - Currently we are seeing instances fail to provision within the AWS US East 1 region. US East 1 currently has increased api error rates.

Engineyard
Provisioning Issues in US East 1

Jun 9, 20:36 UTC Investigating - Currently we are seeing instances fail to provision within the AWS US East 1 region. US East 1 currently has increased api error rates.

Engineyard
ImageMagick vulnerability CVE-2016-3714

Jun 8, 15:16 UTC Update - We are tracking CVE-2016-5118 and CVE-2016-3714 together. We will update this status page when a fix is released.May 4, 15:16 UTC Investigating - ImageMagick vulnerability CVE-2016-3714 announced. There is currently no patch available. However, you can protect your application by following the steps listed at: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&p=132726&sid=6b961f8b680a0c18189de528bd53504a#p132726 We will continue to monitor the situation as it develops.

Engineyard
AWS Issues on Sydney Region

Jun 5, 19:37 UTC Resolved - AWS issues in the Sydney Region have been reported as resolved per AWS http://status.aws.amazon.com/ . If you have any outstanding issues please open a support ticketJun 5, 05:59 UTC Investigating - We are currently investigating EC2 issues in the Sydney region. AWS has reported increased connectivity issues for EC2 instances.

Engineyard
AWS Issues on Sydney Region

Jun 5, 05:59 UTC Investigating - We are currently investigating EC2 issues in the Sydney region. AWS has reported increased connectivity issues for EC2 instances.

Engineyard
Can't Edit Environment Settings If Using EBS Encryption

May 12, 01:37 UTC Resolved - Editing environment settings now works if using EBS encryption. If you see any issue, please open a support ticket.May 6, 02:01 UTC Investigating - Environment settings currently can't be updated if EBS encryption is enabled. Please open a Support ticket if you need to update your environment settings.

Engineyard
Can't Edit Environment Settings If Using EBS Encryption

May 6, 02:01 UTC Investigating - Environment settings currently can't be updated if EBS encryption is enabled. Please open a Support ticket if you need to update your environment settings.

Engineyard
ImageMagick vulnerability CVE-2016-3714

May 4, 15:16 UTC Investigating - ImageMagick vulnerability CVE-2016-3714 announced. There is currently no patch available. However, you can protect your application by following the steps listed at: https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&p=132726&sid=6b961f8b680a0c18189de528bd53504a#p132726 We will continue to monitor the situation as it develops.

Engineyard
Customers unable to submit support tickets

Apr 29, 14:57 UTC Resolved - The issue affecting ticket submission has now been identified and resolved and tickets can again be submitted via https://support.cloud.engineyard.com.Apr 29, 10:32 UTC Investigating - We are currently seeing issues submitted support tickets via https://support.cloud.engineyard.com. Should you wish to submit a ticket at this time, please make use of the "File a Ticket" link found in the top-right corner of the Cloud dashboard (https://cloud.engineyard.com).

Engineyard
Customers unable to submit support tickets

Apr 29, 10:32 UTC Investigating - We are currently seeing issues submitted support tickets via https://support.cloud.engineyard.com. Should you wish to submit a ticket at this time, please make use of the "File a Ticket" link found in the top-right corner of the Cloud dashboard (https://cloud.engineyard.com).

Engineyard
Trial Account Process

Apr 22, 20:54 UTC Resolved - Trial signups should be working properly once moreApr 22, 19:59 UTC Investigating - We are currently seeing an issue with trial sign ups.

Engineyard
Trial Account Process

Apr 22, 19:59 UTC Investigating - We are currently seeing an issue with trial sign ups.

Engineyard
US East 1 (Virginia) having network issues

Apr 21, 22:23 UTC Resolved - This incident has been resolved.Apr 21, 21:35 UTC Identified - Currently seeing impacts to customers related to networking issues in the region

Engineyard
US East 1 (Virginia) having network issues

Apr 21, 21:35 UTC Identified - Currently seeing impacts to customers related to networking issues in the region

Engineyard
Platform task failures

Apr 13, 14:19 UTC Resolved - Permanent solution has been put in place. All provisioning operations work normally. Issue is resolved. For any further issues or assistance please submit a ticket at https://support.cloud.engineyard.com.Apr 13, 13:59 UTC Update - UPDATE 13th April 14:00UTC - Permanent solution being put in place. All provisioning operations will not work for the next 30mins.Apr 13, 12:36 UTC Monitoring - Platform tasks are now completing successfully again, though the current resolution is a temporary one, so intermittent failures may be experienced over the next few hours as the permanent resolution is put in place. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.Apr 13, 11:15 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances and deploys. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.

Engineyard
Platform task failures

Apr 13, 13:59 UTC Update - UPDATE 13th April 14:00UTC - Permanent solution being put in place. All provisioning operations will not work for the next 30mins.Apr 13, 12:36 UTC Monitoring - Platform tasks are now completing successfully again, though the current resolution is a temporary one, so intermittent failures may be experienced over the next few hours as the permanent resolution is put in place. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.Apr 13, 11:15 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances and deploys. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.

Engineyard
Platform task failures

Apr 13, 12:36 UTC Monitoring - Platform tasks are now completing successfully again, though the current resolution is a temporary one, so intermittent failures may be experienced over the next few hours as the permanent resolution is put in place. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.Apr 13, 11:15 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances and deploys. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.

Engineyard
Platform task failures

Apr 13, 11:15 UTC Identified - We are seeing various platform tasks failing at this current time, e.g. provision and termination of instances and deploys. At this time we have identified an issue with the platform and are working on a resolution. If you require any assistance please submit a ticket at https://support.cloud.engineyard.com.

Engineyard
AWS US-East-1 connectivity issues

Mar 10, 10:16 UTC Resolved - As of 2:02 AM PST AWS have marked this issue as resolved and are reporting the service to be running as normal.Mar 10, 09:02 UTC Investigating - AWS are reporting connectivity issues and degraded EBS volume performance for a small number of instances in a single Availability Zone in the US-East-1 Region. Customers with affected instances may see performance issues at this time. Please monitor http://status.engineyard.com/ and http://status.aws.amazon.com/ for further updates and submit a support ticket at https://support.cloud.engineyard.com should you require further assistance.

Engineyard
Upcoming Maintenance Friday January 29th, 2016

Jan 29, 17:58 UTC Resolved - We have completed the scheduled maintenance of our account and billing systems and all impacted services are fully restored.Jan 26, 00:45 UTC Monitoring - Upcoming Maintenance: Friday January 29th, 2016. The maintenance will start at 9am PT and end at 10am PT (1hr). Customer Applications will remain running but you will not be able to create new accounts, access or update billing information during this maintenance.

Engineyard
Zendesk outage

Dec 24, 03:27 UTC Resolved - Zendesk has reported that all services have been restored at 12:45pm PST.Dec 23, 20:23 UTC Monitoring - Zendesk appears to have recovered and the support site should be accessible at this time; an official all-clear is still pending. We are continuing to monitor the situation. For emergency support please contact us via IRC or phone (https://www.engineyard.com/company/contact).Dec 23, 14:43 UTC Investigating - Zendesk are currently experiencing issues, which is resulting in problems with access to our support site https://support.cloud.engineyard.com for some customers. For emergency support please contact us via IRC or phone (https://www.engineyard.com/company/contact).

Engineyard
Dashboard Unavailable for Scheduled Maintenance

Dec 22, 05:12 UTC Resolved - This incident has been resolved.Dec 22, 03:57 UTC Monitoring - We will be performing maintenance on our dashboard for 30 minutes starting at 8pm PST on Monday December 21. During this time ALL systems will be unavailable.

Engineyard
Zendesk outage

Dec 17, 15:21 UTC Resolved - Zendesk have resolved the incident and as such our support site should be fully functional again.Dec 17, 12:49 UTC Investigating - Zendesk are currently experiencing issues, which is resulting in access issues to our support site https://support.cloud.engineyard.com. For emergency support please contact us via IRC or phone (https://www.engineyard.com/company/contact).

Engineyard
Inability to boot t2 type instances on stack v4-2.0.97

Nov 3, 10:58 UTC Resolved - Ability to boot t2, c4, and m4 type instances has been restored. The incident is resolved.Nov 2, 18:25 UTC Update - Our engineers are continuing to investigate this issue.Nov 2, 15:59 UTC Update - The issue has expanded fom the booting of t2 type instances to also affect booting of c4 and m4 type instances on stack v4-2.0.97. Other instance types can be booted normally. In case of needing assistance please contact our Support organization at https://support.cloud.engineyard.com.Oct 31, 16:31 UTC Identified - We've identified an issue preventing booting t2 type instances on stack v4-2.0.97. Other instance types can be booted normally. In case of needing assistance please contact our Support organization at https://support.cloud.engineyard.com">open a ticket with Support

Engineyard
Uptime monitoring not reporting to the dashboard

Oct 29, 20:35 UTC Resolved - We have fixed this on our side after identifying the change in provider payloadOct 19, 11:08 UTC Investigating - We are currently investing an issue where uptime monitoring alerts for applications are not being piped to the customer dashboard or alert emails. If you have any questions please submit a ticket at https://support.cloud.engineyard.com.

Engineyard
Dashboard Currently Not Working

Oct 14, 23:14 UTC Resolved - Our dashboard is working properly and is currently stable.Oct 14, 20:39 UTC Monitoring - Our dashboard is currently running. We are monitoring for any lasting irregularitiesOct 14, 20:05 UTC Identified - We have identified the issue and are working on a resolution.Oct 14, 19:17 UTC Investigating - We received notifications that our dashboard is not working as expected. We are currently working on a resolution to this issue.

Engineyard
Composer functionality

Oct 14, 19:15 UTC Resolved - We have resolved this issue via updating curl. Please update to the newest stack version to resolve this issue.Jul 17, 18:56 UTC Identified - We have identified issues with PHP's Composer functionality on our platform. Our engineers are working on the issue and we will provide updates once resolved.

Engineyard
Chef Recipes Error When Upgrading

Aug 12, 03:42 UTC Resolved - The issue with ntp failing to install during an upgrade has been solved. You should not see any errors when you click Upgrade.Aug 11, 08:31 UTC Investigating - When you click Upgrade, you might see an error installing ntp. Please refrain from clicking Upgrade for now. If you need to upgrade, run "ey ssh -e environment 'sudo eix-sync'" before clicking Upgrade. If you need any help, please open a support ticket.

Engineyard
Deployments and Chef runs not working due to AWS S3 errors

Aug 10, 11:00 UTC Resolved - AWS has reported that the error has been fixed and AWS S3 service is now operating normally. Customers may now deploy, or click Apply on the environment dashboard.Aug 10, 10:24 UTC Update - AWS is continuing to execute their recovery plan for AWS S3. All customers should still refrain from doing any deployments or clicking Apply on the environment dashboard. AWS has reported that new EC2 instance launches in N. Virginia (us-east-1) region are succeeding.Aug 10, 08:50 UTC Update - AWS EC2 service in N. Virgina is also experiencing launch failures. AWS has identified the root cause and is continuing work to resolve the issue. Customers may experience failed provisioning of instances in the N. Virginia (us-east-1) region.Aug 10, 08:13 UTC Identified - AWS S3 service in the US Standard region is currently experiencing elevated errors and affecting Engine Yard Cloud deployments and chef runs. All customers should refrain from doing any deployments or clicking Apply on the environment dashboard.

Engineyard
Detached Instances

Aug 6, 01:25 UTC Resolved - Previously Detached instances are once again detachedAug 6, 01:09 UTC Identified - We have identified the underlying issue and are working on rectifying the issue.Aug 6, 00:23 UTC Investigating - We are currently seeing some detached instances become active in environments again. We are currently investigating.

Engineyard
Database Snapshots When Booting New Instances

Jul 31, 13:59 UTC Resolved - The database snapshot selection issue has now been resolved, meaning database instances can be booted from snapshots without issue. If you require any further assistance please submit a ticket at https://support.cloud.engineyard.com.Jul 30, 06:36 UTC Investigating - We are investigating an issue where you can't select a database snapshot when booting new instances. Please refrain from stopping the whole environment until we resolve this issue.

Engineyard
Elastic Load Balancers failing to provision

Jul 14, 11:36 UTC Resolved - Issues regarding provisioing of ELBs for environments have been resolved. In case of needing any futher assistance please submit a ticket to Support.Jul 13, 14:20 UTC Identified - We have identified the issue behind the failure in provisioning ELBs for environments. Please submit a ticket to Support should you need to provision a new ELB or replace an existing one at this time, as well as if you require any further assistance.Jul 13, 10:47 UTC Investigating - We are investigating reports of ELBs failing to provision for environments. Please refrain from attempting to provision a new ELB or replace an existing one at this time. If you require further assistance please contact support via https://support.cloud.engineyard.com.

Engineyard
Applies and Deploys failing

Jun 22, 16:27 UTC Resolved - We have deployed a fix for this. Deployment and Applies should be working as expected. If you are still having issues please feel free to open a support ticket for further investigation.Jun 22, 16:14 UTC Identified - We have identified an issue where deploys and applies aren't working as expected. A fix is currently being worked on.

Engineyard
CloudFlare DNS issues

Jun 12, 10:10 UTC Resolved - CloudFlare have implemented a fix for the DNS issues: https://www.cloudflarestatus.com. If you see further issues or require assistance please contact support via https://support.cloud.engineyard.com.Jun 12, 09:47 UTC Investigating - CloudFlare have identified DNS issues resulting in resolution issues for some customers making use of their DNS servers. Please see https://www.cloudflarestatus.com/ for up to date information.

Engineyard
Timeouts on ui.engineyard.com

Jun 6, 09:56 UTC Resolved - The timeout issue has now been identified and resolved and ui.engineyard.com is now accessible again. Should you see any further issues please submit a support ticket at https://support.cloud.engineyard.com.Jun 6, 09:00 UTC Investigating - We are currently investigating timeouts on our Pro platform at ui.engineyard.com.

Engineyard
DB backups in AWS EU (Frankfurt) Region

Jun 4, 17:17 UTC Resolved - The problem has been resolved with our latest stack upgrades.May 12, 14:46 UTC Investigating - We are noticing issues with DB dump backups in the AWS EU (Frankfurt) Region. Snapshots remain functional. We will provide updates here as we investigate and identify the issue. Please open a Support Ticket should you have any questions or notice any issues.

Engineyard
Ticketing system

Jun 3, 15:44 UTC Resolved - Our ticketing provider has resolved the issue and service has returned to normal.Jun 3, 15:22 UTC Investigating - We are experiencing connectivity and timeout issues with our ticketing system provider. We have opened a ticket with them and are investigating. If you need immediate help, please join us in IRC or call our support line listed here: https://www.engineyard.com/company/contact

Engineyard
Intermittent Chef errors when clicking Apply

Apr 30, 16:36 UTC Resolved - The issue with chef errors when adding or removing instances has been resolved.Apr 30, 13:29 UTC Investigating - We are seeing some intermittent errors when running chef on environments. This may affect integrations and terminations of instances in environments. We will update this status page as we investigate this issue.

Engineyard
Trial customers unable to boot into a Region

Apr 22, 16:18 UTC Resolved - This has been resolved and new accounts are able to boot without issue.Apr 22, 14:22 UTC Investigating - We are currently seeing errors when new accounts attempt to boot instances. We are investigating and will update here once this has been identified and resolved.

Engineyard
OpenSSL vulnerabilities reported

Mar 30, 20:40 UTC Resolved - We have provided OpenSSL patches through our standard stack upgrade path. For notes on this process, please visit: https://support.cloud.engineyard.com/entries/89894297-Engine-Yard-Release-Notes-March-2015#20150320Mar 18, 18:32 UTC Investigating - Engine Yard is aware of the recently announced vulnerability in the OpenSSL protocol. The affected versions are 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf. The announcement’s high-risk vulnerability pertains only to 1.0.2, which is not applicable to Engine Yard’s application stacks, and therefore poses no risk. However, versions 1.0.1k, 1.0.0p, and 0.9.8zd are applicable as medium-severity risk. The following CVEs are involved, but detailed information has not been publicly disclosed at this time: CVE-2015-0209 CVE-2015-0285 CVE-2015-0288 CVE-2015-0291 Once OpenSSL has released further information and the recommended patches, we will begin the process of reviewing, testing, and integrating. Further updates can be found in our Security Known Issue article here: https://support.cloud.engineyard.com/entries/90876027-OpenSSL-vulnerabilities-reported

Engineyard
GitHub connectivity issues

Mar 27, 13:03 UTC Resolved - GitHub are reporting that the connectivity issues have been resolved, so no further deploy issues should be seen at Engine Yard, although the DDoS attack continues. Please continue to monitor https://status.github.com for updates to the situation and submit a ticket at https://support.cloud.engineyard.com if you have any further questions or issues.Mar 27, 09:22 UTC Monitoring - GitHub has been under DDos attack for the past 24+ hours. The attack is now under control, but customers may see intermittent connectivity issues causing deploy failures. Please monitor https://status.github.com for updates to the situation and submit a ticket at https://support.cloud.engineyard.com if you have any further questions or issues.

Engineyard
Upgrade failures on non-Ruby environments

Mar 18, 19:27 UTC Resolved - A Hotfix has been released for non-Ruby environments. Please feel free to update your environments at this time.Mar 18, 16:47 UTC Identified - Problem has been identified and fixed, and is currently in QA process. Expect availability within 2-3 hours.Mar 18, 12:12 UTC Investigating - We are seeing configuration failures on non-Ruby environments after applying the latest stack upgrade made available yesterday. For customers running PHP and Node.js applications, please avoid applying this latest upgrade to your environments until this issue has been rectified. For further assistance or if you have any questions please contact support via https://support.cloud.engineyard.com.

Engineyard
Emails not getting sent

Mar 16, 06:50 UTC Resolved - The issue has been fixed. You should now be receiving emails from the platform.Mar 16, 05:25 UTC Identified - Emails from our platform are not getting sent due to an issue with our provider. To see the alerts for your environments, please check the dashboard.