2
Add Supabase to Atlassian Statuspage third-party component directory (statuspage.io - monitoring)
Source: supabase/supabase#46231 · opened by @tiwonl
Summary Request to add Supabase to Atlassian's Statuspage third-party component directory, so customers can automatically display Supabase component status on their own status pages. Context Many of us run platforms on Supabase and host public status pages on Atlassian Statuspage. To accurately reflect the health of our service, we want to surface Supabase's status (Database, Auth, Edge Functions, Storage, Realtime, etc.) on our own status page. Atlassian Statuspage supports this through their third-party component directory. Currently 150+ services are listed, including Cloudflare, Stripe, AWS, GitHub, Mailgun, and SendGrid. When activated, the component status auto-updates whenever the upstream provider updates their status page. Supabase is not currently in this directory. Why this matters Without this listing, customers have to choose between: 1. External uptime checks (UptimeRobot, etc.) which don't reflect Supabase's actual reported stat…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add a scoped, read-only metrics / monitoring API key (alternative to service_role)
7 votes · 0 comments
Feature Request: Add Bitbucket Support for Supabase Branching
5 votes · 0 comments
Allow Customization of /migrations Directory in config.toml for Supabase Migrations and Shadow Database
7 votes · 0 comments
Enhanced SQL Query Management for Supabase CLI: A Proposal for Query File and Folder Support
4 votes · 0 comments
Adding custom API keys with selectable Postgres role for backend components
1 vote · 0 comments
No comments yet.