What happened
Supabase reported a bigger problem starting July 30, 2026 at 17:38 UTC. It lasted about 19 hours, recovering on July 31 at 13:26 UTC. Supabase has since marked it resolved. The facts available are thin, so this piece stays honest about that rather than filling in gaps.
Who this kind of outage hits, and how they usually find out
If your app or your automations run on Supabase, a 19-hour disruption is a long time for things to go quietly wrong. The people who feel it first are often not you. They are your users, hitting a form that silently fails, a login that goes nowhere, a workflow that stops producing results. You find out when someone emails to ask why their account is broken, or why the report they expected never arrived. By then the problem has been running for hours and you are already behind.
That gap, between when the tool stopped working and when you heard about it, is the part that costs you. Not just time. Trust.
Why this is especially rough without a technical background
When a database or backend tool goes quiet, there is usually no error on your screen. Your app looks fine from where you sit. Your automations show no obvious failure. The work just stops moving, silently, and nothing inside the tool tells you. If you are not someone who reads logs or watches server responses, the first real signal is an unhappy customer. That is a hard position to recover from, because you are explaining a problem you did not know you had.
Timeline
- July 30, 2026 at 17:38 UTC, Supabase reported a bigger problem on its public status page.
- The disruption ran for about 19 hours.
- July 31, 2026 at 13:26 UTC, Supabase marked the issue resolved.
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 check anything yourself. That turns “my customer told me something is broken” into “I got a heads-up within a minute of Supabase’s own report.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you drop in. So if the trouble is on your side rather than Supabase’s, that surfaces too, in the same place.
To be straight about what this is: NoCrash does not find the outage before Supabase’s own status page does. It reads that page and tells you fast, in plain English, alongside everything else you build on.
The authoritative account
For the official record of this outage, go to Supabase’s status page: https://stspg.io/fptknzxz37wz