iszdown
Menu
Service status & outage reports

Is Supabase down?

Check Supabase availability, incident history, downtime reports, and website performance.

https://supabase.com/ ↗
Provider reports operational

Mapped components are operational in the latest status update; individual experiences can vary.

0 recorded outage reports · rolling 24 hours

Estimated activity checked · Text version ↗

My watchlist

Service disruption activity for Supabase

Last 24 hours
0501002026-11-10T04:10:00.000Z: 0.02026-11-10T04:20:00.000Z: 0.02026-11-10T04:30:00.000Z: 0.02026-11-10T04:40:00.000Z: 0.02026-11-10T04:50:00.000Z: 0.02026-11-10T05:00:00.000Z: 0.02026-11-10T05:10:00.000Z: 0.02026-11-10T05:20:00.000Z: 0.02026-11-10T05:30:00.000Z: 0.02026-11-10T05:40:00.000Z: 0.02026-11-10T05:50:00.000Z: 0.02026-11-10T06:00:00.000Z: 0.02026-11-10T06:10:00.000Z: 0.02026-11-10T06:20:00.000Z: 0.02026-11-10T06:30:00.000Z: 0.02026-11-10T06:40:00.000Z: 0.02026-11-10T06:50:00.000Z: 0.02026-11-10T07:00:00.000Z: 0.02026-11-10T07:10:00.000Z: 0.02026-11-10T07:20:00.000Z: 0.02026-11-10T07:30:00.000Z: 0.02026-11-10T07:40:00.000Z: 0.02026-11-10T07:50:00.000Z: 0.02026-11-10T08:00:00.000Z: 0.02026-11-10T08:10:00.000Z: 0.02026-11-10T08:20:00.000Z: 0.02026-11-10T08:30:00.000Z: 0.02026-11-10T08:40:00.000Z: 0.02026-11-10T08:50:00.000Z: 0.02026-11-10T09:00:00.000Z: 0.02026-11-10T09:10:00.000Z: 0.02026-11-10T09:20:00.000Z: 0.02026-11-10T09:30:00.000Z: 0.02026-11-10T09:40:00.000Z: 0.02026-11-10T09:50:00.000Z: 0.02026-11-10T10:00:00.000Z: 0.02026-11-10T10:10:00.000Z: 0.02026-11-10T10:20:00.000Z: 0.02026-11-10T10:30:00.000Z: 0.02026-11-10T10:40:00.000Z: 0.02026-11-10T10:50:00.000Z: 0.02026-11-10T11:00:00.000Z: 0.02026-11-10T11:10:00.000Z: 0.02026-11-10T11:20:00.000Z: 0.02026-11-10T11:30:00.000Z: 0.02026-11-10T11:40:00.000Z: 0.02026-11-10T11:50:00.000Z: 0.02026-11-10T12:00:00.000Z: 0.02026-11-10T12:10:00.000Z: 0.02026-11-10T12:20:00.000Z: 0.02026-11-10T12:30:00.000Z: 0.02026-11-10T12:40:00.000Z: 0.02026-11-10T12:50:00.000Z: 0.02026-11-10T13:00:00.000Z: 0.02026-11-10T13:10:00.000Z: 0.02026-11-10T13:20:00.000Z: 0.02026-11-10T13:30:00.000Z: 0.02026-11-10T13:40:00.000Z: 0.02026-11-10T13:50:00.000Z: 0.02026-11-10T14:00:00.000Z: 0.02026-11-10T14:10:00.000Z: 0.02026-11-10T14:20:00.000Z: 0.02026-11-10T14:30:00.000Z: 0.02026-11-10T14:40:00.000Z: 0.02026-11-10T14:50:00.000Z: 0.02026-11-10T15:00:00.000Z: 0.02026-11-10T15:10:00.000Z: 0.02026-11-10T15:20:00.000Z: 0.02026-11-10T15:30:00.000Z: 0.02026-11-10T15:40:00.000Z: 0.02026-11-10T15:50:00.000Z: 0.02026-11-10T16:00:00.000Z: 0.02026-11-10T16:10:00.000Z: 0.02026-11-10T16:20:00.000Z: 0.02026-11-10T16:30:00.000Z: 0.02026-11-10T16:40:00.000Z: 0.02026-11-10T16:50:00.000Z: 0.02026-11-10T17:00:00.000Z: 0.02026-11-10T17:10:00.000Z: 0.02026-11-10T17:20:00.000Z: 0.02026-11-10T17:30:00.000Z: 0.02026-11-10T17:40:00.000Z: 0.02026-11-10T17:50:00.000Z: 0.02026-11-10T18:00:00.000Z: 0.02026-11-10T18:10:00.000Z: 0.02026-11-10T18:20:00.000Z: 0.02026-11-10T18:30:00.000Z: 0.02026-11-10T18:40:00.000Z: 0.02026-11-10T18:50:00.000Z: 0.02026-11-10T19:00:00.000Z: 0.02026-11-10T19:10:00.000Z: 0.02026-11-10T19:20:00.000Z: 0.02026-11-10T19:30:00.000Z: 0.02026-11-10T19:40:00.000Z: 0.02026-11-10T19:50:00.000Z: 0.02026-11-10T20:00:00.000Z: 0.02026-11-10T20:10:00.000Z: 0.02026-11-10T20:20:00.000Z: 0.02026-11-10T20:30:00.000Z: 0.02026-11-10T20:40:00.000Z: 0.02026-11-10T20:50:00.000Z: 0.02026-11-10T21:00:00.000Z: 0.02026-11-10T21:10:00.000Z: 0.02026-11-10T21:20:00.000Z: 0.02026-11-10T21:30:00.000Z: 0.02026-11-10T21:40:00.000Z: 0.02026-11-10T21:50:00.000Z: 0.02026-11-10T22:00:00.000Z: 0.02026-11-10T22:10:00.000Z: 0.02026-11-10T22:20:00.000Z: 0.02026-11-10T22:30:00.000Z: 0.02026-11-10T22:40:00.000Z: 0.02026-11-10T22:50:00.000Z: 0.02026-11-10T23:00:00.000Z: 0.02026-11-10T23:10:00.000Z: 0.02026-11-10T23:20:00.000Z: 0.02026-11-10T23:30:00.000Z: 0.02026-11-10T23:40:00.000Z: 0.02026-11-10T23:50:00.000Z: 0.02026-11-11T00:00:00.000Z: 0.02026-11-11T00:10:00.000Z: 0.02026-11-11T00:20:00.000Z: 0.02026-11-11T00:30:00.000Z: 0.02026-11-11T00:40:00.000Z: 0.02026-11-11T00:50:00.000Z: 0.02026-11-11T01:00:00.000Z: 0.02026-11-11T01:10:00.000Z: 0.02026-11-11T01:20:00.000Z: 0.02026-11-11T01:30:00.000Z: 0.02026-11-11T01:40:00.000Z: 0.02026-11-11T01:50:00.000Z: 0.02026-11-11T02:00:00.000Z: 0.02026-11-11T02:10:00.000Z: 0.02026-11-11T02:20:00.000Z: 0.02026-11-11T02:30:00.000Z: 0.02026-11-11T02:40:00.000Z: 0.02026-11-11T02:50:00.000Z: 0.02026-11-11T03:00:00.000Z: 0.02026-11-11T03:10:00.000Z: 0.02026-11-11T03:20:00.000Z: 0.02026-11-11T03:30:00.000Z: 0.02026-11-11T03:40:00.000Z: 0.02026-11-11T03:50:00.000Z: 0.02026-11-11T04:00:00.000Z: 0.024h ago18h ago12h ago6h agoNow
Disruption activity index (0–100). Published incidents and repeated check failures carry more weight than emerging problem patterns. This is not a report count or percentage of affected users. Gaps have no observations; connecting lines do not add measurements.

Observed disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.

Latest observation: 2026-11-11 04:06:49 UTC. Refreshes automatically while this page is visible.

No user-submitted outage reports in the last 24 hours.

Supabase outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

DecJanFebMarAprMayJunJulAugSepOctNov
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Supabase website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-11-11 04:04:50 UTC.

Checked address: https://supabase.com/

DNS lookup: 4 ms · TCP connection: 7 ms · TLS handshake: 23 ms. Certificate expires 2026-12-09; trusted connection: yes.

100%
Successful website checks (24h)
280 successful / 280 measurable checks

98 ms
Median response time

158 ms
95th percentile response time

Successful website response times, 0 to 306 milliseconds306 ms0 ms2026-11-10T04:11:42.000Z: 99 ms2026-11-10T04:16:51.000Z: 98 ms2026-11-10T04:22:00.000Z: 96 ms2026-11-10T04:27:05.000Z: 103 ms2026-11-10T04:32:10.000Z: 99 ms2026-11-10T04:37:13.000Z: 113 ms2026-11-10T04:42:18.000Z: 81 ms2026-11-10T04:47:23.000Z: 108 ms2026-11-10T04:52:28.000Z: 107 ms2026-11-10T04:57:33.000Z: 87 ms2026-11-10T05:02:38.000Z: 105 ms2026-11-10T05:07:44.000Z: 90 ms2026-11-10T05:12:54.000Z: 92 ms2026-11-10T05:18:05.000Z: 95 ms2026-11-10T05:23:14.000Z: 90 ms2026-11-10T05:28:24.000Z: 119 ms2026-11-10T05:33:32.000Z: 100 ms2026-11-10T05:38:42.000Z: 92 ms2026-11-10T05:43:52.000Z: 159 ms2026-11-10T05:49:00.000Z: 107 ms2026-11-10T05:54:09.000Z: 99 ms2026-11-10T05:59:13.000Z: 93 ms2026-11-10T06:04:19.000Z: 99 ms2026-11-10T06:09:24.000Z: 108 ms2026-11-10T06:14:28.000Z: 100 ms2026-11-10T06:19:34.000Z: 95 ms2026-11-10T06:24:41.000Z: 88 ms2026-11-10T06:29:50.000Z: 87 ms2026-11-10T06:35:00.000Z: 87 ms2026-11-10T06:40:11.000Z: 102 ms2026-11-10T06:45:20.000Z: 111 ms2026-11-10T06:50:28.000Z: 97 ms2026-11-10T06:55:38.000Z: 93 ms2026-11-10T07:00:46.000Z: 93 ms2026-11-10T07:05:54.000Z: 116 ms2026-11-10T07:11:04.000Z: 94 ms2026-11-10T07:16:12.000Z: 94 ms2026-11-10T07:21:17.000Z: 103 ms2026-11-10T07:26:22.000Z: 91 ms2026-11-10T07:31:30.000Z: 130 ms2026-11-10T07:36:40.000Z: 99 ms2026-11-10T07:41:47.000Z: 89 ms2026-11-10T07:46:56.000Z: 99 ms2026-11-10T07:52:06.000Z: 288 ms2026-11-10T07:57:14.000Z: 94 ms2026-11-10T08:02:22.000Z: 103 ms2026-11-10T08:07:32.000Z: 97 ms2026-11-10T08:12:42.000Z: 111 ms2026-11-10T08:17:49.000Z: 88 ms2026-11-10T08:22:58.000Z: 103 ms2026-11-10T08:28:08.000Z: 151 ms2026-11-10T08:33:12.000Z: 96 ms2026-11-10T08:38:17.000Z: 90 ms2026-11-10T08:43:22.000Z: 89 ms2026-11-10T08:48:27.000Z: 102 ms2026-11-10T08:53:30.000Z: 96 ms2026-11-10T08:58:37.000Z: 92 ms2026-11-10T09:03:42.000Z: 145 ms2026-11-10T09:08:47.000Z: 83 ms2026-11-10T09:13:52.000Z: 146 ms2026-11-10T09:18:57.000Z: 126 ms2026-11-10T09:24:04.000Z: 136 ms2026-11-10T09:29:07.000Z: 96 ms2026-11-10T09:34:12.000Z: 118 ms2026-11-10T09:39:18.000Z: 274 ms2026-11-10T09:44:27.000Z: 94 ms2026-11-10T09:49:34.000Z: 98 ms2026-11-10T09:54:44.000Z: 96 ms2026-11-10T09:59:54.000Z: 100 ms2026-11-10T10:05:05.000Z: 87 ms2026-11-10T10:10:12.000Z: 115 ms2026-11-10T10:15:21.000Z: 115 ms2026-11-10T10:20:29.000Z: 103 ms2026-11-10T10:25:38.000Z: 113 ms2026-11-10T10:30:46.000Z: 104 ms2026-11-10T10:35:57.000Z: 88 ms2026-11-10T10:41:04.000Z: 108 ms2026-11-10T10:46:08.000Z: 114 ms2026-11-10T10:51:18.000Z: 88 ms2026-11-10T10:56:28.000Z: 105 ms2026-11-10T11:01:38.000Z: 83 ms2026-11-10T11:06:48.000Z: 100 ms2026-11-10T11:11:58.000Z: 91 ms2026-11-10T11:17:07.000Z: 91 ms2026-11-10T11:22:14.000Z: 119 ms2026-11-10T11:27:24.000Z: 92 ms2026-11-10T11:32:34.000Z: 113 ms2026-11-10T11:37:42.000Z: 88 ms2026-11-10T11:42:49.000Z: 96 ms2026-11-10T11:47:54.000Z: 93 ms2026-11-10T11:53:02.000Z: 115 ms2026-11-10T11:58:10.000Z: 85 ms2026-11-10T12:03:20.000Z: 117 ms2026-11-10T12:08:30.000Z: 91 ms2026-11-10T12:13:40.000Z: 84 ms2026-11-10T12:18:49.000Z: 91 ms2026-11-10T12:23:59.000Z: 88 ms2026-11-10T12:29:08.000Z: 96 ms2026-11-10T12:34:16.000Z: 83 ms2026-11-10T12:39:24.000Z: 100 ms2026-11-10T12:44:34.000Z: 90 ms2026-11-10T12:49:45.000Z: 93 ms2026-11-10T12:54:52.000Z: 103 ms2026-11-10T13:00:05.000Z: 95 ms2026-11-10T13:05:12.000Z: 177 ms2026-11-10T13:10:21.000Z: 100 ms2026-11-10T13:15:28.000Z: 219 ms2026-11-10T13:20:38.000Z: 94 ms2026-11-10T13:25:47.000Z: 90 ms2026-11-10T13:30:56.000Z: 122 ms2026-11-10T13:36:06.000Z: 101 ms2026-11-10T13:41:13.000Z: 111 ms2026-11-10T13:46:22.000Z: 89 ms2026-11-10T13:51:32.000Z: 120 ms2026-11-10T13:56:36.000Z: 113 ms2026-11-10T14:01:44.000Z: 94 ms2026-11-10T14:06:52.000Z: 116 ms2026-11-10T14:12:04.000Z: 96 ms2026-11-10T14:17:12.000Z: 103 ms2026-11-10T14:22:22.000Z: 94 ms2026-11-10T14:27:31.000Z: 163 ms2026-11-10T14:32:41.000Z: 95 ms2026-11-10T14:37:50.000Z: 102 ms2026-11-10T14:43:00.000Z: 100 ms2026-11-10T14:48:11.000Z: 114 ms2026-11-10T14:53:18.000Z: 87 ms2026-11-10T14:58:26.000Z: 85 ms2026-11-10T15:03:36.000Z: 106 ms2026-11-10T15:08:42.000Z: 99 ms2026-11-10T15:13:52.000Z: 112 ms2026-11-10T15:18:58.000Z: 98 ms2026-11-10T15:24:06.000Z: 138 ms2026-11-10T15:29:16.000Z: 89 ms2026-11-10T15:34:26.000Z: 113 ms2026-11-10T15:39:34.000Z: 94 ms2026-11-10T15:44:45.000Z: 89 ms2026-11-10T15:49:54.000Z: 108 ms2026-11-10T15:55:05.000Z: 92 ms2026-11-10T16:00:12.000Z: 91 ms2026-11-10T16:05:19.000Z: 81 ms2026-11-10T16:10:28.000Z: 81 ms2026-11-10T16:15:36.000Z: 108 ms2026-11-10T16:20:46.000Z: 103 ms2026-11-10T16:25:54.000Z: 89 ms2026-11-10T16:31:05.000Z: 100 ms2026-11-10T16:36:12.000Z: 99 ms2026-11-10T16:41:22.000Z: 105 ms2026-11-10T16:46:30.000Z: 101 ms2026-11-10T16:51:38.000Z: 97 ms2026-11-10T16:56:47.000Z: 117 ms2026-11-10T17:01:52.000Z: 101 ms2026-11-10T17:07:00.000Z: 109 ms2026-11-10T17:12:10.000Z: 96 ms2026-11-10T17:17:18.000Z: 93 ms2026-11-10T17:22:26.000Z: 89 ms2026-11-10T17:27:37.000Z: 96 ms2026-11-10T17:32:46.000Z: 96 ms2026-11-10T17:37:55.000Z: 105 ms2026-11-10T17:43:05.000Z: 108 ms2026-11-10T17:48:12.000Z: 87 ms2026-11-10T17:53:22.000Z: 100 ms2026-11-10T17:58:30.000Z: 88 ms2026-11-10T18:03:40.000Z: 107 ms2026-11-10T18:08:51.000Z: 96 ms2026-11-10T18:14:01.000Z: 89 ms2026-11-10T18:19:10.000Z: 98 ms2026-11-10T18:24:18.000Z: 90 ms2026-11-10T18:29:28.000Z: 93 ms2026-11-10T18:34:38.000Z: 81 ms2026-11-10T18:39:49.000Z: 89 ms2026-11-10T18:44:56.000Z: 89 ms2026-11-10T18:50:06.000Z: 121 ms2026-11-10T18:55:11.000Z: 118 ms2026-11-10T19:00:16.000Z: 94 ms2026-11-10T19:05:25.000Z: 102 ms2026-11-10T19:10:34.000Z: 89 ms2026-11-10T19:15:45.000Z: 92 ms2026-11-10T19:20:54.000Z: 93 ms2026-11-10T19:26:05.000Z: 180 ms2026-11-10T19:31:13.000Z: 88 ms2026-11-10T19:36:22.000Z: 249 ms2026-11-10T19:41:32.000Z: 88 ms2026-11-10T19:46:43.000Z: 102 ms2026-11-10T19:51:52.000Z: 84 ms2026-11-10T19:56:58.000Z: 105 ms2026-11-10T20:02:03.000Z: 103 ms2026-11-10T20:07:05.000Z: 89 ms2026-11-10T20:12:11.000Z: 86 ms2026-11-10T20:17:18.000Z: 88 ms2026-11-10T20:22:27.000Z: 81 ms2026-11-10T20:27:36.000Z: 107 ms2026-11-10T20:32:44.000Z: 93 ms2026-11-10T20:37:53.000Z: 99 ms2026-11-10T20:43:04.000Z: 108 ms2026-11-10T20:48:12.000Z: 92 ms2026-11-10T20:53:21.000Z: 91 ms2026-11-10T20:58:30.000Z: 80 ms2026-11-10T21:03:42.000Z: 125 ms2026-11-10T21:08:49.000Z: 99 ms2026-11-10T21:13:57.000Z: 94 ms2026-11-10T21:19:03.000Z: 91 ms2026-11-10T21:24:07.000Z: 126 ms2026-11-10T21:29:12.000Z: 91 ms2026-11-10T21:34:22.000Z: 132 ms2026-11-10T21:39:28.000Z: 87 ms2026-11-10T21:44:37.000Z: 100 ms2026-11-10T21:49:44.000Z: 81 ms2026-11-10T21:54:54.000Z: 92 ms2026-11-10T22:00:05.000Z: 118 ms2026-11-10T22:05:12.000Z: 92 ms2026-11-10T22:10:18.000Z: 180 ms2026-11-10T22:15:28.000Z: 98 ms2026-11-10T22:20:39.000Z: 89 ms2026-11-10T22:25:46.000Z: 98 ms2026-11-10T22:30:52.000Z: 89 ms2026-11-10T22:35:56.000Z: 100 ms2026-11-10T22:41:05.000Z: 90 ms2026-11-10T22:46:12.000Z: 114 ms2026-11-10T22:51:22.000Z: 129 ms2026-11-10T22:56:28.000Z: 106 ms2026-11-10T23:01:38.000Z: 91 ms2026-11-10T23:06:49.000Z: 92 ms2026-11-10T23:11:59.000Z: 86 ms2026-11-10T23:17:08.000Z: 83 ms2026-11-10T23:22:19.000Z: 89 ms2026-11-10T23:27:26.000Z: 90 ms2026-11-10T23:32:34.000Z: 87 ms2026-11-10T23:37:43.000Z: 76 ms2026-11-10T23:42:52.000Z: 98 ms2026-11-10T23:48:01.000Z: 106 ms2026-11-10T23:53:10.000Z: 99 ms2026-11-10T23:58:21.000Z: 83 ms2026-11-11T00:03:30.000Z: 102 ms2026-11-11T00:08:40.000Z: 110 ms2026-11-11T00:13:46.000Z: 105 ms2026-11-11T00:18:56.000Z: 91 ms2026-11-11T00:24:02.000Z: 184 ms2026-11-11T00:29:09.000Z: 93 ms2026-11-11T00:34:17.000Z: 102 ms2026-11-11T00:39:27.000Z: 112 ms2026-11-11T00:44:37.000Z: 95 ms2026-11-11T00:49:45.000Z: 116 ms2026-11-11T00:54:52.000Z: 101 ms2026-11-11T01:00:02.000Z: 158 ms2026-11-11T01:05:10.000Z: 306 ms2026-11-11T01:10:19.000Z: 85 ms2026-11-11T01:15:29.000Z: 107 ms2026-11-11T01:20:39.000Z: 97 ms2026-11-11T01:25:43.000Z: 92 ms2026-11-11T01:30:52.000Z: 105 ms2026-11-11T01:35:59.000Z: 92 ms2026-11-11T01:41:06.000Z: 97 ms2026-11-11T01:46:10.000Z: 112 ms2026-11-11T01:51:14.000Z: 86 ms2026-11-11T01:56:22.000Z: 106 ms2026-11-11T02:01:30.000Z: 98 ms2026-11-11T02:06:38.000Z: 93 ms2026-11-11T02:11:49.000Z: 85 ms2026-11-11T02:16:58.000Z: 130 ms2026-11-11T02:22:08.000Z: 111 ms2026-11-11T02:27:17.000Z: 130 ms2026-11-11T02:32:25.000Z: 83 ms2026-11-11T02:37:34.000Z: 90 ms2026-11-11T02:42:44.000Z: 82 ms2026-11-11T02:47:53.000Z: 99 ms2026-11-11T02:52:58.000Z: 222 ms2026-11-11T02:58:04.000Z: 95 ms2026-11-11T03:03:09.000Z: 84 ms2026-11-11T03:08:13.000Z: 99 ms2026-11-11T03:13:18.000Z: 97 ms2026-11-11T03:18:28.000Z: 170 ms2026-11-11T03:23:38.000Z: 133 ms2026-11-11T03:28:46.000Z: 128 ms2026-11-11T03:33:56.000Z: 180 ms2026-11-11T03:39:07.000Z: 94 ms2026-11-11T03:44:16.000Z: 84 ms2026-11-11T03:49:26.000Z: 114 ms2026-11-11T03:54:35.000Z: 85 ms2026-11-11T03:59:42.000Z: 111 ms2026-11-11T04:04:50.000Z: 87 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Supabase official status · fetched 2026-11-11 04:06:49 UTC

1 mapped components · 0 reporting problems
ComponentProvider status
ap-east-1operational

Official incident timeline

Interruption in connections to Supavisor in eu-west-2 · resolved · 2026-11-08T12:35:48Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    The interruption to Supavisor connections in eu-west-2 has been resolved. Monitoring has confirmed that systems have recovered and connections are operating normally.

  2. · monitoring

    We detected an interruption in connections to Supavisor in eu-west-2 between 09:42 and 09:52 GMT which may have affected connections for some users. This has since been resolved and we are monitoring to ensure all systems have fully recovered.

Increased Errors with Project Lifecycle Operations in US-West-2 · resolved · 2026-11-07T02:17:30Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    The upstream provider incident has been resolved, and Project Lifecycle operations in US-West-2 have recovered. All operations are functioning normally, and we are marking this incident as resolved.

  2. · monitoring

    Our upstream provider has implemented changes, and we are seeing recovery in project creation in US-West-2. We will continue to monitor the recovery of Project Lifecycle operations to ensure stability.

  3. · identified

    We continue to work with our upstream provider as they investigate the ongoing incident affecting US-West-2. There are no additional updates at this time, and Project Lifecycle operations remain impacted. Currently active projects remain unaffected. We will provide another update in 2 hours, or sooner if additional information becomes available.

  4. · identified

    All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.

Intermittent 502/503 errors for pg_net calls to Edge Functions · resolved · 2026-11-05T23:55:13Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

  2. · investigating

    We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.

Storage issues in us-east-1 and eu-central-1 · resolved · 2026-11-05T11:02:26Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    The incident has been resolved.

  2. · monitoring

    The planned database capacity increase for Storage in us-east-1 was completed at 08:06 UTC. Some requests to Storage in us-east-1 may have failed briefly while the database switched over during the change. Storage in us east-1 and eu-central-1 is operating normally. We are continuing to monitor Storage error rates.

  3. · monitoring

    We will be conducting maintenance to address storage service improvements between 0800 and 0900 UTC on 5 November 2026. There may be an interruption of storage services in us-east-1 at some point during that window. The impact will be of a short duration and limited to us-east-1.

  4. · monitoring

    The cause of the issue has been identified as directly related to load. We will be doing maintenance on our platform to address this issue. As of now, storage response has returned to normal. We will continue to monitor the environment.

  5. · investigating

    We are still investigating increased error rates for storage requests, and have expanded the investigation to eu-central-1 as well. The team has identified higher-than-usual load in some areas of the storage infrastructure and is currently working on remediation options.

  6. · investigating

    We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.

Intermittent errors on Supavisor Shared Pooler in us-east-2 · resolved · 2026-11-04T04:17:32Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    Errors have subsided and connections are back to normal.

  2. · monitoring

    Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal" ```

Management API Postgres config updates overwriting previous updates · resolved · 2026-11-03T07:04:25Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    Connection Logging feature is working fine for all customers now.

  2. · monitoring

    A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

  3. · monitoring

    We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.

  4. · investigating

    We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.

  5. · investigating

    We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)

Storage uploads failing in us-east-1 · resolved · 2026-11-02T22:48:45Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    Storage uploads have remained stable, and this issue is now resolved.

  2. · monitoring

    The fix has been implemented, and we are seeing Storage uploads return to normal. We will continue monitoring to ensure stability.

  3. · identified

    We have identified the issue causing Storage uploads to fail and are working on a fix. We will provide more updates as things progress.

  4. · investigating

    We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.

PG15 -> PG17 Upgrade Failures · resolved · 2026-10-31T21:14:16Z

Product match: unmapped.

Read the provider’s incident report

  1. · resolved

    This issue is now resolved.

  2. · monitoring

    We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.

  3. · identified

    We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.

Recovery tracker

No recent recovery can be established from available evidence.

6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 94 ms · Earlier median: 98 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is supabase down right now
  • is supabase down

Query “is supabase” · observed 2026-11-11 03:53:30 UTC · 0 newly observed problem phrases.

Query “supabase” · observed 2026-11-11 03:49:24 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Supabase.

GitHub official status · 2026-11-11 04:06:49 UTC

No active incidents recorded.

Cloudflare official status · 2026-11-11 04:06:49 UTC

About Supabase status on Iszdown

Check Supabase availability, incident history, downtime reports, and website performance.

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.

1 product-matched official components are listed above. Latest public website measurement: 2026-11-11T04:04:50.000Z.

Visit the official Supabase website · Official provider status · How it works

What to check when Supabase is not working

These are troubleshooting suggestions, not a list of currently reported problems.

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.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Supabase outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

IncidentStarted (UTC)Recorded durationLast collected status
Increased Errors with Project Lifecycle Operations in US-West-2148 minresolved
Intermittent 502/503 errors for pg_net calls to Edge Functions42 minresolved
Storage issues in us-east-1 and eu-central-1978 minresolved
Intermittent errors on Supavisor Shared Pooler in us-east-229 minresolved
Storage uploads failing in us-east-174 minresolved
Delayed Log Delivery from 14:10 - 15:30 UTC53 minresolved
Log Drain Issues47 minresolved
Elevated Mgmt API Error Rates in Multiple Regions5355 minresolved

Frequently asked questions about Supabase

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-11-11T04:08:33.000Z.

How many Supabase outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04: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-11-11T04:06: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 to Supabase

Check a related product separately; its status can differ from Supabase.

Supabase