I ran a passive outside-in check over 649 public apps (Show HN posts from Jan 2025 to Oct 2026, plus two maker directories) to see how often a live app has quietly stopped working. 86 of them load a page whose code points at a Supabase project.
For 31 of those 86, the project's <ref>.supabase.co hostname no longer resolves, but the app's landing page still loads normally. Sign-in and saving fail, and a monitor that pings the homepage still says "up".
NXDOMAIN looks the same for a paused project and a deleted one. The storage hostname still reaches a gateway, though, and it answers differently: curl -i https://<ref>.storage.supabase.co/storage/v1/version
The user conducted an analysis of 649 public apps to determine how many are backed by Supabase projects that are paused or removed. They found that 31 out of 86 apps have a Supabase project whose hostname no longer resolves, yet the app's landing page still loads. The user seeks a method to distinguish between paused and deleted projects from an external perspective.