Thanks for the insight! To clarify why we expect such a burst: The contest offers a special prize for the first 100 users to successfully submit their entries. While the total traffic might not hit exactly 2,000, we are realistically expecting at least 1,000+ concurrent users racing to be in that Top 100. This 'FOMO' effect is what creates the massive spike in Auth and Storage requests at the exact opening second. I will definitely follow your advice to contact Supabase support directly to whitelist our project and will look into temporary CPU scaling (Large instance) for the launch window.
Thanks for the insight! To clarify why we expect such a burst: The contest offers a special prize for the first 100 users to successfully submit their entries. While the total traffic might not hit exactly 2,000, we are realistically expecting at least 1,000+ concurrent users racing to be in that Top 100. This 'FOMO' effect is what creates the massive spike in Auth and Storage requests at the exact opening second. I will definitely follow your advice to contact Supabase support directly to whitelist our project and will look into temporary CPU scaling (Large instance) for the launch window.