Supabase: ‘Project not specified’ errors reported for users in ap-northeast-2
Affected components: ap-northeast-2
Timeline of updates
- investigating
We are investigating reports of users receiving ‘Project not specified’ errors in ap-northeast-2.
- monitoring
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.
- resolved
Projects in ap-northeast-2 have recovered and this issue is now resolved.
Changes Rewindex caught on this incident
- Incident updated: ‘Project not specified’ errors reported for users in ap-northeast-2
- Incident updated: ‘Project not specified’ errors reported for users in ap-northeast-2
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.
Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Supabase, started 2026-11-17 06:14 UTC, resolved after 3.2 h, 3 update(s); edited after publishing.
- Title
- ‘Project not specified’ errors reported for users in ap-northeast-2
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M7M28VB7RPQ89T93T9T1SBZ2
Supabase profileRecent Supabase incidentsAll outages on November 17, 2026Supabase in November 2026MarkdownJSON