Engine Yard Outage History

Engine Yard is up right now

Engine Yard had 6 outages in the last 2 years totaling 228h 24m of downtime — averaging 0.2 incidents per month.

There were 6 Engine Yard outages since May 14, 2025 totaling 228h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://engineyard.statuspage.io

Critical October 20, 2025

AWS Degraded – Multiple Services in US-East-1 Region

Detected by Pingoru
Oct 20, 2025, 11:38 AM UTC
Resolved
Oct 20, 2025, 11:11 PM UTC
Duration
11h 32m
Affected: Engine Yard CloudEngine Yard KontainersHelp Centerec2-ap-northeast-1ec2-ap-southeast-1ec2-ap-southeast-2ec2-sa-east-1ec2-us-east-1ec2-us-west-1ec2-us-west-2Atlassian Bitbucket Git via HTTPSAtlassian Bitbucket SSHCloudFlare CloudFlare APIsCloudFlare SJC - San Jose, California, USACloudFlare IAD - Ashburn, Virginia, USARubyGems.org Gem DownloadsRubyGems.org Gem Index API
Timeline · 2 updates
  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

Detected by Pingoru
Aug 28, 2025, 03:15 AM UTC
Resolved
Aug 29, 2025, 02:48 AM UTC
Duration
23h 33m
Affected: Engine Yard Cloud
Timeline · 3 updates
  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

Detected by Pingoru
Aug 04, 2025, 09:23 AM UTC
Resolved
Aug 04, 2025, 11:12 AM UTC
Duration
1h 49m
Affected: Engine Yard Cloud
Timeline · 2 updates
  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

Detected by Pingoru
May 26, 2025, 05:51 AM UTC
Resolved
May 28, 2025, 05:09 AM UTC
Duration
1d 23h
Affected: Engine Yard Cloud
Timeline · 4 updates
  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

Detected by Pingoru
May 15, 2025, 09:29 PM UTC
Resolved
May 20, 2025, 01:11 AM UTC
Duration
4d 3h
Affected: Engine Yard Cloud
Timeline · 3 updates
  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

Detected by Pingoru
May 14, 2025, 02:32 PM UTC
Resolved
May 16, 2025, 11:02 AM UTC
Duration
1d 20h
Affected: Engine Yard Cloud
Timeline · 3 updates
  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 →