Engine Yard Outage History

Engine Yard is up right now

Pingoru has recorded 53 incidents for Engine Yard: 1 in the last 12 months and 1 in the last 90 days.

Source: engineyard.statuspage.io

53incidents recorded
1last 12 months
1last 90 days
7 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Engine Yard in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 589 (0%)

Incidents, newest first

Minor October 23, 2026 SSL certificate errors on some connections 7m Engine Yard Cloud

Started Oct 23, 2026, 05:52 AM UTC· resolved Oct 23, 2026, 05:59 AM UTC

  1. identified Oct 23, 2026, 05:52 AM UTC

    We have identified an issue with SSL certificates on some endpoints. Some users may see certificate errors. This is more likely on Firefox, Apple devices, corporate proxies and strict API integrations. Other clients may not be affected. We are replacing the affected certificates and will update this page when the work is complete. Your data is not affected.

  2. resolved Oct 23, 2026, 05:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025 AWS Degraded – Multiple Services in US-East-1 Region 11h 32m Engine Yard Cloud, Engine Yard Kontainers, Help Center, ec2-ap-northeast-1 and 13 more

Started Oct 20, 2025, 11:38 AM UTC· resolved Oct 20, 2025, 11:11 PM UTC

  1. identified Oct 20, 2025, 11:38 AM UTC

    AWS has confirmed increased error rates and latencies affecting multiple services in the US-EAST-1 region. The incident is currently classified as "Degraded" by AWS. You may experience slowness, timeouts, or trouble accessing some parts of platform and services. We're closely monitoring the situation and will keep you updated as AWS provides more information.

  2. resolved Oct 20, 2025, 11:11 PM UTC

    AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.

Read the full incident report →

Major August 28, 2025 403 Forbidden callback errors 23h 33m Engine Yard Cloud

Started Aug 28, 2025, 03:15 AM UTC· resolved Aug 29, 2025, 02:48 AM UTC

  1. investigating Aug 28, 2025, 03:15 AM UTC

    We are currently investigating an issue causing 403 Forbidden callback errors, which are resulting in failed Chef runs and broken deployments. Our team is actively working to identify the root cause and restore full functionality.

  2. monitoring Aug 28, 2025, 04:26 AM UTC

    We have successfully implemented a fix for the issue that caused errors, and our systems are now operating normally. All impacted services are fully restored, and we have verified that the issue is no longer reproducible. We will continue to closely monitor system performance and provide another update within the next 24 hours

  3. resolved Aug 29, 2025, 02:48 AM UTC

    The incident has been resolved.

Read the full incident report →

Major August 4, 2025 EngineYard Cloud login not working 1h 49m Engine Yard Cloud

Started Aug 04, 2025, 09:23 AM UTC· resolved Aug 04, 2025, 11:12 AM UTC

  1. investigating Aug 04, 2025, 09:23 AM UTC

    We are currently investigating an issue related to the inability to login to https://login.engineyard.com/login.

  2. resolved Aug 04, 2025, 11:12 AM UTC

    Corrective actions were applied and the login to EngineYard Cloud should once again properly work.

Read the full incident report →

Major May 26, 2025 eybackup process failing 1d 23h Engine Yard Cloud

Started May 26, 2025, 05:51 AM UTC· resolved May 28, 2025, 05:09 AM UTC

  1. investigating May 26, 2025, 05:51 AM UTC

    We are currently investigating an issue with the eybackup process. Our team is actively working to identify the root cause and implement a fix.

  2. identified May 26, 2025, 10:26 AM UTC

    We have identified the issue, and our team is working on a final fix.

  3. monitoring May 27, 2025, 03:23 AM UTC

    Our team has investigated and fixed the issue. If backups are still failing, please perform a Chef run and test again—this should resolve the issue.

  4. resolved May 28, 2025, 05:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 15, 2025 Server provisioning failure - Failed to boot 4d 3h Engine Yard Cloud

Started May 15, 2025, 09:29 PM UTC· resolved May 20, 2025, 01:11 AM UTC

  1. investigating May 15, 2025, 09:29 PM UTC

    We are currently investigating the issue where some customers are unable to make deployments with the “Failed to boot in” messages.

  2. monitoring May 15, 2025, 11:38 PM UTC

    A fix has been implemented and we are monitoring the situation.

  3. resolved May 20, 2025, 01:11 AM UTC

    The server provisioning failure issue has been resolved.

Read the full incident report →

Major May 14, 2025 Access to backups using the UI not available 1d 20h Engine Yard Cloud

Started May 14, 2025, 02:32 PM UTC· resolved May 16, 2025, 11:02 AM UTC

  1. identified May 14, 2025, 02:32 PM UTC

    We have been notified that certain UI functionalities, such as accessing backups, are currently degraded. We have identified the root of this issue and are working to have it addressed. In the meantime, please reference this article to download your backups through a different method: https://support.engineyard.com/article/45200-view-and-download-database-backups

  2. monitoring May 15, 2025, 11:42 AM UTC

    Our infrastructure team has implemented a fix. We continue to monitor the situation closely and will provide further updates as soon as possible. Thank you for your patience.

  3. resolved May 16, 2025, 11:02 AM UTC

    The backup-access issue using the UI has been successfully resolved

Read the full incident report →