ActiveMajorSupabase
Partial outageChecked
Supabase is reported as having a partial outage
On the official feed, Supabase appears in an open incident. It may not be you.
Email alerts for this stack
One link confirms your address and turns them on. No password or card.
https://outagedeck.com/stack?p=github,vercel,supabase,sentry
Already have an account, or sign in with GitHub or Google? Turn this board into alerts there.
Your vendors right now
Each row is the status published on the official source OutageDeck reads for that vendor. The check time and direct source link stay visible so you can verify it yourself.
Open incidents in this stack
Straight from the official incident source for each vendor, newest update first.
How to read this board
OutageDeck re-reads the official status feed of all 180 tracked providers about every 10 minutes and stores what it finds. This board simply shows you the subset you chose. Green means none of those vendors has acknowledged an incident in its official feed. It does not mean your region, tenant, or request path is healthy. If OutageDeck or a vendor feed stops refreshing, the check time exposes that. A read failure is never converted into a provider outage. Browse every tracked provider or set up alerts so the next one finds you instead.
Want this board somewhere your team already looks? Turn it into a status wall: one line of Markdown for a README, wiki, or dashboard, and it keeps itself current.
Using a coding agent? The same verdict is one tool call away: connect the MCP server and your agent can ask "is it us or them?" mid-task, before it starts tearing apart your code.
A stack board holds up to 12 vendors and nothing about it is stored. Reload it, bookmark it, or paste it into your incident channel.