Hosted email OTP accepted but not delivered for custom-domain recipients

We are seeing a hosted email OTP delivery failure and would appreciate a delivery-log review.

Setup:

  • React + Vite web application
  • @web3auth/auth 11.8.2
  • sapphire_mainnet
  • Hosted/default Email Passwordless OTP using the code flow
  • Redirect UX
  • The exact non-wildcard HTTPS origin is allowlisted
  • Google login works on the same Web3Auth project

Observed behavior:

  • The hosted /v8/authorize page opens and says that a 6-digit verification code was sent.
  • The passwordless start request returns success with a tracking ID.
  • No OTP email arrives in Inbox, Spam, or Trash after five minutes.
  • We reproduced this with both a primary address on a custom domain and a plus alias on the same domain.
  • The primary address successfully received messages from no-reply@web3auth.io as recently as July 16, so this mailbox and route previously worked.
  • We submitted the official resubscribe form successfully, waited, and retested. Delivery still did not occur.
  • An HTTP 427 response appeared only after repeated QA attempts. After a cooldown, the start request succeeded again, but accepted attempts still produced no email.
  • There are no Siftr application errors during the accepted attempts, and the Web3Auth status page reports the mail services as operational.

Could support please inspect the SendGrid/mail delivery events for suppression, bounce, domain blocking, quota, or rate limiting? We can provide the affected addresses, exact UTC attempt windows, client/project details, and network evidence privately to a MetaMask support representative.

@yashovardhan, you previously asked for delivery details privately in similar cases. This new forum account is not yet allowed to send a private message. Please reply here or open a private thread with me, and I will send the affected addresses and exact UTC attempt windows there.

Hi @Derek_Smith thanks for bringing this up let me ask the team - we’ll be right back with you

@shana hey just wanted to circle back on this and see if the devs were able to confirm the issue / fix timeline – thanks!

Hi still waiting for the team to get back to us, let me send a reminder notification. Sorry for the wait