Engine Yard

Two data centers, one is Equinix on the East Coast:

About Us

Engine Yard came about in early 2006 because we saw a genuine need: customers were developing business-critical Rails applications, but they didn’t want to worry about deployment issues, nor did they want to hire IT staff to manage servers.

Customers wanted Rails-focused 24/7 operations support on top of great infrastructure, plus they wanted a smooth path from 100 users to 100,000 users.

That’s what Engine Yard is all about.

Our Customers

Over 400 customers, 2 data centers.

A growing number of organizations trust Engine Yard to manage their Rails application deployments, from small/medium applications running on 3 slices to large applications running on fully dedicated clusters.

Take a look at the January 11, 2008 TechCrunch article about Engine Yard with many comments from our valued customers.

Partners

www.equinix.com

www.heraklesdata.com

Herakles, LLC is a privately held company, offering mission critical colocation space and managed services to private and public institutions seeking to outsource their primary or disaster recovery IT infrastructure. Herakles operates a world class Internet data center located in Sacramento, CA with technical and security personnel on site 24 hours a day, every day.

Dear Engine Yard Customers,

As many of you know, we experienced a severe outage at our west coast data center yesterday; many of our customers were affected and experienced several hours of downtime. Our engineers became aware of the problem as soon as it occurred, and began the relevant data center escalation procedures.

What Happened

Yesterday March 30th, at 9:00 a.m. (PST), our west coast data center experienced a loss of internet connectivity.

Why Did It Happen

Our data-center provider — Herakles — maintains redundant internet uplinks with redundant equipment. Normally the failure of a single internet uplink or switch will prompt a failover event, with minimal loss of connectivity. In this case, however, the route processor of one of the redundant switches (a Cisco 6509) malfunctioned.