Engine Yard

Engine Yard Status

Official source
Everything seems OK

Don't miss the next Engine Yard outage!

Get a notification when the status changes! Start your FREE account today!

Sign up with Google or with email

Easily monitor 30 service providers that your business relies on for only $7/month.
Monitor up to 5 services for free.

Stats

0 incidents in the last 7 days

0 incidents in the last 30 days

Automatic Checks

Last check: 1 minute ago

Last known issue: over 1 year ago

Latest Incidents

Last 30 days

14/04
15/04
16/04
17/04
18/04
19/04
20/04
21/04
22/04
23/04
24/04
25/04
26/04
27/04
28/04
29/04
30/04
01/05
02/05
03/05
04/05
05/05
06/05
07/05
08/05
09/05
10/05
11/05
12/05
13/05
14/05

Resolved Inhability to boot and/or configure instances

On August 15, 2019 at 20:45:43 GMT, our monitoring system alerted that a core component of the platform was not responding. This component is responsible of providing information on stack versions and access to Chef recipes used to configure instances. At 20:55:49 GMT our Support Team begun investigating the issue. At 21:00:01 GMT it was identified that the application running this component couldn't connect to the database. At 21:01:47 GMT it was detected that the db instance had restarted itself and was entering recovery mode. At 21:02:48 GMT the component resumed services. At 21:14:42 GMT, after both automatic and manual testing reported no failures, the issue was deemed as solved.

over 1 year ago Official incident report

Resolved Inhability to boot and/or configure instances

On July 3, 2019 at 17:12:45 GMT, our monitoring system alerted that a core component of the platform was not responding. This component is responsible of providing information on stack versions and access to Chef recipes used to configure instances. At 17:20:05 GMT it was identified that the application running this component couldn't connect to the database. At 17:21:15 GMT it was detected that the db instance had restarted itself and was entering recovery mode. At 17:30:54 GMT the component resumed services. At 17:54:33 GMT, after both automatic and manual testing reported no failures, the issue was deemed as solved.

almost 2 years ago Official incident report

Resolved Networking issues impacting Support Portal availability

Networking issues are currently impacting the availability of support.cloud.engineyard.com. If you require urgent support please call us (+1 866 518-9273) or join us in IRC (irc.freenode.net #engineyard). Customers making use of CloudFlare may also be seeing downtime for their applications, dependent on the visitor location.

almost 2 years ago Official incident report

Resolved Regression identified with stack v5 3.0.59 and PHP apps

A regression has been identified with stack v5-3.0.59 and PHP applications. For the time being, do refrain from upgrading an environment to said version if running a PHP application. Contact EY Support for more information.

almost 2 years ago Official incident report

Resolved Platform tasks failing

We are seeing various platform task requests fail to be actioned. We are currently investigating this issue, but at this time please hold off from performing actions such as deployments or the addition or removal of any environmental resources.

about 2 years ago Official incident report

Resolved Stack Configuration Outage

There is currently an outage that is preventing chef configuration runs from completing successfully on the Platform. Your applications are not directly impacted, but you may be unable to boot instances or modify the configuration of your running environment. Our Engineering and Support teams are working to restore functionality as quickly as possible.

almost 3 years ago Official incident report

Resolved AWS Outage in US East

AWS has reported connectivity issues within one US-East-1 region; our Support team is working to help any impacted customers through their recovery.

almost 3 years ago Official incident report

Resolved EY Cloud Dashboard issues

We are encountering issues with provisioning instances from the dashboard. We are aware of the issue and our engineers are working on it. For the moment please refrain from booting new instances.

over 3 years ago Official incident report

Resolved Amazon has notified of an Emergency change in the reboot schedule. Instances requiring reboots will restart by 6:00 AM Pacific tomorrow.

Engine Yard Support is adjusting team member schedules to provide additional staffing to assist with the anticipated influx of Support requests tonight and tomorrow morning, and will be doing everything possible to try to minimize the impact of this event upon your applications. If you have already completed your restarts or reboots this should not affect you. If you need to verify the instances impacted you can visit https://cloud.engineyard.com/instance-reboots We encourage you to try and restart or replace instances to the extent possible prior to this maintenance.

over 3 years ago Official incident report

Resolved Emergency Maintenance ongoing - estimated 30 mins

We are currently investigating this issue.

over 3 years ago Official incident report

Incidents will happen.
You just need to prepare the best for them.

We're monitoring 805 services and adding more every week.

All-in-one platform to check the status of your services

IsDown integrates with hundreds of services. Handles the hassle of going to each one of the status pages and manage it one by one. We also help control how you receive the notifications.
We monitor all problems and outages and keep you posted on their current status in almost real-time.

Get notifications in your favorite communication channel

You can easily get notifications in your email, slack, or use Webhooks and Zapier to introduce the service status in your workflows.


Email
Slack
Slack
Zapier
Zapier

Webhooks

Empower your teams with more data

IsDown collects status data from services to help you be ahead of the game.

Engineering

You already monitor internal systems. Add another dimension (external systems) to your monitoring data and complement it with the external factors.

Customer Support

Know before your clients tell you. Anticipate possible issues and make the necessary arrangements.

Marketing

One of your competitors is down? Maybe a good time to spread the word about your service.

Trusted by teams from all over the world

Services Available
805
Incidents registered
47767
Monitoring Incidents
70

Ready to dive in? Start using IsDown today.

Sign up for free