On July 27, 2026, Supabase reported a bigger problem starting at 17:54 UTC. It lasted about one hour and was marked resolved at 19:01 UTC. Supabase has confirmed the disruption is over.
Who this kind of outage hits, and how they usually find out
If your app or workflows run on Supabase, a database problem does not announce itself to you. It announces itself to your users first. Someone tries to log in, load their data, or submit a form, and nothing happens. They email you, or they just leave. You find out when a customer says “your app is broken,” not when the thing actually broke. That gap, between when the tool stopped working and when you heard about it, is where the damage happens.
Why this is especially rough if you are not an engineer
There is no error on your screen. Your workflow builder looks fine. Your app might even load. The work just quietly stops moving, queries go nowhere, and you have no way to know unless you happen to be testing the exact thing that broke at the exact moment it broke. Most people are not. So the first real signal is an unhappy customer, sometimes hours later, sometimes the next morning. You then have to piece together what happened, when, and whether anything needs to be fixed on your side, all while apologizing to someone who already lost trust.
What the timeline looked like
- 17:54 UTC – Supabase reported a bigger problem on its public status page.
- 19:01 UTC – Supabase marked the issue resolved.
- Total duration – about 1 hour.
That is a tight window in absolute terms, but if your app was serving customers during that hour, one hour is long enough to matter.
How a watcher catches this before your users do
NoCrash reads Supabase’s public status page every minute. The moment Supabase flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to go check anything. You find out within a minute of Supabase’s own report, not an hour later from a frustrated customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token, so a quiet stall on your own side surfaces too. If you give it a URL or add a small JS snippet to your app, it watches that as well. The idea is one place that tells you, in plain English, when something you depend on or something you built goes quiet.
To be clear about what it does not do: NoCrash does not find the outage before Supabase’s own status page does. It reads that page and tells you fast. That is the thing it does.
For the authoritative account of this outage, see Supabase’s own status page: https://stspg.io/m4xm198ksyf6