"Your play time expires in 30 minutes"

#0 - Sept. 1, 2010, 7:25 p.m.
Blizzard Post
Is what a popup I just got said. Except it doesn't. I paid for a month just over a week ago. When I check the subscription status it doesn't have a value for the expiration date.

Please fix this. I suppose if the message was accurate I can't post here again until you do.

Edit: It didn't actually kick me out. When I switched characters it reset the counter (started from 30 minutes again and gave another message every 5 minutes). Then when I decided to test it more and logged out, it gives me a "The login server is currently busy" message when I try to get back in.

It's possible I looked at the wrong numbers for my bank, I forget I pay for two WoW accounts. I gotta look over that more closely. But I've never noticed the account page to say anything other than "Active" with a renew date, "Canceled" with an expiration date and "Frozen" if it's actually expired. "Canceled (Expires: {0})" is new to me. I've not seen that timeout popup before, either.

Now the account management site went down for maintenance. I suppose the login server issue is related to that.
#2 - Sept. 1, 2010, 9:16 p.m.
Blizzard Post
Players who pay with a recurring payment method, such as a credit card, will receive this message if the subscription status is “pending”. This status is nothing to be alarmed about initially. It simply means that the subscription is currently processing and we have not received confirmation that the payment was collected or will be declined.

In the event the payment did not process successfully, you would have been notified via email. If the payment was successful, the status would update from “pending” to “active”.

Q u o t e:
Then when I decided to test it more and logged out, it gives me a "The login server is currently busy" message when I try to get back in.

This issue has since been resolved. You should be able to log back into the game without a problem.
#9 - Sept. 20, 2010, 6:38 a.m.
Blizzard Post
As Harlsoco mentioned above, this can be a perfectly normal notification.

Lately, however, there is a known issue where the message may recur when it should not. I do apologize for that, I know it's annoying.

For those that have posted above - if you are still experiencing this issue, please try relogging. This is something under investigation as to cause, but I don't have an ETA at the moment.