# Supabase outage reports and status Canonical page: https://iszdown.com/now/supabase Status: Provider reports operational 24-hour window (UTC): 2026-10-21T01:00:00.000Z to 2026-10-22T01:00:00.000Z Recorded outage reports in this window: 0 Last successful estimated-activity check: No usable observation available Check Supabase availability, incident history, downtime reports, and website performance. ## How to interpret this page Estimated down reports are based on US problem-related activity. Values are relative activity from 0 to 100, not counts of submitted reports. The HTML chart averages samples into ten-minute intervals. Partial samples are excluded and missing samples are not invented. Recorded outage reports and estimated activity are separate signals. Neither confirms that every user is affected. Missing or stale data does not establish that a service is working. Methodology: https://iszdown.com/methodology ## Citation Cite [Supabase on Iszdown](https://iszdown.com/now/supabase), include your access time and the observation time above, and qualify estimated activity as an estimate. Recheck before describing current status. Iszdown is independent of the monitored provider. ## Estimated activity samples No usable activity samples are available for this service in this window. ## Evidence and recovery Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. Provider marked the incident resolved; independent website recovery is still being checked. ## Website measurements Successful sampled checks (24h): Unknown (0/0). Restricted checks: 0. Median response: Unknown ms. P95 response: Unknown ms. These are sampled public website checks from one US server, not continuous uptime or authenticated app/API tests. Missing data stays unknown. ## Official provider evidence Updated 2026-10-22T00:59:49.000Z. - ap-east-1: operational - [Project lifecycle operations such as project creation, pausing, and restoration, in all regions](https://status.supabase.com/incidents/01M5FHP5PVQBY4NVTBBH9XG0CH): resolved; updated 2026-10-21T16:51:51Z - [Projects stuck in restarting state](https://status.supabase.com/incidents/01M5DN6V02FJHZTE9390XJM9YY): resolved; updated 2026-10-21T05:39:55Z - [Support Form Errors](https://status.supabase.com/incidents/01M5AJFRAM620A395B243YX1K6): resolved; updated 2026-10-19T18:13:51Z - [Project creation errors ap-ne1](https://status.supabase.com/incidents/01M548Q6TQZCWECMHJH7PZ9EMS): resolved; updated 2026-10-17T07:49:32Z - [Realtime latency](https://status.supabase.com/incidents/01M4S5FT4GCZ8BWV2W1RB5WXNE): resolved; updated 2026-10-14T20:25:15Z - [Edge Function Degradation](https://status.supabase.com/incidents/01M4RTJRV55MN1WZDT7KTSAKK5): resolved; updated 2026-10-13T18:24:49Z - [Log ingestion impaired](https://status.supabase.com/incidents/01M4RT1HA64EWGKK2NJJ00Z7M5): resolved; updated 2026-10-13T01:30:33Z - [Intermittent connection errors via the connection pooler in us-east-1](https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K): resolved; updated 2026-10-21T16:27:59Z ## Daily outage history Dates use America/New_York. Green means no issues observed with sufficient monitoring; pink means official incidents, repeated website failures, or reports from at least three network addresses. Gray means insufficient coverage. These are daily evidence summaries, not guaranteed uptime. | Date | Daily assessment | Observed hours | Official incidents | | --- | --- | --- | --- | | 2026-09-01 | Service issues detected | 0 | 1 | | 2026-09-03 | Service issues detected | 0 | 1 | | 2026-09-04 | Service issues detected | 0 | 1 | | 2026-09-10 | Service issues detected | 0 | 1 | | 2026-09-11 | Service issues detected | 0 | 1 | | 2026-09-16 | Service issues detected | 0 | 1 | | 2026-09-19 | Service issues detected | 0 | 1 | | 2026-09-22 | Service issues detected | 0 | 1 | | 2026-09-23 | Service issues detected | 0 | 2 | | 2026-09-24 | Service issues detected | 0 | 3 | | 2026-09-29 | Service issues detected | 0 | 1 | | 2026-09-30 | Service issues detected | 0 | 1 | | 2026-10-01 | Service issues detected | 0 | 1 | | 2026-10-02 | Service issues detected | 0 | 1 | | 2026-10-03 | Service issues detected | 0 | 1 | | 2026-10-04 | Service issues detected | 0 | 1 | | 2026-10-05 | Service issues detected | 0 | 1 | | 2026-10-06 | Service issues detected | 0 | 2 | | 2026-10-12 | Service issues detected | 0 | 3 | | 2026-10-13 | Service issues detected | 0 | 2 | | 2026-10-14 | Service issues detected | 0 | 1 | | 2026-10-17 | Service issues detected | 0 | 1 | | 2026-10-19 | Service issues detected | 2 | 1 | | 2026-10-21 | Service issues detected | 20 | 1 | ## About Supabase monitoring This page combines the available Supabase report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works. ## Troubleshooting ### Supabase will not open Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption. ### Supabase is slow or only one feature fails Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature. ## Frequently asked questions ### Is Supabase down right now? Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T01:01:20.000Z. ### How many Supabase outage reports are there today? The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T01:00:00.000Z to 2026-10-22T01:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate. ### Why does Supabase show operational when it is not working for me? An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Supabase feature. ### When was Supabase status last updated? The latest status observation was 2026-10-22T00:59:49.000Z. Only matched product components and incidents are shown. The assessment is recent. ### Has Supabase had outages before? The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime. ### How do I follow Supabase or report a problem? Use “Watch this service” to save Supabase in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets. ## Related services - [Supabase](https://iszdown.com/now/supabase)