Supabase · Degraded
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Supabase status

Supabase · Atlassian Statuspage
Degraded
Atlassian Statuspage reports Partially Degraded Service.
Platform services
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

401 errors due to JWT rejections

Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.

Status identified Impact degraded Updated

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
27
Retained
27
Affected retained
1
Projection scope: complete · 27 retained of 27 reported components across 1 source group.
Analytics Operational
ap-northeast-1 Group: Compute capacity Operational
API Gateway Degraded
ap-northeast-2 Group: Compute capacity Operational
Auth Operational
ap-south-1 Group: Compute capacity Operational
Connection Pooler Operational
ap-southeast-1 Group: Compute capacity Operational
Dashboard Operational
ap-southeast-2 Group: Compute capacity Operational
Database Operational
ca-central-1 Group: Compute capacity Operational
Edge Functions Operational
eu-central-1 Group: Compute capacity Operational
Management API Operational
eu-central-2 Group: Compute capacity Operational
Realtime Operational
eu-north-1 Group: Compute capacity Operational
Storage Operational
eu-west-1 Group: Compute capacity Operational
Showing 20 of 27 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Degraded
HTTP 200 · 379.93 ms feed latency
Degraded
HTTP 200 · 239.65 ms feed latency
Degraded
HTTP 200 · 346.26 ms feed latency
Degraded
HTTP 200 · 331.77 ms feed latency
Degraded
HTTP 200 · 272.09 ms feed latency
Degraded
HTTP 200 · 442.11 ms feed latency
Degraded
HTTP 200 · 373.09 ms feed latency
Degraded
HTTP 200 · 417.89 ms feed latency
Degraded
HTTP 200 · 254.73 ms feed latency
Degraded
HTTP 200 · 380.45 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
311.09 ms