-
Why is BA’s website SO broken? Still?
Trying to book a return flight to NYC using an upgrade voucher. If you want to check out another route by pressing the “back” button with the intention of changing the destination airport, the site throws up an error. So you go back to the homepage, click on “My Account”, it says I’m already signed in using another account (I only have one account that’s already logged in) and won’t let me go any further. OK, so I’ll log back out and start again. Then log back in to go through the process again. It now say my details aren’t correct, even though I’ve logged in using the same details 5 minutes ago.
And on, and on, and on it goes. Its like I’m in some infinite loop of madness.
It just seems if you want to make a change to a redemption booking before confirming, the site can’t cope. It really shouldn’t be this difficult should it?
It’s particularly messy with the upgrade voucher. You basically have to go right back to the start for each search. At one point it was defaulting to the 241 as well, which could make things really complicated if you didn’t double check what you were doing – does it still do that?
I think you might be right. I have no 2 for 1 vouchers so can’t comment.
Anyway, I’ve given up and am doing it by phone. Got straight through to someone so that’s something.
Wife can’t seem to check in for her flight tomorrow.
“We’re sorry, the site is extremely busy right now”.
Bollocks it is, it’s just archaic.
Another reader was panicking about this the other day – it seemed to resolve itself after a few hours.
It’s truly abysmal … been searching for reward flights and keep getting the ‘there was a problem with your request’ error.
Yep – I had to call the other day just to book LHR-MAN with avios. Not exactly a complex itinerary…
I was also a victim of the “site too busy” saga. After a fair bit of testing I’ve found I never get that error when using Google Chrome, and only seem to get it when using Safari. Some poor compatibility testing going on in the BA Web team I suspect.
1 hour 32 minutes to make the booking via phone. About 2 minutes on hold to get through, the rest was listening to the operator get more frustrated with the system she was trying to use. Error messages, locking her out, waiting for the thing to update etc etc.
At least we both had a laugh about our experiences. I was surprised at how candid she was about the IT system.
Anyway, I’m booked and ready to go to Noo Yawk in May which has cheered me right up. Until my next BA booking experience anyway.
I was also a victim of the “site too busy” saga. After a fair bit of testing I’ve found I never get that error when using Google Chrome, and only seem to get it when using Safari. Some poor compatibility testing going on in the BA Web team I suspect.
More likely one of your browsers is glued by a load balancer into part of the BA backend that is broken. I’m seeing the same things.
Throw away your cookies and switch networks if you can too. May end up on a better bit of the infrastructure.
- You must be logged in to reply to this topic.
Popular articles this week:
