Supabase service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Is Supabase Down? Check supabase.com Status and Outages
Run a live reachability check for supabase.com. Compare the regional responses with the problem you see in Supabase.
Find Supabase help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Understanding Supabase connection and service problems
Supabase project APIs, database connections, Auth and Storage do not share every failure.
The checker above requests supabase.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Supabase action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Supabase status information and official help
Supabase help and reporting
Match database, Auth, Storage or the project product involved.
Open supabase.com
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Where to report a Supabase problem
Match database, Auth, Storage or the project product involved.
Open Supabase help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Include these details in a Supabase report
Project/region, database/Auth/Storage action, SDK/driver, request/error ID and time without keys or records.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Supabase.
What to check when Supabase is not working
These are troubleshooting comparisons, not claims that Supabase is currently experiencing a particular incident.
Start with the action that failed
Identify the project/region and the product returning the error and compare its health/status information.
Narrow down the affected service
Use a minimal authorised read and inspect project logs before changing policies or restarting clients widely.
Read the actual checker response
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Supabase is down: a step-by-step workflow
- Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
- Run the supabase.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
- Compare the relevant provider information. Open Supabase status and check whether the named service and incident time fit your error.
- Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.
If Supabase Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Supabase seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open supabase.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Supabase issue.
3. Compare permitted network paths
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Supabase support.
Frequently asked questions about Supabase problems
Is Supabase down, or is the problem limited to one feature?
Run the supabase.com check and compare its original timestamps and responses with your actual error. Supabase project APIs, database connections, Auth and Storage do not share every failure.
Where can I report a problem with Supabase?
Use the official help/reporting resource linked above. Match database, Auth, Storage or the project product involved.
What should I check first when Supabase is not working?
Identify the project/region and the product returning the error and compare its health/status information. Use a minimal authorised read and inspect project logs before changing policies or restarting clients widely.
What information helps Supabase support investigate?
Project/region, database/Auth/Storage action, SDK/driver, request/error ID and time without keys or records.