‘Project not specified’ errors reported for users in ap-northeast-2
Nov 17, 06:14 UTCNov 17, 09:26 UTC
Duration
3h 12m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
58 incidents
Affected
Not listed by the vendor.
Final update
Projects in ap-northeast-2 have recovered and this issue is now resolved.
Timeline
- Resolved · Nov 17, 09:26 UTC
Projects in ap-northeast-2 have recovered and this issue is now resolved.
- Monitoring · Nov 17, 06:33 UTC
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.
- Investigating · Nov 17, 06:14 UTC
We are investigating reports of users receiving ‘Project not specified’ errors in ap-northeast-2.
More from Supabase
Full historyGateway availability disruptionlasted 0mEdge Function Issues in ap-northeast-1lasted 3h 7mProjects in sa-east-1 experiencing delayed event ingestionlasted 8h 44mElevated Error rates for All Supabase project APIslasted 1h 18mDatabase Connection Errorslasted 3h 4mStorage request degradation in eu-west-1lasted 8m