Supabase Status
System status
View historical uptime →Incident overview
Total incidents
78
Active now
0
Resolved
78
Avg. resolution
47h 17m
Recent incidents
View all →Project creation errors ap-ne1
Realtime latency
Edge Function Degradation
Log ingestion impaired
Increased rates of Pooler connection timeouts in us-east-1
pgBouncer issues on some older projects
Projects failing to load Supautils in multiple regions
Increased response times for requests
Project Creation Failures
User unable to log in to Supabase Dashboard
Uptime Comparisons
Frequently asked questions
Is Supabase down right now?
Supabase is currently operational. DevHelm monitors Supabase's official status page continuously and updates this page every 5 minutes.
What is Supabase's current uptime?
Supabase has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Supabase's official status page data.
How many incidents has Supabase had recently?
Supabase has experienced 78 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 47h 17m. All incidents are currently resolved.
What components does Supabase monitor?
DevHelm tracks 1 individual component for Supabase, including ap-east-1. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Supabase outages?
You can subscribe to Supabase's incident feed via Atom/RSS at devhelm.io/status/supabase/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Supabase as a dependency in your DevHelm workspace.
What SLA does Supabase offer?
See the full Supabase SLA report at devhelm.io/sla/supabase — including their official uptime guarantee, pricing tiers, credit policy, and how their measured uptime compares to their SLA commitment.
About Supabase status monitoring
This page provides real-time operational status for Supabase, powered by DevHelm's continuous monitoring infrastructure. We track Supabase's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Supabase status data is refreshed every 5 minutes. We currently track 1 individual component, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Supabase in your stack
Get alerted when Supabase has issues — before your users notice. Set up in 30 seconds.