It's nice that everyone is so concerned about how long the battery backups last before the generators kick on....
Let's take a minute to discuss site redundancy and geo load balancers.

There is NO reason an enterprise of this size should be hosed by a power failure at a single location. In 2016, that is literally inexcusable. Here's what happened (another IT guy here, using his crystal ball).

Multiple solutions integrators and IT service providers have sent proposals to Delta with fixes for this for YEARS. YEARS. Someone at the top has decided that the cost outweighs the risk, and the papers have gotten lost in the pile.

Well guess what. That person will likely no longer be employed shortly. Delta will shell out 5-50 million in network redesign, app compatibility/lift and shift etc.

Here's a hint, Delta. If you want to boast about a BILLION dollars in profit, and how you distribute earth-shattering profit sharings, take the time to invest in your infrastructure first. Today cost you more than any day/event in the past decade, and it could have been avoided.

The last few times DL has automatically rebooked me on international trips hit by IRROPs, it's booked me for airports in a different country than to where I was ticketed. I've had to call in to get that manually fixed. And given the phone handling times can be a mess at times, the situation was made even worse by DL.

I have to wonder if DL uses DL/Skyteam elite status or fare as a basis to prioritize who gets rebooked how and for when.

I'm not an IT person, but isn't odd that power for critical systems and their backups are co-located?

Totally odd.

For even single-million-companies we do DR "100s of miles away" (and 'backup'/failover at least in a different building, better other end of city.)

I believe the report mentioned backup generator, not backup system. Backup generator has to be in the same location. DL, however, should have had a backup system somewhere else.

It's just to get back at DL for their shady non-transparent award flight practices :D

I took that post as a joke...following up the posters that seemed serious about VDB.

Tpa-atl and now going back to gate in TPA because someone wants to get off the plane.

Indeed. You'll find its typical that companies of Delta's size have data centers in very redundant places (think somewhere on the east coast then somewhere in the mountains out west)

Was supposed to go DCA-DTW-MCI today and decided to grab a ticket on AA as fast as I could once I found out. I personally found it very interesting that gate agents were still announcing delays for individual flights due to a "technical error" instead of making a blanket announcement- though several captains came out and got on the PA in the hold rooms telling folks it was a global incident that would impact all flights.

Ticket counter looked mobbed, and the local media was out in full force with all the major stations doing live shots at the ticket counters. Must be a slow news day in DC...

Wonder if this will make DL rethink their interline with AA...

Not a nationwide ground stop to ATL until 10:05. A coworker is in the air SLC-ATL.

Looks like flights are leaving CVG. Started with some DL Connection flights, now mainline to SLC, LAX, and FLL.

And it's in the air. Estimated SIN arrival of 4:34am.

This part of August in DC usually means relatively slow news days still.

If this kind of thing doesn't get DL to rethink interline and IRRROPs recovery invoking interlining, then not sure what it will take for DL to change its ways.

Not a good day for Delta's CIO. Pretty astounding for this to happen to a company of this size. I bet there's a lot more to this story than the power outage being reported.

+1.. Like when I was reading the SWA issue and a failed router. I was thinking, do they not use redundant routing and switching?