Skip to content
PulseWatchOUTAGE.INTEL
Supabase logo

Cloud Infrastructure

Is Supabase down right now?

UnknownOfficial status last polled Oct 6, 2026 02:45 UTCsupabase.comOfficial status page

Open-source Firebase alternative — Postgres backend

Are you on the Supabase team and see something inaccurate? Report it to us. We respond within one business day.

Is Supabase down right now?

Vendor-reported issue. Supabase: Supabase: Intermittent latency in Eastern US Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Oct 6, 2026 02:48 UTC

UnknownVendor-reported issue

Supabase: vendor reports an issue

As of Oct 6, 2026 02:48 UTC

Supabase: Intermittent latency in Eastern US Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

Oct 2, 2026 17:45 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Supabase.

20

Incident days

10

No recorded incident

471h 1m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Supabase. Hover a day for detail.

Sep 7Sep 12Sep 17Sep 22Sep 27Oct 201234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

20

Days with incidents

2 incidents

Busiest day

471h 1m

Recorded duration

Report volume

0 reports in last 24H

02:45 AM06:15 AM09:45 AM01:15 PM04:45 PM08:15 PM11:45 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Supabase: vendor-reported minor incident on October 1 (tracked 1d 15h)

Oct 1, 02:35 AM → Oct 2, 05:45 PM · 1d 15h · medium

Supabase reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1 day and 15 hours, closing it on 2026-10-02T17:45:41.357Z.

Duration
1d 15h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The incident is known from Supabase's own status page.

Incident timeline

  1. Oct 1, 02:35 AM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 02:35 AM

    Status updated: possible issue

  3. Oct 2, 05:45 PM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 02:35 AM

    Supabase reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Supabase is unknown, so there is no incident history to measure and no uptime figure is shown.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 2:35:43 AM · 1d 15h

02:35 AM05:45 PM
Detection10/1/2026, 2:35:43 AM · 5d ago

Detected — medium severity

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/22/2026, 5:06:05 PM · 8d 9h

05:06 PM02:26 AM
Detection9/22/2026, 5:06:05 PM · 13d ago

Detected — medium severity

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/13/2026, 2:31:24 AM · 9d 14h

02:31 AM05:00 PM
Detection9/13/2026, 2:31:24 AM · 23d ago

Detected — medium severity

Supabase: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Supabase incident correlated across 1 signal group: official/vendor.

9/4/2026, 12:37:40 AM · 7h 44m

12:37 AM08:21 AM
Detection9/4/2026, 12:37:40 AM · 1mo ago

Detected — medium severity

Supabase incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Supabase incident correlated across 1 signal group: official/vendor.

9/3/2026, 6:37:00 AM · 2h 1m

06:37 AM08:38 AM
Detection9/3/2026, 6:37:00 AM · 1mo ago

Detected — medium severity

Supabase incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Supabase enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
Vendor-reported issue: Supabase: Intermittent latency in Eastern US. Affected scope is described in the vendor notice; service-wide impact is not established.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
4
Open threshold
3x

Official site

supabase.com