A question about auth rate limits
Hi, everyone in the help channel:
I have a Next.js project integrated with Supabase Auth, and email registration is used as the registration method. Yesterday, during a class, nearly 80 people registered within a short period of time (as shown in the figure, most registration requests were within half an hour). They all received the registration confirmation emails and completed the registration. However, as shown in the figure, I received an email from Supabase suggesting that I should configure SMTP. Therefore, I looked into the documentation regarding auth rate limits. Now I have two questions:
Why didn't the high concurrency of registration requests trigger the rate limit of 2 requests per hour for the
Why were my users able to smoothly receive the registration confirmation emails, but this behavior triggered a prompt from Supabase, which told me it was due to a large number of email bounces?
Can anyone help me with these questions? Thank you again.
I have a Next.js project integrated with Supabase Auth, and email registration is used as the registration method. Yesterday, during a class, nearly 80 people registered within a short period of time (as shown in the figure, most registration requests were within half an hour). They all received the registration confirmation emails and completed the registration. However, as shown in the figure, I received an email from Supabase suggesting that I should configure SMTP. Therefore, I looked into the documentation regarding auth rate limits. Now I have two questions:
Why didn't the high concurrency of registration requests trigger the rate limit of 2 requests per hour for the
/auth/v1/signupWhy were my users able to smoothly receive the registration confirmation emails, but this behavior triggered a prompt from Supabase, which told me it was due to a large number of email bounces?
Can anyone help me with these questions? Thank you again.
