How to Fix Authy Code Not Working
If you are trying to log in and Authy keeps rejecting your verification code, the problem is usually tied to time sync, account setup, device changes, or app connectivity.
This guide explains how to fix Authy code not working and shows the most effective checks to restore two-factor authentication access.
Why Authy codes stop working
Authy generates time-based one-time passwords, also called TOTP codes, which depend on the correct account, the correct device, and accurate time on both ends.
When any of those elements drift, the code you enter may be valid in the app but still fail on the website or login screen.
- Time mismatch: Your phone, computer, or server clock is out of sync.
- Wrong account: You are using a different Authy profile or phone number.
- App sync issues: Authy has not fully refreshed your token list.
- Changed device: You restored the app but did not complete account reauthorization.
- Service-side problems: The website or authentication server is temporarily failing.
Check the code entry first
Before changing settings, make sure the issue is not a simple input mistake.
Authy codes change every 30 seconds, so even a short delay can make a code expire before submission.
- Type the code exactly as shown, without extra spaces.
- Use the newest code in the Authy app.
- Submit it immediately after it refreshes.
- Confirm you are entering the code for the correct site or account.
If the login page supports pasting, make sure the clipboard does not add hidden characters.
This matters more often on desktop browsers than on mobile devices.
Verify your device time and time zone
One of the most common reasons Authy verification fails is incorrect system time.
TOTP authentication is synchronized to the clock, so even a small mismatch can cause a rejection.
On iPhone and iPad
- Open Settings.
- Go to General and then Date & Time.
- Enable Set Automatically.
On Android
- Open Settings.
- Tap System or General management.
- Choose Date & time.
- Turn on automatic date, time, and time zone.
On Windows or macOS
- Use the operating system’s automatic time setting.
- Restart the browser after syncing the clock.
- Reload the login page and request a fresh code.
After adjusting the clock, wait for Authy to generate the next code and try again.
Confirm you are using the right Authy account
Authy accounts are typically tied to a phone number, and switching numbers, devices, or restore methods can create confusion.
If you have multiple phones or recently changed your SIM card, you may be looking at a different Authy profile than the one linked to your account.
- Check the phone number associated with Authy.
- Make sure the token belongs to the service you are trying to access.
- Look for duplicate or old installations of Authy on other devices.
- Verify that multi-device access is still enabled if you rely on more than one device.
If the token is missing, renamed, or duplicated, the verification app may be out of sync with the account you intended to protect.
Resync or refresh Authy tokens
Sometimes the app itself needs to be refreshed so it can properly display the current token list.
This is especially helpful after reinstalling the app, moving to a new phone, or restoring from backup.
- Close Authy completely and reopen it.
- Check whether all accounts are visible in the token list.
- Force a refresh by signing out and back in only if you understand the recovery impact.
- Install the latest version of Authy from the App Store or Google Play.
If the app is outdated, token generation or device authorization can behave inconsistently.
Updating often resolves compatibility problems without additional steps.
Check network access and app permissions
Authy does not need a constant connection to generate codes, but it does need occasional internet access to sync accounts and validate device changes.
Poor connectivity can delay token updates or account recovery.
- Switch between Wi-Fi and mobile data to test connectivity.
- Disable VPNs or privacy filters temporarily.
- Allow Authy to use background data if your phone restricts it.
- Check whether battery saver mode is limiting app activity.
On corporate networks, firewalls or DNS filtering can also interfere with login flows.
If the code works on cellular data but not on Wi-Fi, the network is likely part of the problem.
Remove and re-add the token if the service allows it
If only one account is failing and all other Authy codes work, the token itself may be corrupted or no longer matched to the service.
The most reliable fix is often to remove the authenticator entry from the service account and set it up again.
Before doing this, confirm you have one of the following:
- Backup codes from the service
- Recovery options such as email or SMS
- Access to another trusted device
Then disable two-factor authentication for that service and re-enable it using the new QR code or setup key.
This creates a fresh token and usually eliminates stale-code errors.
Look for server-side issues
Sometimes the problem is not Authy at all.
The website or app you are trying to access may be having an outage, rate limit problem, or authentication bug.
- Try logging in from another browser or device.
- Check the service status page if one exists.
- Wait a few minutes and request a new code.
- Try another two-factor method if available, such as backup codes or a security key.
Services using Authy through Twilio or another identity platform can also experience temporary delays.
In those cases, repeated attempts may fail until the backend recovers.
Use account recovery carefully
If Authy is installed on a new phone and the old one is unavailable, recovery steps may be required before codes work again.
This process can vary depending on whether multi-device was enabled, whether the phone number changed, and whether your backups were intact.
- Open Authy and confirm your phone number.
- Follow the device authorization prompts carefully.
- Restore access only through official Authy recovery methods.
- Avoid third-party tools that claim to bypass two-factor authentication.
Recovery errors can look like code failures, but the deeper issue is often that the device has not been trusted yet.
Prevent future Authy code problems
Once your login works again, a few habits can reduce the chance of another failure.
Good two-factor authentication hygiene matters, especially for email, banking, cloud storage, and cryptocurrency accounts.
- Keep your device time on automatic.
- Update Authy and your operating system regularly.
- Save backup codes in a secure password manager.
- Confirm your phone number and recovery options are current.
- Review trusted devices after any phone replacement.
Using a password manager, hardware security key such as YubiKey, or multiple recovery options can reduce dependence on a single phone app.
When to contact support
If none of the fixes work, contact the service you are trying to access rather than Authy first, because the account system usually owns the two-factor verification policy.
Provide clear details so support can verify the problem quickly.
- The exact account or service name
- The device type and operating system
- When the problem started
- Whether the code is rejected, expired, or never accepted
- Any recent phone number, device, or app changes
With the right information, support can often reset two-factor authentication or issue recovery steps that restore access without compromising account security.