Anyone have trouble to log-in QFF today?

[BensAdventures]

Bookings for my next three weeks have all gone..must be a bug.

Same here! I had multiple bookings, including a flight to SIN tomorrow, all gone... I'll give it some time, then call QF.

 

[RooFlyer]

Have 'Your profile' and 'Your summary' pages changed in their format overnight? Or was this done some time ago?

If new, probably the reason for the outages today. I haven't ever seen Qantas' (contract) IT manage to change their web site without stuffing it up as well.

 

[JessicaTam]

Now can log in, but like SeatBackForward, my bookings have gone.

Hopeless.


Again.

Same here. And I agree.

 

[whughes3]

Well, as of now, when I try to access my account I get:

[h=2]Error 404--Not Found[/h]

[TABLE="width: 100%"]
[TR]
[TD="width: 100%, bgcolor: white"][h=3]From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:[/h] [h=4]10.4.5 404 Not Found[/h] The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
[/TD]
[/TR]
[/TABLE]
CHARMING!!!!!!

 

[Wannabee]

I have the same issue. Just sent them
a message on Twitter

 

[eric2011]

Was able to make a new booking 1 hour ago for tomorrow but cannot get back in to manage bookings. All future bookings gone. Check my trip shows flight is ok

 

[RooFlyer]

Well, as of now, when I try to access my account I get:

[h=2]Error 404--Not Found[/h]

[TABLE="width: 100%"]
[TR]
[TD="width: 100%, bgcolor: white"][h=3]From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:[/h] [h=4]10.4.5 404 Not Found[/h] The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
[/TD]
[/TR]
[/TABLE]
CHARMING!!!!!!

Yep, same again (as posted #10 earlier today). They've obviously just twigged to the 'bookings gone' problem and of course have taken the whole thing down, rather than fixing it in the background.

Bloody amateurs.

 

[oz74]

Same issues here! Very annoying.

 

[Wannabee]

Worked for me just now. At first I saw the booking were back and now it lets me do seat selection.

 

[oz74]

Letting me log in but bookings disappeared!

 

[serfty]

At SFO now and getting the 404 error after logging on.

 

[legroom]

Could not see any of my bookings incl. one for BNE tomorrow !

Must be a cyber attack - denial of service

Else, it is sheer incompetence.


PS: the mobile app refused to recognise my log in, too. Total denial of service here @ Qantas

 

[oz74]

You doing a status run serfy?

 

[MH_fan]

Having the same problems after loggin in too.

 

[jdp]

Seems to be back now. 11am Sydney time.

 

[flyingfan]

I had problems but can access my bookings now - all good.

 

[Limewood]

Same here all now good.

 

[eric2011]

All good for me two

 

[drross]

no problems now - everything working 'well' again .. well, at least as good as usual.

 

[JessicaTam]

no problems now - everything working 'well' again .. well, at least as good as usual.

Until the next time...