Usually feels like
Open-ended
Nothing in the mechanism sets a ceiling, so no honest band exists.
A cooldown counts something down. This counts nothing, and no part of it is obliged to end.
The wait, in plain words
Locks are quiet by design. Sign in behaves normally right up to the moment it stops, and what replaces the account is usually a short line naming a state and nothing else. Sometimes not even that. No reason, no reference, no indication of who to ask or when to ask them.
The first instinct is to read the silence. It is not worth reading. The absence of a reason is not evidence that the lock was a mistake, and it is not evidence that it was deserved. It is a property of how the thing is built, and it would look identical either way.
Set it beside a cooldown after failed tries. That wait is short, it follows something you have just done, and it releases on its own. Its shape is visible in its behaviour: it is a timer, and timers end. This has none of those properties, which is why it sits in a different band rather than at the far end of the same one.
Underneath, while nothing moves
An account lock is the output of a rule. Rules of this kind exist because an account system has to defend itself against automated sign in attempts, against shared and resold accounts, against sessions arriving from patterns the system treats as suspicious, and against activity that looks like somebody testing what an account can do. Any of them can fire without the person behind the account having intended anything at all.
The rule will not be described to you, and it is better to understand why than to read it as rudeness. An explanation names the signal. Naming the signal tells anybody who wants to defeat it exactly what to change next time. The population most interested in that explanation is not you, and a system that answers you answers them in the same words. The silence is load bearing.
The honest description is therefore not that this wait is long. It is that it has no measurable extent at all. Nothing starts a clock, nothing reports on one, and nothing is obliged to stop.
Behaving, and not behaving
Not every locked account is the same wait. The distinction that matters is whether the account still exists as far as the system is concerned.
A lock that is still a wait
Sign in still recognises the account. The refusal happens after your details are accepted, and the message names a state rather than denying that the account exists. Everything else on the site behaves in the ordinary way.
There is a support route in the interface, and messages sent into it are at least accepted.
A lock that has stopped being a wait
The account is not recognised at all, as though it had never been made. Or the page accepts the details and then behaves differently on every attempt, or asks for something it has never asked for before.
Or the whole site is behaving oddly, in which case the wait you are actually in is a market that has not come back and not this one.
That last case is worth ruling out before anything else, because the response to it is different and the confusion is common. An account that will not open on a service that is itself in trouble is not a locked account.
The condition that ends this wait has to sit on your side, because nothing on the other side will provide one. It ends when the appeal has been made once through whatever route exists, and when everything on that account that mattered has been dealt with by other means or written off deliberately. After that, opening the sign in page is not waiting for an outcome. It is checking a door.
Safe to do meanwhile
There is genuinely little to do, and the little there is should be done once and then left alone.
- Write the appeal once and keep a copyShort and factual, with no argument about fairness. What the account is, when it stopped opening, what you were doing. Kept somewhere you can read without the account.
- Calibrate what a support channel normally doesSo your expectation of a reply is set by the channel rather than by how much you want one.
- Rule out the ordinary explanations firstA gate that has changed, a circuit that is failing, a stale session. All of them produce sign in failures that are not locks.
- Decide in advance how often you will tryAn interval you set is a wait. An impulse you follow is not.
What makes it longer
Almost everything that makes this worse gets done in the first stretch of it, while the silence is still surprising.
- Making a second account to ask about the first. Systems that lock accounts tend to notice, and the result is usually two locked accounts.
- Appealing again and again. Volume does not turn a channel that never acknowledges into one that does.
- Signing in from somewhere new to see whether that helps. It changes the picture the system holds of you, and not in the direction you want.
- Arguing about the reason. There is no reason on the table to argue with.
- Leaving anything of value sitting behind the lock while you decide what to make of it.
What this card is not. This card is not a route to recovering an account, and nothing here can tell you why any particular one stopped opening.
Questions people ask about this wait
Does appealing more than once improve anything?
There is no evidence available to you either way, which is itself the answer. A channel that does not acknowledge receipt cannot tell you whether the first message landed, so a second one is a guess about a system you cannot see. Markets of this shape generally treat repeated messages as a single thread.
Is silence a sign that the lock is permanent?
No. It is a sign that the system does not explain itself, which is equally true of the temporary ones. The silence is uninformative in both directions, and reading it as a verdict is reading something that was never written.