Databases / Postgres platform / Supabase

Supabase

SEV 2 · BLEEDING · 1h 40m

Since Sep 2026 · 26 incidents · status.supabase.com · checked just now

CompareStatus page
GradeFLast 90 days
FPRODBSHIP
Happening now
Oct 22, 2026ongoingSEV 2
API Gateway Request IssuesSupabase reported issues with requests reaching its API gateway, caused by a demand spike on its backplane. Mitigations to scale and manage demand were deployed and the spike was reportedly managed, but the incident remains in monitoring while further reinforcement is rolled out. No resolution time or affected share was given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Requests to the Supabase API gateway had issues from a backplane demand spike; the text does not give the share of customers affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 17:01 UTC · investigating
    We have noticed issues with requests coming to our API gateway. We are investigating.
  2. 17:28 UTC · identified
    We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
  3. 17:57 UTC · monitoring
    The mitigations have managed the demand spike. We are monitoring for continued stability.
  4. 18:17 UTC · monitoring
    We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
Source

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade F
IncidentsEverything posted on the status page except scheduled maintenance.
260 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
2h 02m
LongestLongest single incident, start to resolved.
6d 19h
Since lastTime since the last counted incident was resolved.
ongoing

By area

FProduction
9INCIDENTS
9d 12hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Sep 29, 2026 · 6d 19hIntermittent latency in Eastern US
SEV 2Oct 12, 2026 · 45h 26mRealtime latency
SEV 2Oct 12, 2026 · 22h 36mEdge Function Degradation
Worse. 9 in the last 6 months, 0 in the 6 before.
BShipping
17INCIDENTS
3d 0hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Sep 23, 2026 · 24h 30mStorage search failing for restored projects
SEV 3Oct 12, 2026 · 22h 36mEdge Function Degradation
SEV 3Oct 22, 2026 · 12h 03mProject lifecycle operation errors in the EU region
Worse. 17 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production database, per month10 GB of data, about 1 GB of RAM on all month, 10M queries a month, one region, no replicas, commercial use. Cheapest plan that runs it.
Pro, Micro compute2 of 4 cheaper · Upstash: cheaper, better grade
$25.25/mo
Pro plan$25
Micro compute (1 GB RAM)$10
Included compute credit−$10
2 GB disk over the 8 GB included, at $0.125/GB$0.25

supabase.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 26 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down10
Sev 3 · Can't shipCan't deploy, build or manage it13
Sev 4 · PapercutDocs, status page, slow dashboard3
1 security incident

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
4.4Last 12 months
Update gapMedian time between status page updates during an incident.
47mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 10Sev 1–2

Incident history

Show all 26
Oct 22, 2026ongoingSEV 4
Log Drain IssuesLog drains missed some routed logs for a subset of components in some regions; rolled back and restored within about 20 minutes.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Log drains missed some routed logs for a subset of components in some regions; rolled back and restored within about 20 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 18:03 UTC · investigating
    Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
  2. 18:22 UTC · monitoring
    The rollback has restored log drains to normal operation. We will monitor for continued functionality.
Source
Oct 22, 2026ongoingSEV 2
API Gateway Request IssuesSupabase reported issues with requests reaching its API gateway, caused by a demand spike on its backplane. Mitigations to scale and manage demand were deployed and the spike was reportedly managed, but the incident remains in monitoring while further reinforcement is rolled out. No resolution time or affected share was given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Requests to the Supabase API gateway had issues from a backplane demand spike; the text does not give the share of customers affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 17:01 UTC · investigating
    We have noticed issues with requests coming to our API gateway. We are investigating.
  2. 17:28 UTC · identified
    We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
  3. 17:57 UTC · monitoring
    The mitigations have managed the demand spike. We are monitoring for continued stability.
  4. 18:17 UTC · monitoring
    We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
Source
Oct 22, 20262h 13mSEV 3
Elevated Mgmt API Error Rates in Multiple RegionsThe Management API had elevated error rates and latency across multiple regions for about two hours, so project creation and other operations could fail or be slow. Logins to supabase.com also timed out. A mitigation restored normal error rates and latency, and the incident was resolved after monitoring. The provider gave no detailed cause.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Management API errors and slow responses across multiple regions for about two hours, blocking project creation and dashboard logins.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 11:29 UTC · investigating
    We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
  2. 11:32 UTC · investigating
    We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow. This is also causing logins to supabase.com to timeout.
  3. 12:07 UTC · monitoring
    A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.
  4. 13:42 UTC · resolved
    Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
Source
Oct 22, 202612h 03mSEV 3
Project lifecycle operation errors in the EU regionProject lifecycle operations (create, restore, pause) in the EU region had elevated error rates from 21 Oct 23:00 UTC. A mitigation brought error rates back to normal, and the incident was resolved after about 12 hours. The provider said it was working on fixing affected projects, and no data loss was reported.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Project create, restore and pause operations failed at elevated rates in the EU region for about 12 hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 03:53 UTC · monitoring
    We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.
  2. 09:15 UTC · monitoring
    Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.
  3. 15:56 UTC · resolved
    Error rates have remained at normal levels following the mitigation. This incident is now resolved.
Source
Oct 21, 20260mSEV 2
Intermittent connection errors via the connection pooler in us-east-1On October 9, 2026, about 1% of new connections through the Shared Pooler in us-east-1 failed with timeouts from 22:10 to 22:51 UTC. Cause was a cloud provider network incident between availability zones. Existing connections stayed open; retries succeeded.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    About 1% of new pooled connections in us-east-1 failed for roughly 41 minutes; existing connections and direct database access were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 02:10 UTC · resolved
    Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.
Source
Oct 21, 20261h 16mSEV 3
Project lifecycle operations such as project creation, pausing, and restoration, in all regionsProject lifecycle operations, including project creation, pausing, and restoration, failed in all regions from 15:36 to 16:51 UTC on 21 October. A fix was applied and lifecycle job failures dropped. Running projects were not described as affected.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Project creation, pausing and restoration failed in all regions for about 75 minutes; running databases were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 15:36 UTC · investigating
    We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.
  2. 16:12 UTC · monitoring
    A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.
  3. 16:51 UTC · resolved
    The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.
Source
Oct 20, 20267h 41mSEV 2
Projects stuck in restarting stateSome Supabase projects in us-east-2 got stuck in a restarting state from about 22:00 UTC on October 20 until the fix finished rolling out around 05:40 UTC on October 21. The provider identified the root cause and rolled out a fix to affected projects; the text does not describe the cause in detail.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some database projects in us-east-2 were stuck restarting for several hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
8 updates
  1. 21:59 UTC · investigating
    Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.
  2. 23:06 UTC · identified
    We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.
  3. 23:48 UTC · identified
    We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.
  4. 00:39 UTC · identified
    We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
  5. 01:38 UTC · identified
    We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
  6. 02:48 UTC · identified
    We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.
  7. 04:47 UTC · monitoring
    The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
  8. 05:39 UTC · resolved
    All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
Source
Oct 19, 20261h 00mSEV 4
Support Form ErrorsSev 4 from the incident title (no components listed)
3 updates
  1. 17:13 UTC · identified
    We have identified an issue with support ticket creation for some customers, we have a fix in development.
  2. 17:36 UTC · monitoring
    The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.
  3. 18:13 UTC · resolved
    Ticket creation has remained normal. We re resolving this incident.
Source
Oct 17, 20261h 22mSEV 3
Project creation errors ap-ne1Sev 3 from the incident title (no components listed)
3 updates
  1. 06:27 UTC · identified
    Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.
  2. 07:16 UTC · monitoring
    Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.
  3. 07:49 UTC · resolved
    Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.
Source
Oct 12, 202645h 26mSEV 2
Realtime latencySupabase Realtime had high latency and instability, mainly affecting the presence feature and possibly join rates, from October 12 to October 14. Capacity was added to the affected clusters and stabilised users were reported on October 14. The incident was marked resolved on October 14 at 20:25 UTC.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Realtime latency and instability hit the presence feature for about a day and a half; a large share of affected customers recovered, with some regions lagging.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
9 updates
  1. 22:59 UTC · investigating
    We are experiencing increased latency with Realtime and are actively investigating.
  2. 00:02 UTC · monitoring
    We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
  3. 06:38 UTC · monitoring
    We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
  4. 13:49 UTC · identified
    We’re seeing increased Realtime latency and instability affecting the presence feature, which may impact join rates. This recurrence comes as we continue work on the remaining preventative measures. We are actively investigating and taking steps to mitigate the impact. We’ll share another update as soon as we have more information.
  5. 17:34 UTC · identified
    We are continuing to investigate increased Realtime latency and instability affecting the presence feature, which may impact join rates. Our team is actively working on mitigation and we will share another update as soon as more information becomes available.
  6. 21:15 UTC · identified
    We’ve added extra capacity to the system and are currently testing it. We expect to begin stabilizing the affected clusters shortly. We’ll continue to share further updates as more information becomes available.
  7. 23:27 UTC · identified
    We’re seeing recovery for a large percentage of affected customers, though some issues remain in certain regions. We’re continuing to work on resolving the remaining issues and will share further updates as more information becomes available.
  8. 03:00 UTC · monitoring
    We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
  9. 20:25 UTC · resolved
    Realtime has fully recovered.
Source
Oct 12, 202622h 36mSEV 2
Edge Function DegradationEdge Functions saw significant degraded performance starting October 12, mainly affecting deploys and retrieving function bodies, with elevated error rates. Deployments returned to normal by October 12 evening and the incident closed October 13. Worker jobs that failed during the incident, including possibly affected backups, were to be re-queued, with no data loss confirmed.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Edge Function deploys and function body retrieval were significantly degraded for about a day; the scope across regions is not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 19:49 UTC · identified
    We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
  2. 20:23 UTC · identified
    We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
  3. 21:07 UTC · identified
    Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
  4. 02:24 UTC · monitoring
    Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
  5. 18:24 UTC · resolved
    Edge function deployments have remained stable. We are closing the incident.
Source
Oct 12, 20265h 51mSEV 4
Log ingestion impairedSupabase log ingestion was impaired from about 19:40 to 01:30 UTC on October 12-13, 2026. Logs were delayed or unavailable during this time. The provider said the fix was implemented and ingestion returned to normal. Affected components and scope were not specified.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Log ingestion was impaired for about six hours, with logs delayed or unavailable; the provider did not say how widely.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 19:39 UTC · investigating
    Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.
  2. 20:09 UTC · identified
    We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.
  3. 20:56 UTC · identified
    We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.
  4. 22:17 UTC · identified
    We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.
  5. 00:05 UTC · identified
    We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.
  6. 00:35 UTC · monitoring
    The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.
  7. 01:30 UTC · resolved
    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.
Source
Oct 6, 20262h 56mSEV 3
Upgrade IssuesUpgrades to PostgreSQL 17.11.0.003 kept failing, so Supabase suspended upgrades for affected projects from 15:23 to 18:18 UTC. The problem was limited to upgrades from earlier PG17 versions. A fix was implemented and upgrades were re-enabled in the dashboard.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Project upgrades to 17.11.0.003 failed and were suspended for about three hours; running databases were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 15:23 UTC · investigating
    We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
  2. 16:03 UTC · identified
    We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
  3. 16:37 UTC · identified
    A fix has been developed and we are going through the review and implementation process.
  4. 17:27 UTC · monitoring
    The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
  5. 18:18 UTC · resolved
    We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
Source
Oct 6, 20261h 10mSEV 2 · SECURITY
Increased errors on management api leading to project operation failuresSev 3 from the incident title (no components listed), raised to Sev 2 for security
4 updates
  1. 07:53 UTC · investigating
    We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
  2. 07:55 UTC · investigating
    We are continuing to investigate this issue.
  3. 08:13 UTC · monitoring
    We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
  4. 09:03 UTC · resolved
    This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.
Source
Sep 29, 20266d 19hSEV 2
Intermittent latency in Eastern USClients in the eastern US saw intermittent high latency connecting to Supabase projects, worst during EDT business-hour spikes, regardless of project region. Caused by a problematic network PoP; networking partners applied mitigations and a fix was implemented October 5, resolved October 6.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Elevated latency for clients in the eastern US connecting to Supabase projects, mainly during peak hours, lasting about a week.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
10 updates
  1. 16:26 UTC · identified
    We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.
  2. 17:55 UTC · identified
    We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
  3. 21:35 UTC · identified
    A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
  4. 02:14 UTC · identified
    We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available.
  5. 14:54 UTC · identified
    We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.
  6. 21:26 UTC · identified
    We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available.
  7. 20:23 UTC · identified
    Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.
  8. 21:06 UTC · identified
    While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.
  9. 18:45 UTC · monitoring
    A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
  10. 12:15 UTC · resolved
    A fix for this issue has been implemented and our data shows previous impacted users have recovered.
Source
Sep 28, 202649mSEV 3
Log Ingestion DegradationSev 3 from the incident title (no components listed)
4 updates
  1. 13:47 UTC · investigating
    Log ingestion is experiencing some delays. Ingestion will be retried by clients.
  2. 13:52 UTC · identified
    The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
  3. 14:00 UTC · monitoring
    Log ingestion has recovered. We are monitoring for continued stability.
  4. 14:36 UTC · resolved
    Log ingestion is normal.
Source
Sep 24, 20262h 02mSEV 3
Project Lifecycle Issues in eu-west-1Sev 3 from the incident title (no components listed)
7 updates
  1. 15:36 UTC · investigating
    We are investigating project lifecycle operation issues in eu-west-1.
  2. 15:50 UTC · identified
    We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
  3. 16:23 UTC · identified
    All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
  4. 16:56 UTC · identified
    Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
  5. 17:03 UTC · identified
    The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
  6. 17:12 UTC · monitoring
    We are continuing to monitor to ensure ongoing stability.
  7. 17:38 UTC · resolved
    This incident has been resolved.
Source
Sep 24, 202636mSEV 3
Permission errors in the Supabase DashboardSev 3 from the incident title (no components listed)
4 updates
  1. 10:37 UTC · investigating
    We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. This may prevent some users from managing their projects through the Dashboard. We are working to identify the cause and will provide further updates as they become available.
  2. 10:50 UTC · identified
    We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. We are working on a fix and will provide another update once it has been implemented.
  3. 11:08 UTC · monitoring
    We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected. We are monitoring the results to ensure the issue is fully resolved.
  4. 11:49 UTC · resolved
    This incident has been resolved. Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.
Source
Sep 23, 20261h 42mSEV 3
Supabase CLI CI workflow failuresSev 3 from the incident title (no components listed)
4 updates
  1. 21:58 UTC · investigating
    We're seeing rate limiting issues causing Supabase CLI CI workflow failures
  2. 22:36 UTC · identified
    We've identified the cause and are working on a fix.
  3. 22:56 UTC · monitoring
    We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.
  4. 23:41 UTC · resolved
    This incident has been resolved.
Source
Sep 23, 202640mSEV 3
Increased error rate in project creation and project restoreSev 3 from the incident title (no components listed)
4 updates
  1. 09:21 UTC · investigating
    We are currently investigating this issue
  2. 09:39 UTC · identified
    We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.
  3. 09:54 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 10:49 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
UpstashGrade A+100.00% up4 incidentsMTTR 0m~$22.25/moPlanetScaleGrade A99.99% up5 incidentsMTTR 26m$10/moCockroachDB CloudGrade B100.00% up5 incidentsMTTR 7h 00m–/moMongoDB AtlasGrade C100.00% up18 incidentsMTTR 2h 35m$56.94/moSupabaseGrade F100.00% up26 incidentsMTTR 2h 02m$25.25/mo

README badge

Supabase's live grade, for your README.

Supabase grade badge
[![supabase on downagain.dev](https://downagain.dev/badge/supabase.svg)](https://downagain.dev/p/supabase)