Projects using the default email provider experiencing errors sending emails

This incident has been resolved.

The fix has been applied to all existing projects as well. At this time, things are looking back to normal, but we will continue monitoring for further issues.

The change for the default email provider is still rolling out to existing projects, and is about 60% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp

The change for the default email provider is still rolling out to existing projects, and is about 32% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp

The change for the default email provider is still rolling out to existing projects, and is about 15% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp

We've made the swap to our new upstream provider for all newly created projects. We're working pushing the change out to all existing projects.

However, we still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp

We have identified an issue with our upstream email provider, and are working to move this to a different service.

In the meantime, we would always suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp

We are currently investigating this issue.