Supabase incident
Shared SMTP service has low deliverability for some users
Resolved after 8 hours 21 minutes, affecting Auth, on December 24, 2025.
A fix has been deployed, all new projects are fully operational. We've finished backporting the fix to affected projects and now monitoring.
Affected components
Update timeline
- investigating Dec 24, 2025, 03:33 PM UTC
We are currently investigating an issue where some users have reported failures when sending email via the Shared SMTP service. If you are impacted, and need email services working immediately, you can work around this immediately by following best practice for production use cases and configure custom SMTP: https://supabase.com/docs/guides/auth/auth-smtp
- investigating Dec 24, 2025, 03:58 PM UTC
We are currently investigating an issue where some users have reported failures when sending email via the Shared SMTP service. This is also impacting newly creating projects. If you are impacted, and need email services working immediately, you can work around this immediately by following best practice for production use cases and configure custom SMTP: https://supabase.com/docs/guides/auth/auth-smtp
- investigating Dec 24, 2025, 05:01 PM UTC
We are continuing to investigate this issue. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 05:41 PM UTC
We have identified the issue, and we are working on the fix. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 06:30 PM UTC
We have implemented a fix, and all new projects should now be fully operational. We are now working on backporting it to the affected projects. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 07:27 PM UTC
We have implemented a fix, and all new projects should now be fully operational. We are rolling out a backporting fix to the affected projects; this is going to take around 3 hours. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 08:26 PM UTC
A fix has been deployed, all new projects are now fully operational. We're currently backporting the fix to affected projects (30% complete). An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 09:28 PM UTC
We've deployed a fix and confirmed all new projects are fully operational. Remediation for previously affected projects is underway and 50% complete. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- identified Dec 24, 2025, 10:31 PM UTC
A fix has been deployed, all new projects are fully operational. We're currently backporting the fix to affected projects (69% complete). An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp
- monitoring Dec 24, 2025, 11:42 PM UTC
A fix has been deployed, all new projects are fully operational. We've finished backporting the fix to affected projects and now monitoring.
- resolved Dec 24, 2025, 11:55 PM UTC
This incident has been resolved.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.