Supabase Status Page Drops SMS and Webhook Alerts, Resubscribe

Supabase moved its status page to incident.io on Oct. 8, 2026, and subscribers who got outage alerts by SMS, Slack, webhook or RSS stopped receiving them. Slack and RSS users must resubscribe. SMS and webhook alerts are gone: the new page does not support them (Supabase changelog, “Status page moves to incident.io,” Oct. 8, 2026).

What changed

The address is still status.supabase.com. Supabase said email subscribers carried over automatically. SMS, Slack, webhook and RSS subscribers did not. The new page supports only email, RSS and Slack. A team that wired SMS or a webhook into a pager, a chat bot or an internal tool needs a different channel.

Email subscribers get one addition: they can pick products and regions. A team on a single region no longer receives every notice.

What to do

• Check how your team hears about Supabase incidents. An SMS or webhook alert has been dead since Oct. 8.
• Resubscribe at status.supabase.com by Slack, RSS or email.
• Point the new email or RSS feed at any tool a webhook used to feed, or poll the page on a schedule.
• Set the product and region filters while you are there.

The other side of the dashboard

A status page is only as good as what feeds it. Google’s postmortem for Firebase’s Sept. 28-29 iOS crash said the Firebase and Google Ads status dashboards “remained green” because they rely mainly on server-side health metrics. The Pragmatic Engineer newsletter, in an Oct. 9 post, called the incident handling “shockingly poor.” Google committed to integrate SDK-related outage information into its dashboards.

The take

Hosting the status page with a vendor is sensible. Dropping webhooks is the cost, and it lands on the teams that automated their response. A silent channel gives no sign that alerts stopped.

Test your alert path now. Resubscribe, confirm a message arrives, and name who owns the channel. An outage is a poor time to learn the alerts stopped on Oct. 8.