A six-digit authenticator code is short-lived. If a sign-in form rejects it, stop and check the account label and timer before trying more random codes. Repeated attempts can trigger a temporary lock, and a genuine support team will never ask you to read the code aloud.
Check the obvious mismatches
- Choose the entry for the exact service and account you are signing in to.
- Wait for a fresh code rather than entering one just before its timer expires.
- Check that the phone’s date, time and time zone are set correctly, preferably from the device’s automatic time setting.
- Confirm you are on the service’s real sign-in page, not a link received in an unexpected message.
Google’s Authenticator help says current versions use the operating system clock; an older instruction to find a separate time-correction menu may not apply. Codes can be generated without mobile data, so a missing signal alone does not explain an incorrect time-based code.
Use recovery routes carefully
If you changed phones, the old account entry may not have moved. Check the authenticator’s supported sync or transfer method and the service’s saved backup codes. Use only the official account-recovery page; do not install a third-party “code fixer” or send a QR setup code to someone offering help.
After access is restored, review your backup sign-in methods and remove an old device only when the replacement works. Store recovery codes somewhere separate from the phone.
See Google Authenticator Help and the sign-in service’s own recovery instructions.



