Project Status reports unhealthy services

[supabase-search[bot]]

This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.

If the project was recently restored, it can take up a couple minutes to become fully operational.

Services rely on the backend database. Unhealthy services can indicate a database being overloaded due to being undersized or not tuned appropriately.

• Review this troubleshooting doc to determine if it could be a resource issue.
• If services recover and become unhealthy again, there is likely a repeated issue overloading the database.

Possible resolutions:

• Restart the database in Project Settings (this may be only a temporary fix if the project is undersized / unoptimized).
• Increase project resources in Infrastructure.
• Performance Tune the database.

The "Edge Functions Unhealthy" indicator is based on a platform-level health check, not the project's own functions. Confirm the actual functions work by invoking them directly. If functions are working fine, this is likely a false positive.

Check the following if only Edge Functions service reports unhealthy:

• Verify actual function behavior by invoking the edge function directly (e.g., via cURL with a CORS request). If it responds correctly, the health indicator is likely a false positive.
• Check invocation logs. Filter logs using the keyword ~"health" to see if health check calls are failing and if any errors are presented.
• Restart the database in Project Settings. This has resolved the unhealthy state in some cases, particularly when it's a transient issue.