All Systems Operational
Uptime over the past 90 days. View historical uptime.
Analytics ? Operational
90 days ago
100.0 % uptime
Today
API Gateway ? Operational
90 days ago
99.82 % uptime
Today
Auth ? Operational
90 days ago
99.82 % uptime
Today
Connection Pooler ? Operational
90 days ago
100.0 % uptime
Today
Dashboard ? Operational
90 days ago
100.0 % uptime
Today
Database ? Operational
90 days ago
100.0 % uptime
Today
Edge Functions ? Operational
90 days ago
99.98 % uptime
Today
Management API ? Operational
90 days ago
100.0 % uptime
Today
Realtime ? Operational
90 days ago
100.0 % uptime
Today
Storage ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
Past Incidents
Oct 7, 2024

No incidents reported today.

Oct 6, 2024

No incidents reported.

Oct 5, 2024

No incidents reported.

Oct 4, 2024

No incidents reported.

Oct 3, 2024
Auth limits due to default SMTP server usage unintentionally enforced on Token, Verify, and Admin endpoints
Resolved - This incident has been resolved.
Oct 3, 15:45 UTC
Monitoring - The rollout is complete and we are monitoring.
Oct 3, 12:17 UTC
Update - The fix is being rolled out to all affected instances, we are 50% complete, we estimate that it will be 1h 30 minutes until the rollout is complete.
Oct 3, 11:33 UTC
Identified - We have identified the issue and a fix is being deployed.
Oct 3, 09:59 UTC
Update - We are continuing to investigate this issue.
Oct 3, 08:47 UTC
Investigating - We are currently investigating this issue.
Oct 3, 08:40 UTC
Oct 2, 2024

No incidents reported.

Oct 1, 2024

No incidents reported.

Sep 30, 2024

No incidents reported.

Sep 29, 2024

No incidents reported.

Sep 28, 2024

No incidents reported.

Sep 27, 2024

No incidents reported.

Sep 26, 2024
Edge functions currently disabled for us-east-1 region
Resolved - This incident has been resolved.
Sep 26, 18:16 UTC
Monitoring - We believe the network connectivity issues we were seeing in us-east-1 have been resolved, and the region has been re-enabled.

You may now specify it, and it will also participate in requests without a region specified again.

We'll monitor for any additional errors, but things are looking good now.
Sep 26, 17:06 UTC
Update - We have temporarily disabled edge functions in us-east-1. Requests without a region should reroute to another region automatically; however, if you specify us-east-1 for any of your functions, please choose another region at this time.

We've added capacity to other regions, and global error rates have returned to normal levels.

We are working with AWS on a resolution and hope to re-enable us-east-1 soon.

We will provide additional updates as we have them.
Sep 26, 16:28 UTC
Identified - We have identified network connectivity issues at our hosting provider (AWS) in us-east-1, which is preventing requests from reaching edge functions. We are looking into solutions.

Increased pressure in other regions due to requests being rerouted around us-east-1 are resulting in higher than normal error rates, for which we are currently increasing resources to accommodate the additional traffic.
Sep 26, 15:57 UTC
Investigating - We are currently investigating this issue.
Sep 26, 15:33 UTC
Project lifecycle operations upgrades
Completed - The scheduled maintenance has been completed.
Sep 26, 09:00 UTC
Update - Platform upgrades are still in progress.
Additional time is required to complete this operation. We expect this to complete before 0900 UTC
Sep 26, 07:56 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 26, 07:00 UTC
Scheduled - Project creation, project unpause, read replica creation, and database version upgrades operated through the Dashboard and Management API will be briefly unavailable while we carry out needed upgrades.
The interruption is expected to last less than one hour.

The HTTP APIs and Postgres endpoints for existing projects will NOT be affected, and will continue serving traffic normally.
Sep 25, 10:45 UTC
Sep 25, 2024
Read Replica Load Balancers incorrectly attempting to route to deleted replicas
Resolved - This incident has been resolved.
Sep 25, 03:17 UTC
Monitoring - A fix has been rolled out, and the configuration for affected projects has been fixed as well.

It was also determined that the bug was introduced at ~0755 on the 24th of September, and three projects in total were impacted by the edge condition that was determined to be buggy.
Sep 25, 03:12 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 25, 02:16 UTC
Investigating - We are currently investigating this issue.
Sep 25, 02:15 UTC
Sep 24, 2024

No incidents reported.

Sep 23, 2024
Projects using the default email provider experiencing errors sending emails
Resolved - This incident has been resolved.
Sep 23, 21:09 UTC
Monitoring - The fix has been applied to all existing projects as well. At this time, things are looking back to normal, but we will continue monitoring for further issues.
Sep 23, 20:08 UTC
Update - The change for the default email provider is still rolling out to existing projects, and is about 60% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp
Sep 23, 19:32 UTC
Update - The change for the default email provider is still rolling out to existing projects, and is about 32% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp
Sep 23, 18:17 UTC
Update - The change for the default email provider is still rolling out to existing projects, and is about 15% done. We'll continue to update here as things progress.

We still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp
Sep 23, 17:15 UTC
Update - We've made the swap to our new upstream provider for all newly created projects. We're working pushing the change out to all existing projects.

However, we still suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp
Sep 23, 16:04 UTC
Identified - We have identified an issue with our upstream email provider, and are working to move this to a different service.

In the meantime, we would always suggest using your own SMTP provider for production workloads. For instructions on setting up your own SMTP provider, see here: https://supabase.com/docs/guides/auth/auth-smtp
Sep 23, 14:59 UTC
Investigating - We are currently investigating this issue.
Sep 23, 14:44 UTC
← Incident History Powered by Atlassian Statuspage