How Long Does a Verification Email Take? Real Times

Updated October 28, 2026 · 6 min read

Most verification emails arrive within a few seconds to a couple of minutes, though some senders take longer; the table below shows each service's average. If nothing has come after five minutes, check the address and your filters, then resend once. On a rented inbox you can wait up to 25 minutes, after which the order cancels itself and refunds you.

This page is for anyone staring at a “check your inbox” screen and wondering how long to wait, and for developers choosing a timeout. Instead of a guess, it uses OTPGmail's own order data, refreshed automatically, for twelve services people sign up for every day.

Average wait by service, from live orders

How the figures are measured. The average wait runs from the moment an inbox is rented to the moment its first code lands, so it includes the time a person takes to paste the address and submit the form; the email itself often travels faster. “Got a code” is the share of orders that received one before the waiting window closed, out of the orders that either got a code or timed out. Orders a customer cancelled by hand are left out, and a service needs at least 20 such orders in 30 days before a number is shown.

Vinted can be joined with an email address and a code, which is what the Vinted row in the table measures, or with “Continue with Google”, which needs a Google account you can sign in to rather than an emailed code. Signing up for Vinted with an email code covers the first route, and links to the second.

Read the two columns together. When a service's average is fast but its share is low, the email comes quickly when it comes at all, and the real obstacle sits earlier in the sign-up. When the average is slow but the share holds up, patience pays.

Why verification emails get delayed

• The sender's queue. At busy times senders batch their mail. CapCut's help, for example, says its code can take one to three minutes when servers are under load.
• Checks before sending. Many platforms score a sign-up first and send the email only if it passes. A sign-up that is held back looks exactly like a slow email, except that nothing ever arrives.
• Resends and limits. Each resend can replace the previous code, and repeated requests can trigger a pause of several minutes during which nothing is sent.
• Filters on your side. Your own mailbox may move the message to junk, a Promotions or Other tab, or hold it while a work filter checks it.
• A device that is not fetching. The email reached your mailbox, but the phone app has not refreshed yet.
• A typo. The email was sent promptly, to an address that is not yours.

What to do at one, five and 25 minutes

1. At one minute: do nothing yet. Check that the address shown on the code screen is correct, and leave the page open.
2. At three to five minutes: in your own mailbox, search the whole account for the sender's name, including junk and tabs. Then resend once and use only the newest code. On a rented inbox there is nothing to search: OTPGmail reads the inbox for you and shows the code on your order page.
3. At ten minutes or more: the site most likely did not send. Look for an unresolved captcha, a phone-number prompt or an error on the sign-up page, and work through the checklist for missing codes.
4. At 25 minutes on a rented inbox: the order cancels itself and 100% goes back to your balance, usually within a minute, as the refund policy describes. You can also cancel earlier for the same refund.

Once a code does arrive, enter it straight away: the website's own clock starts when it sends the code, and OTP expired or invalid explains what happens if you wait too long. For CapCut specifically, see CapCut code not sending to email.

For developers: timeouts and polling

If a script waits for the code, design for the slow cases rather than the average:

• Poll GET /v1/orders/{id} every 3–5 seconds while the status is waiting_code; polling faster returns the same stored data.
• Use the order's codeDeadlineAt as your hard timeout. Before that moment a missing code is still normal; after it, the order is cancelled and refunded automatically.
• Budget per service. Treat the averages above as a floor, not a ceiling, and allow several times that for the slowest senders in the table before your script gives up early.
• Treat a timeout as an expected outcome: log it, rent a fresh inbox if the flow should continue, and send a new Idempotency-Key for the new order.

The receive email OTP overview shows the whole flow from renting to reading the code.

Frequently asked questions

How long does a Snapchat verification email take?

On rented inboxes at OTPGmail the average is about 2 minutes, but Snapchat leads with a phone-number field, so make sure you switched to the email option; otherwise nothing is emailed at all.

Why is my verification email delayed in Outlook?

Outlook may file automated mail under the Other tab or in Junk Email. Search the whole mailbox for the sender's name, and mark the message as not junk so the next one reaches your inbox.

Should I keep pressing resend?

No. Resend once after a few minutes, then wait. Repeated requests can replace the code you were waiting for and trigger a pause during which nothing is sent.

Does a slow code mean my account is blocked?

Not by itself. A delay usually comes from the sender's queue or your filters. If no code ever arrives at any address, the site probably held the sign-up back, and its help centre is the place to ask.

Related guides