Login anomaly
Rapid retries, bot-like behavior, or impossible travel pattern.
Account locks are often triggered by security logic, not only user mistakes. This guide explains why restrictions happen, what to do immediately, how to prepare an unlock request, and how to avoid repeat locks after access is restored.
Cause Mapping
Rapid retries, bot-like behavior, or impossible travel pattern.
Identity details inconsistent with verification data.
Ownership conflicts between account and payment instrument.
Routine compliance or suspicious activity review windows.
First Response
Do not brute-force retries. Repeated attempts can extend lock windows. Capture the error state once, confirm you are on the official domain, and shift from retry mode to evidence mode.
Then review inbox and SMS for security notices. If a verification action is pending, complete it through official links. If no self-service action appears, prepare a support request with clean facts.
Support Quality
Support teams work faster when the request is specific. Include exact lock wording, timestamp, account identifier, and any recent security events like password reset, new device login, or payment-method update.
Avoid emotional or contradictory messages. Clear, chronological facts generally produce faster, cleaner outcomes.
| Error proof | Screenshot with date/time and visible URL |
|---|---|
| Timeline | Last successful login and first locked attempt |
| Context | Recent profile, device, or payment changes |
| Identity | Any requested verification documents |
Prevention
Refresh password and remove stale autofill records.
Avoid rapid switching across risky networks and unknown devices.
Batch account changes deliberately instead of frequent edits.
Locked Account FAQs
Related Guides