Supabase Status

Resolved: This incident has been resolved, and log delivery has returned to normal.

During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period.

Thank you for your patience while we worked to resolve this.

Monitoring: Logging systems have returned to normal operation.

During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period.

We will continue monitoring closely to ensure ongoing stability.

Investigating: Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

Resolved: All changes hav been applied.

Monitoring: The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.

Identified: We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.

Investigating: We are investigating reports of connectivity issues to project API endpoints.

Resolved: We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure.

We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support.

The incident is now resolved

Identified: Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe.

Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad.

Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side.

Investigating: We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users.

Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses.

Investigating: We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more.

Investigating: We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.