Supabase Status · History · Incident #3705
RESOLVEDAccess Issues From Some Providers in Brazil
Minor · Started May 14, 2026 · 3:34 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Supabase Status · History · Incident #3705
RESOLVEDMinor · Started May 14, 2026 · 3:34 PM
Duration
32d 16h 40m
Severity
Minor
Detection lead
—
User reports
—
Summary
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Started
May 14, 2026 · 3:34 PM
Resolved
Jun 16, 2026 · 8:15 AM
Duration
32d 16h 40m
Severity
None
Event timeline
Investigating
May 14 · 3:34 PM SupabaseWe are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
Investigating
May 14 · 3:54 PM SupabaseWe have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share.
Investigating
May 14 · 4:37 PM SupabaseWe have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution.
Identified
May 14 · 10:23 PM SupabaseWe are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.
Identified
May 19 · 10:30 PM SupabaseWe are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.
Identified
Jun 3 · 9:32 PM SupabaseWe continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue.
Identified
Jun 9 · 1:26 PM SupabaseWe are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation.
Monitoring
Jun 12 · 2:42 PM SupabaseWe continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.
Monitoring
Jun 15 · 4:52 PM SupabaseThe top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.
Resolved
Jun 16 · 8:15 AM SupabaseThe top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026