rewindex

ChangesSupabase‘Project not specified’ errors reported for users in ap-northeast-2

Supabase: Incident updated: ‘Project not specified’ errors reported for users in ap-northeast-2

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: Between 04:56 UTC - 06:20 UTC projects in ap-northeast-2 encountered 4xx/5xx http errors retrieving project configuration from our upstream network partner with the error: Project not specified. The issue has since recovered and we are working with our network partner on a full review. We will continue to monitor this issue until confirmed resolved.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayTuesday, November 17Tue, Nov 17

2 incident changes

Cite this

Incident updated: ‘Project not specified’ errors reported for users in ap-northeast-2 on Supabase’s status page, changed 2026-11-17 06:43 UTC (change 1 of 2).

Title
Incident updated: ‘Project not specified’ errors reported for users in ap-northeast-2
Vendor
Supabase
Date
URL
https://rewindex.com/change/r51b994f06882e9

All Supabase changesSupabase profileMarkdownJSON