Supabase Outage History

Supabase is up right now

Supabase had 77 outages in the last 2 years totaling 1071h 31m of downtime — averaging 3.2 incidents per month.

There were 77 Supabase outages since December 24, 2025 totaling 1071h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.supabase.com

Minor June 17, 2026

Hardware failure in us-east

Detected by Pingoru
Jun 17, 2026, 03:12 PM UTC
Resolved
Jun 17, 2026, 05:02 PM UTC
Duration
1h 50m
Affected: us-east-2
Timeline · 4 updates
  1. investigating Jun 17, 2026, 03:12 PM UTC

    Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.

  2. identified Jun 17, 2026, 03:44 PM UTC

    We have identified projects specifically impacted by this issue and are recovering affected projects.

  3. monitoring Jun 17, 2026, 04:13 PM UTC

    All the identified affected projects in us-east-2 are now healthy. If your project is in us-east and not responsive, please open a ticket to let us know.

  4. resolved Jun 17, 2026, 05:02 PM UTC

    We have now recovered all Projects affected by the outage in us-east-2.

Read the full incident report →

Major June 17, 2026

Degraded Management API performance affecting payments and Supabase Studio

Detected by Pingoru
Jun 17, 2026, 12:31 PM UTC
Resolved
Jun 17, 2026, 02:10 PM UTC
Duration
1h 38m
Affected: API GatewayDashboardca-central-1Management APIsa-east-1us-east-1us-east-2
Timeline · 4 updates
  1. investigating Jun 17, 2026, 12:31 PM UTC

    We are currently investigating the issue

  2. investigating Jun 17, 2026, 12:51 PM UTC

    We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2. Customers may experience failed payments, failed project creations, and degraded performance in Supabase Studio. As a precautionary measure, we have temporarily disabled the following features while we investigate: - Top up Credits - Update Billing Information - Redeem Credits To reduce impact, we have redirected traffic to healthy regions. Our team continues to actively investigate and work toward a full resolution.

  3. monitoring Jun 17, 2026, 01:15 PM UTC

    We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. All payment features have been re-enabled. Customers should no longer experience failed payments or failed project creations. We are continuing to monitor the system closely and will provide a final update once we have confirmed full stability.

  4. resolved Jun 17, 2026, 02:10 PM UTC

    All regions continue to report healthy Management API performance and platform stability.

Read the full incident report →

Minor June 16, 2026

Project usage analytics API endpoints breakage

Detected by Pingoru
Jun 16, 2026, 03:47 PM UTC
Resolved
Jun 16, 2026, 05:01 PM UTC
Duration
1h 14m
Affected: Analytics
Timeline · 5 updates
  1. investigating Jun 16, 2026, 03:47 PM UTC

    We are investigating a breakage in project usage analytics data propagation.

  2. investigating Jun 16, 2026, 04:18 PM UTC

    We are investigating the components involved in analytics endpoints updates to isolate any changes that could have caused this problem. The issue is limited to the usage.api-requests-count endpoint.

  3. identified Jun 16, 2026, 04:22 PM UTC

    The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.

  4. monitoring Jun 16, 2026, 04:27 PM UTC

    The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.

  5. resolved Jun 16, 2026, 05:01 PM UTC

    All analytics responses have returned to normal.

Read the full incident report →

Minor June 16, 2026

Degraded Log Explorer in the dashboard

Detected by Pingoru
Jun 16, 2026, 11:26 AM UTC
Resolved
Jun 16, 2026, 03:08 PM UTC
Duration
3h 42m
Affected: Analytics
Timeline · 4 updates
  1. monitoring Jun 16, 2026, 11:26 AM UTC

    Some users are seeing errors or degraded performance on usage reportss and logs in the Supabase dashboard. The team has already rolled out mitigations and are seeing improvements. We are continuing to monitor the results.

  2. identified Jun 16, 2026, 01:01 PM UTC

    The mitigations rolled out have resulted in a great reduction in errors and most users should now see fully-functional logging and usage charts; however, some users may still see erroneously empty usage charts on the project home page. The team is continuing to work on this issue.

  3. monitoring Jun 16, 2026, 01:30 PM UTC

    We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.

  4. resolved Jun 16, 2026, 03:08 PM UTC

    We have rolled out additional performance improvements to reporting API endpoints.

Read the full incident report →

Minor June 12, 2026

Storage users in US-West-2 experiencing increased latency on storage requests

Detected by Pingoru
Jun 12, 2026, 04:00 PM UTC
Resolved
Jun 13, 2026, 12:40 AM UTC
Duration
8h 39m
Affected: Storage
Timeline · 8 updates
  1. identified Jun 12, 2026, 04:00 PM UTC

    Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.

  2. identified Jun 12, 2026, 04:30 PM UTC

    We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.

  3. identified Jun 12, 2026, 05:29 PM UTC

    The team is still working on a solution, and mitigation work is underway.

  4. identified Jun 12, 2026, 06:28 PM UTC

    We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.

  5. identified Jun 12, 2026, 07:30 PM UTC

    We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region.

  6. monitoring Jun 12, 2026, 08:26 PM UTC

    Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.

  7. monitoring Jun 12, 2026, 11:57 PM UTC

    Job queues continue to drain. We will actively monitor until they are complete.

  8. resolved Jun 13, 2026, 12:40 AM UTC

    All residual jobs have drained. Storage performance and job activity is normal.

Read the full incident report →

Notice June 10, 2026

Higher connection failure rate for ap-northeast-1 and ap-northeast-2

Detected by Pingoru
Jun 10, 2026, 12:00 AM UTC
Resolved
Jun 10, 2026, 12:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 10, 2026, 01:43 AM UTC

    From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.

Read the full incident report →

Notice June 8, 2026

DNS Resolution Failures for TLD .co users

Detected by Pingoru
Jun 08, 2026, 03:39 AM UTC
Resolved
Jun 16, 2026, 08:16 AM UTC
Duration
8d 4h
Timeline · 8 updates
  1. identified Jun 08, 2026, 03:39 AM UTC

    We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .co TLD resolution impacting multiple DNS providers. Customers may be able to bypass this issue by using a VPN while we work towards resolution. We will update the statuspage when we have more information to share.

  2. monitoring Jun 08, 2026, 06:37 AM UTC

    The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.

  3. monitoring Jun 08, 2026, 12:38 PM UTC

    Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner.

  4. monitoring Jun 08, 2026, 05:32 PM UTC

    We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name.

  5. monitoring Jun 10, 2026, 11:24 PM UTC

    Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing.

  6. monitoring Jun 12, 2026, 11:09 AM UTC

    Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information becomes available.

  7. monitoring Jun 15, 2026, 04:52 PM UTC

    The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.

  8. resolved Jun 16, 2026, 08:16 AM UTC

    The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.

Read the full incident report →

Critical June 2, 2026

Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)

Detected by Pingoru
Jun 02, 2026, 01:36 PM UTC
Resolved
Jun 02, 2026, 02:41 PM UTC
Duration
1h 5m
Affected: Management API
Timeline · 4 updates
  1. investigating Jun 02, 2026, 01:36 PM UTC

    We are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.

  2. identified Jun 02, 2026, 02:05 PM UTC

    We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.

  3. monitoring Jun 02, 2026, 02:12 PM UTC

    The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.

  4. resolved Jun 02, 2026, 02:41 PM UTC

    All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.

Read the full incident report →

Minor May 21, 2026

Branch creation degradation

Detected by Pingoru
May 21, 2026, 04:46 PM UTC
Resolved
May 21, 2026, 07:26 PM UTC
Duration
2h 39m
Timeline · 4 updates
  1. investigating May 21, 2026, 04:46 PM UTC

    We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.

  2. investigating May 21, 2026, 05:45 PM UTC

    We continue investigating different possible underlying causes and will provide updates as progress is made.

  3. monitoring May 21, 2026, 06:54 PM UTC

    Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.

  4. resolved May 21, 2026, 07:26 PM UTC

    Branch creation continues to be stable.

Read the full incident report →

Minor May 21, 2026

Login issues for SSO and Email accounts on Supabase Dashboard

Detected by Pingoru
May 21, 2026, 08:30 AM UTC
Resolved
May 21, 2026, 10:51 AM UTC
Duration
2h 20m
Affected: Dashboard
Timeline · 6 updates
  1. investigating May 21, 2026, 08:30 AM UTC

    Users that are already logged in are not affected.

  2. investigating May 21, 2026, 08:33 AM UTC

    We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available.

  3. identified May 21, 2026, 08:49 AM UTC

    We have identified the issue as being related to a recent key rotation and are currently working on a fix.

  4. identified May 21, 2026, 09:26 AM UTC

    A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.

  5. monitoring May 21, 2026, 09:43 AM UTC

    We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.

  6. resolved May 21, 2026, 10:51 AM UTC

    The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.

Read the full incident report →

Minor May 20, 2026

Network restrictions preventing read replica communication

Detected by Pingoru
May 20, 2026, 09:04 PM UTC
Resolved
May 21, 2026, 04:44 AM UTC
Duration
7h 40m
Affected: Database
Timeline · 8 updates
  1. investigating May 20, 2026, 09:04 PM UTC

    Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.

  2. investigating May 20, 2026, 09:46 PM UTC

    We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted.

  3. identified May 20, 2026, 10:48 PM UTC

    We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects.

  4. identified May 20, 2026, 11:41 PM UTC

    Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made.

  5. identified May 21, 2026, 01:12 AM UTC

    Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.

  6. identified May 21, 2026, 03:49 AM UTC

    We have developed a fix and it is currently being validated. We will provide more updates soon.

  7. monitoring May 21, 2026, 04:23 AM UTC

    We have merged the fix and are monitoring for stability.

  8. resolved May 21, 2026, 04:44 AM UTC

    Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.

Read the full incident report →

Minor May 20, 2026

Paused Projects Showing Incorrect Resume Deadline

Detected by Pingoru
May 20, 2026, 03:40 PM UTC
Resolved
May 20, 2026, 07:41 PM UTC
Duration
4h
Affected: Dashboard
Timeline · 5 updates
  1. investigating May 20, 2026, 03:40 PM UTC

    We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard. The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date. For example: “All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still be available for download.” Please note this is a display issue only. Projects paused within the last 90 days can still be resumed successfully. All project data, including backups and storage objects, remains safe and unaffected.

  2. identified May 20, 2026, 04:17 PM UTC

    We’ve isolated the cause of the issue to a recent change and are working on reverting it now.

  3. identified May 20, 2026, 05:41 PM UTC

    The revert of the change is in process.

  4. monitoring May 20, 2026, 07:11 PM UTC

    This change has been reverted. We are monitoring to ensure things remain stable.

  5. resolved May 20, 2026, 07:41 PM UTC

    The UI message incident has been resolved.

Read the full incident report →

Minor May 19, 2026

Error spikes in one of the eu-central-1 Supavisor clusters

Detected by Pingoru
May 19, 2026, 10:31 AM UTC
Resolved
May 09, 2026, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 19, 2026, 10:31 AM UTC

    Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode

Read the full incident report →

Minor May 18, 2026

Log ingestion issues

Detected by Pingoru
May 18, 2026, 11:26 PM UTC
Resolved
May 19, 2026, 12:10 AM UTC
Duration
43m
Affected: Analytics
Timeline · 3 updates
  1. investigating May 18, 2026, 11:26 PM UTC

    Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

  2. monitoring May 18, 2026, 11:58 PM UTC

    Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period. We will continue monitoring closely to ensure ongoing stability.

  3. resolved May 19, 2026, 12:10 AM UTC

    This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.

Read the full incident report →

Notice May 15, 2026

Auth Service Update

Detected by Pingoru
May 15, 2026, 06:11 PM UTC
Resolved
May 15, 2026, 07:18 PM UTC
Duration
1h 7m
Affected: Auth
Timeline · 3 updates
  1. identified May 15, 2026, 06:11 PM UTC

    We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.

  2. monitoring May 15, 2026, 06:47 PM UTC

    The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.

  3. resolved May 15, 2026, 07:18 PM UTC

    All changes hav been applied.

Read the full incident report →

Minor May 13, 2026

Edge Traffic Issues

Detected by Pingoru
May 13, 2026, 04:15 PM UTC
Resolved
May 13, 2026, 08:35 PM UTC
Duration
4h 19m
Affected: Edge Functions
Timeline · 5 updates
  1. investigating May 13, 2026, 04:15 PM UTC

    We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.

  2. investigating May 13, 2026, 04:46 PM UTC

    We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more.

  3. investigating May 13, 2026, 05:31 PM UTC

    We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses.

  4. identified May 13, 2026, 07:50 PM UTC

    Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side.

  5. resolved May 13, 2026, 08:35 PM UTC

    We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved

Read the full incident report →

Minor May 8, 2026

Customer Projects Experiencing Upgrade Issues

Detected by Pingoru
May 08, 2026, 01:25 PM UTC
Resolved
May 08, 2026, 04:13 PM UTC
Duration
2h 48m
Timeline · 5 updates
  1. identified May 08, 2026, 01:25 PM UTC

    Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version. We advise that you do not upgrade your project until the incident is resolved.

  2. identified May 08, 2026, 01:26 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified May 08, 2026, 01:46 PM UTC

    We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process. As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully resolved. We will continue to provide updates as information becomes available.

  4. monitoring May 08, 2026, 02:39 PM UTC

    We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention. Any future upgrades should complete successfully. We are continuing to monitor recovery and system stability closely.

  5. resolved May 08, 2026, 04:13 PM UTC

    Upgrade operations have returned to normal.

Read the full incident report →

Minor May 4, 2026

Supavisor connectivity in eu-central-1

Detected by Pingoru
May 04, 2026, 04:58 PM UTC
Resolved
May 03, 2026, 10:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 04, 2026, 04:58 PM UTC

    From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query failed errors. This has been resolved and Supavisor is fully available.

Read the full incident report →

Major April 28, 2026

403 errors for PostgREST requests

Detected by Pingoru
Apr 28, 2026, 09:26 PM UTC
Resolved
Apr 28, 2026, 11:31 PM UTC
Duration
2h 4m
Affected: API Gateway
Timeline · 6 updates
  1. investigating Apr 28, 2026, 09:26 PM UTC

    We are investigating 403 errors for PostgREST requests across multiple regions.

  2. identified Apr 28, 2026, 09:36 PM UTC

    The issue has been identified and we are working on a fix.

  3. identified Apr 28, 2026, 09:40 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Apr 28, 2026, 10:24 PM UTC

    We are continuing to work on a fix. We’ll share further updates as progress is made.

  5. monitoring Apr 28, 2026, 11:03 PM UTC

    The exceptions fix has been rolled out, and we are monitoring for continued stability.

  6. resolved Apr 28, 2026, 11:31 PM UTC

    This is now resolved. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Notice April 28, 2026

Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

Detected by Pingoru
Apr 28, 2026, 08:34 PM UTC
Resolved
Apr 24, 2026, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 28, 2026, 08:34 PM UTC

    Incident Summary A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially surfaced under a generic SUPABASE_EDGE_RUNTIME_ERROR code. Timeline & Actions Sunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began. Monday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact. Tuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed). Current Status Mitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.

Read the full incident report →

Major April 27, 2026

Some projects unavailable across multiple regions

Detected by Pingoru
Apr 27, 2026, 12:39 PM UTC
Resolved
Apr 27, 2026, 07:04 PM UTC
Duration
6h 24m
Affected: AuthDashboardDatabase
Timeline · 7 updates
  1. identified Apr 27, 2026, 12:39 PM UTC

    Posting this. “We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects”

  2. identified Apr 27, 2026, 01:31 PM UTC

    The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the dashboard for your own projects at any time.

  3. identified Apr 27, 2026, 01:38 PM UTC

    We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the dashboard for your own projects at any time.

  4. identified Apr 27, 2026, 03:00 PM UTC

    The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the dashboard for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.

  5. identified Apr 27, 2026, 04:22 PM UTC

    The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed.

  6. monitoring Apr 27, 2026, 06:34 PM UTC

    We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue.

  7. resolved Apr 27, 2026, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 27, 2026

Some Projects Unreachable following Project Restart

Detected by Pingoru
Apr 27, 2026, 10:54 AM UTC
Resolved
Apr 27, 2026, 08:05 PM UTC
Duration
9h 11m
Affected: Dashboard
Timeline · 8 updates
  1. identified Apr 27, 2026, 10:54 AM UTC

    We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service.

  2. identified Apr 27, 2026, 11:11 AM UTC

    We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

  3. identified Apr 27, 2026, 11:40 AM UTC

    Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.

  4. monitoring Apr 27, 2026, 01:12 PM UTC

    All impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates.

  5. identified Apr 27, 2026, 02:21 PM UTC

    We’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact.

  6. identified Apr 27, 2026, 04:05 PM UTC

    The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.

  7. monitoring Apr 27, 2026, 05:31 PM UTC

    The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.

  8. resolved Apr 27, 2026, 08:05 PM UTC

    All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.

Read the full incident report →