← Back to Supabase History
minor✓ Resolved
Edge Traffic Issues
Status
resolved
Duration
4h 24m
Updates
4
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedWed, May 13, 2026, 08:40 PM
This incident has been resolved.
identifiedWed, May 13, 2026, 07:50 PM
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.
investigatingWed, May 13, 2026, 05:31 PM
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.
investigatingWed, May 13, 2026, 04:46 PM
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.
investigatingWed, May 13, 2026, 04:15 PM
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.
📊 TECHNICAL DETAILS
Internal ID
6d3ba388-26c5-4dcc-80b8-e3977049982a
External ID
ybxpvtjys08w
🕐 Started
Wed, May 13, 2026, 04:15 PM
🔄 Last Updated
Wed, May 13, 2026, 08:40 PM
✓ Resolved
Wed, May 13, 2026, 08:40 PM
MINOR
Impact Level
4h 24m
Total Duration
4
Status Updates
Affected Components
Edge Functions
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed