ClueByFour
Sep 11, 10, 8:14 pm
Someone in IT at LUV is not having a good evening. I have been trying since about 6pm EDT to book a ticket. Try it, and the website sayeth:
This Southwest Airlines feature is unavailable. We apologize for any inconvenience this may cause.
Not only that, but they've acknowledged it's down on their twitter feed (http://twitter.com/SouthwestAir?int=GFOOTER-TOP-TWITTER) and anecdotal reports on their facebook page indicate aggents can't book either (http://www.facebook.com/Southwest?int=GFOOTER-TOP-FACEBOOK#!/Southwest?v=wall).
Epic Fail. This may be the first time I can ever remember thinking that LUV's sole control of their distribution channels (not being able to book them thru every booking engine) is biting their hindquarters a bit. That, and if the reports that agents can't book is true, one has to wonder what other systems are experiencing problems.
Anyone got a report from the airport this evening?
Edited to add: now I get what I can only assume is a reverse proxy error:
Bad Gateway
*
The proxy server received an invalid response from an upstream server.
That's not on my end (no proxy here). Ugly stuff.
This Southwest Airlines feature is unavailable. We apologize for any inconvenience this may cause.
Not only that, but they've acknowledged it's down on their twitter feed (http://twitter.com/SouthwestAir?int=GFOOTER-TOP-TWITTER) and anecdotal reports on their facebook page indicate aggents can't book either (http://www.facebook.com/Southwest?int=GFOOTER-TOP-FACEBOOK#!/Southwest?v=wall).
Epic Fail. This may be the first time I can ever remember thinking that LUV's sole control of their distribution channels (not being able to book them thru every booking engine) is biting their hindquarters a bit. That, and if the reports that agents can't book is true, one has to wonder what other systems are experiencing problems.
Anyone got a report from the airport this evening?
Edited to add: now I get what I can only assume is a reverse proxy error:
Bad Gateway
*
The proxy server received an invalid response from an upstream server.
That's not on my end (no proxy here). Ugly stuff.