Render

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 20:48 UTC

   If cloning fails, the deploy will fail. Deploy logs will provide errors related to that failure. Retrying a deploy may succeed. We are currently investigating this issue.

2. identified 2026-10-20 21:16 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-10-20 22:23 UTC

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

4. identified 2026-10-20 23:46 UTC

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

5. monitoring 2026-10-21 00:08 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-10-21 00:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard, Workflows, Workflows, Workflows, Workflows, Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-15 20:58 UTC

   We've identified an issue with an upstream cloud provider that is affecting real-time updates on Render. Since approximately 19:10 UTC: - Dashboard: Deploy status, service events, and service and task run statuses may not update automatically. Refresh the page to see the current...

2. monitoring 2026-10-15 21:53 UTC

   Our upstream provider has resolved the issue, and affected Render services have recovered. We’re continuing to monitor.

3. resolved 2026-10-15 22:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 19:32 UTC

   We are currently investigating this issue.

2. identified 2026-10-14 19:39 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-14 19:45 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-10-14 19:47 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-10-14 20:41 UTC

   We are temporarily pausing deploys to free services.

6. identified 2026-10-14 20:55 UTC

   The issue has been identified and a fix is being implemented.

7. identified 2026-10-14 20:57 UTC

   Builds are failing to start again across all regions, and our team is still working to address the root cause. Deploys for free services remain paused. We'll share another update as soon as we have more information.

8. monitoring 2026-10-14 21:43 UTC

   A fix has been implemented, and we are monitoring the results. Deploys and builds for services running on free instances continue to be paused.

9. resolved 2026-10-14 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-03 19:35 UTC

   We are currently investigating this issue.

2. investigating 2026-10-03 19:53 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-03 20:13 UTC

   Impacted components are recovering. We are monitoring the situation.

4. resolved 2026-10-03 20:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services, Cron Jobs, Background Workers, Builds and Deploys, PostgreSQL, Redis, Web Services - Free Tier, Autoscaling, Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-27 01:24 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-27 01:36 UTC

   Our upstream provider has begun recovering. Services in Oregon are improving, and we're continuing to monitor.

3. monitoring 2026-09-27 02:17 UTC

   All services, except for the free web services tier, have recovered. We continue to monitor.

4. resolved 2026-09-27 03:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-25 18:26 UTC

   We are currently investigating this issue.

2. resolved 2026-09-25 18:38 UTC

   Builds and deploys failed for a subset of services in Oregon. Services using a prebuilt Docker image and static sites were unaffected.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-09-23 23:30 UTC

   Around 23:31 UTC on 2026-09-23, Key Value services created prior to 2024-03-05 were inadvertently restarted due to a configuration change on our end. No further restarts are planned or expected as a result of that change.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-09 21:26 UTC

   We are currently investigating this issue.

2. investigating 2026-09-09 21:31 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-09 21:32 UTC

   We are continuing to investigate this issue.

4. identified 2026-09-09 21:34 UTC

   The issue has been identified and a fix is being implemented.

5. resolved 2026-09-09 21:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 17:19 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-02 17:30 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-02 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-31 19:30 UTC

   Some web services in Oregon were unavailable between 19:20 and 19:30 UTC.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services, Builds and Deploys

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 15:47 UTC

   We are investigating service instability affecting some web services in our Singapore region. Customers may experience unexpected service restarts or intermittent availability. Our team is actively investigating and working to restore normal operation. We will provide an update...

2. investigating 2026-08-31 16:08 UTC

   We've observed that deploys are primarily affected by this.

3. investigating 2026-08-31 16:33 UTC

   Inbound traffic to Singapore services is impacted. Free service spin-ups (from idle) in Singapore have been temporarily disabled while we continue to investigate.

4. monitoring 2026-08-31 17:22 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-08-31 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 15:47 UTC

   We are currently investigating this issue.

2. identified 2026-08-20 16:12 UTC

   An issue has been identified with our upstream provider, Google Cloud. Free Web Services: Builds/deploys and spin-up have been temporarily disabled while we work to mitigate the issue.

3. monitoring 2026-08-20 17:27 UTC

   We are observing recovery for builds and deploys in all regions. Builds, deploys, and spin-up for free web services have been re-enabled. Some customers may continue to see elevated latency while recovery progresses. We are continuing to monitor.

4. monitoring 2026-08-20 17:45 UTC

   We have observed full recovery. We are continuing to monitor for any further issues.

5. resolved 2026-08-20 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard, Render REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 14:43 UTC

   Requests through the dashboard may be slower than usual. We're currently investigating the issue.

2. investigating 2026-07-27 16:20 UTC

   We are continuing to investigate this issue.

3. investigating 2026-07-27 17:59 UTC

   We are continuing to investigate this issue.

4. investigating 2026-07-27 18:27 UTC

   The REST API is also experiencing degraded performance. As a result, requests to it may experience timeouts and you may need to retry your request. We are continuing to investigate.

5. monitoring 2026-07-27 20:18 UTC

   We've implemented a fix and are monitoring the results. Deploy failure reasons will be temporarily unavailable. Deploy failure events will still be generated. We will provide an update once deploy failure reasons are re-enabled.

6. monitoring 2026-07-27 23:58 UTC

   No further issues have been observed since our fixes. The Dashboard and REST API remain fully operational. Deploy failure reasons are still disabled. We will update this incident once they are re-enabled. There are no further updates expected for today (2026-07-27, UTC-7).

7. resolved 2026-07-28 19:35 UTC

   We've continued to observe no further issues and deploy failure reasons have been re-enabled.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 11:16 UTC

   We are investigating an infrastructure issue affecting services hosted in our Oregon region. Some services may be unreachable or experience failed requests. Our engineering team is actively working to identify the cause and restore normal operation.

2. monitoring 2026-07-24 11:27 UTC

   We've observed recovery across all services and are now monitoring the situation.

3. monitoring 2026-07-24 11:44 UTC

   We believe the issue was caused by an upstream provider. We're continuing to monitor the situation.

4. resolved 2026-07-24 13:30 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-20 00:41 UTC

   We are currently investigating this issue.

2. identified 2026-07-20 00:55 UTC

   GitHub continues to report an outage, https://www.githubstatus.com. This is causing authentication failures when trying to deploy from a GitHub repository.

3. monitoring 2026-07-20 01:54 UTC

   We are now seeing a recovery in our build failure rate. We are continuing to monitor the issue.

4. resolved 2026-07-20 02:11 UTC

   Builds failure rates have recovered. Resolving.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-19 03:44 UTC

   We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.

2. identified 2026-07-19 03:55 UTC

   Services failing to deploy are those deployed in Frankfurt. Running services are not affected, only the deploy process is failing. We are still working to determine the cause of this error for those services.

3. identified 2026-07-19 05:57 UTC

   Users with services hosted in Frankfurt that rely on GitHub repositories for deployments continue to see 403 errors in their logs causing the deployment to fail. We are continuing to work on this issue within our own systems and have reached out to GitHub.

4. identified 2026-07-19 08:29 UTC

   We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.

5. monitoring 2026-07-19 09:10 UTC

   Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.

6. resolved 2026-07-19 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-16 22:42 UTC

   We are currently investigating this issue.

2. investigating 2026-07-16 22:42 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-16 23:09 UTC

   GitHub has updated its status page to report degraded REST API availability: https://www.githubstatus.com/incidents/gxycch3076xk

4. monitoring 2026-07-17 00:13 UTC

   GitHub reports that they have mitigated their incident and are monitoring to ensure stability.

5. resolved 2026-07-17 00:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-15 21:50 UTC

   Some users enrolled in 2FA report login loops when attempting to access the Render dashboard. We're investigating.

2. identified 2026-07-15 21:55 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-15 22:06 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-15 22:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-15 00:22 UTC

   We are currently investigating an issue with the availability of the Render Dashboard.

2. monitoring 2026-07-15 00:51 UTC

   We have identified the root cause of this issue and have made a change to resolve it. Our dashboard is back online. We are now monitoring the issue to ensure it is fully resolved.

3. resolved 2026-07-15 00:54 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services, Cron Jobs, Background Workers, PostgreSQL, Redis, Web Services - Free Tier

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-09 18:18 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-07-09 18:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Custom Domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-02 19:09 UTC

   Due to an ongoing LetsEncrypt incident, wildcard certificates may be slow to issue/renew. We are actively monitoring the situation.

2. resolved 2026-07-02 19:59 UTC

   Issuance has returned to expected performance and we've observed no further impact.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-24 00:00 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-24 00:32 UTC

   We have rolled out a fix for this issue and are now monitoring it before confirming the resolution.

3. monitoring 2026-06-24 01:44 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-06-24 01:45 UTC

   This has now been resolved. Customers will have seen an impact from Jun 22, 2026, at 11:50 UTC.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Custom Domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-18 21:06 UTC

   We are seeing slow or failing issuance of wildcard certificates due to an ongoing incident with the LetsEncrypt certificate authority. We are actively monitoring the situation on our end.

2. monitoring 2026-06-18 23:15 UTC

   We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.

3. resolved 2026-06-19 00:17 UTC

   We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 19:42 UTC

   We are currently investigating the problem. Try this work-around to get deploys going again: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to...

2. monitoring 2026-06-11 19:59 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-11 20:32 UTC

   This incident has been resolved. If you still have a stuck queued deploy, follow the instructions below under "Investigating" to clear the queue. It should then work again as expected going forward.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 18:56 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-11 19:06 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-11 19:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-11 16:01 UTC

   The earlier "Platform latency" incident has affected queued deploys. We are implementing a fix

2. identified 2026-06-11 16:44 UTC

   We are continuing to work on a fix for this issue. In the meantime, stuck deploys can be cleared with these steps: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the...

3. resolved 2026-06-11 18:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 14:37 UTC

   We are currently investigating delays across the platform affecting builds, deploys, and webhooks.

2. monitoring 2026-06-11 14:56 UTC

   A fix has been implemented, and we are continuing to monitor. Auto-deploys would have been affected/missed by these delays and will need to be retriggered.

3. resolved 2026-06-11 14:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-09 20:01 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-09 20:55 UTC

   We're seeing evidence of recovery and are continuing to monitor the situation.

3. resolved 2026-06-09 21:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-05 16:21 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-05 16:48 UTC

   We're seeing signs of recovery. Please try redeploying any affected services.

3. resolved 2026-06-05 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-04 23:27 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-04 23:38 UTC

   Our email provider is experiencing delays in sending emails. Emails will still be delivered after that delay. This impacts verification emails and notifications for workspaces or services. We're monitoring the situation.

3. monitoring 2026-06-04 23:43 UTC

   Our provider has resolved the delay and backlogged emails are being processed. We're continuing to monitor.

4. resolved 2026-06-05 00:39 UTC

   Outstanding emails have been sent and processing has returned to expected operation.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Metrics/Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-01 21:25 UTC

   We are currently investigating this issue. It affects metrics only. Logs are unaffected.

2. monitoring 2026-06-01 21:32 UTC

   We're seeing recovery and are monitoring.

3. resolved 2026-06-01 21:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Custom Domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-22 15:53 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-22 16:25 UTC

   Our upstream provider has deployed a fix and we're seeing gradual recovery.

3. resolved 2026-05-22 16:37 UTC

   Our upstream provider has resolved the issue and custom domain provisioning has recovered.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: PostgreSQL

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-20 18:01 UTC

   We are currently investigating this issue.

2. identified 2026-05-20 18:17 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-20 18:23 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-20 18:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-12 20:00 UTC

   Between approximately 19:45 UTC and 20:30 UTC, logs may be unavailable in the Dashboard. For logs that are unavailable, logs were not streamed to third-party logging providers.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-11 17:07 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-11 17:11 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-11 17:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Custom Domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-05-08 20:22 UTC

   Due to an ongoing incident, Let's Encrypt has paused all certificate issuance. This primarily impacts wildcard domains on Render. In rare instances, non-wildcard custom domains may be using Let's Encrypt for their certificates.

2. resolved 2026-05-08 21:06 UTC

   Let's Encrypt has resumed certificate issuance.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, Workflows, Workflows, Workflows, Workflows, Workflows

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-07 02:00 UTC

   We're investigating reports of Postgres unavailability in multiple regions. At this point we believe this only impacts databases with HA turned on.

2. investigating 2026-05-07 02:01 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-07 02:07 UTC

   We are continuing to investigate this issue.

4. identified 2026-05-07 02:21 UTC

   We've identified the issue and are implementing a fix.

5. identified 2026-05-07 02:34 UTC

   We're bringing the affected Postgres instances back online and expect full recovery within fifteen minutes.

6. identified 2026-05-07 02:38 UTC

   We're continuing to see instance recovery across the fleet. Render Workflows is now fully operational.

7. identified 2026-05-07 02:47 UTC

   All affected instances are back online, though a few databases may still show a stale 'Unready' status. We are working to refresh the status.

8. resolved 2026-05-07 02:54 UTC

   Everything is back to normal, and the incident is now resolved. We are planning long-term mitigations to prevent this issue from recurring, and we will share the results of our investigation with all affected customers.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-23 16:51 UTC

   We are investigating an issue where new services created in the Oregon region are taking longer than usual to deploy.

2. identified 2026-04-23 16:59 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-23 17:06 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-23 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services, PostgreSQL

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-16 23:36 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-04-16 23:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Render Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 14:31 UTC

   We are currently investigating reports of issues connecting BitBucket accounts/repos to Render. Existing services configured with a BitBucket repo are unaffected.

2. identified 2026-04-14 15:12 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-04-14 16:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-13 22:03 UTC

   We are seeing image pull failures within the Oregon region. We have identified the problem and are working on a fix.

2. monitoring 2026-04-13 22:18 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-13 22:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-10 14:41 UTC

   Ongoing maintenance is underway for static IPs in the Oregon region. Services in this region may experience changes to their outbound IP ranges.

2. resolved 2026-04-10 14:56 UTC

   The maintenance has been completed successfully.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-08 12:30 UTC

   Between 12:40 UTC and 18:10 UTC, creation of stateful services in Oregon was delayed. Stateful services are any of Postgres, Key Value, or services with a persistent disk.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Web Services, Web Services, Cron Jobs, Cron Jobs, Background Workers, Background Workers, Builds and Deploys, Builds and Deploys, Web Services - Free Tier, Web Services - Free Tier

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-08 09:57 UTC

   This issue may affect new instances during builds, scaling, and similar operations. You may experience build/deploy failures. We are still investigating.

2. investigating 2026-04-08 10:31 UTC

   We have temporarily disabled free services in Singapore. We are continuing to investigate and work to mitigate the issue.

3. investigating 2026-04-08 10:54 UTC

   We are seeing some recovery following our mitigation efforts, but we are still working to identify the root cause for a long-term resolution.

4. investigating 2026-04-08 11:22 UTC

   We are continuing to investigate this issue.

5. identified 2026-04-08 11:23 UTC

   Services with paid compute should now be operating normally. Please note that free services in this region are still intermittently disabled.

6. identified 2026-04-08 14:42 UTC

   We are now seeing the same issue affecting services in Oregon partially. We are investigating to remediate this as quickly as possible.

7. identified 2026-04-08 15:02 UTC

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

8. monitoring 2026-04-08 15:02 UTC

   We're seeing recovery across all regions.

9. monitoring 2026-04-08 16:05 UTC

   We are disabling new free services in Singapore and partially in Oregon.

10. monitoring 2026-04-08 18:08 UTC

    We are continuing to monitor for any further issues.

11. monitoring 2026-04-08 18:48 UTC

    Paid services are continuing to see recovery across builds and deploys. Free services remain disabled and will return errors if loaded in a browser. Singapore and part of Oregon remain impacted.

12. monitoring 2026-04-08 19:44 UTC

    Provisioning is recovering for free and paid services across all regions. Free services have resumed serving traffic. We are continuing to monitor for further issues.

13. resolved 2026-04-08 22:11 UTC

    We've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.

Excerpts are shortened. Read the full incident on Render's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-07 18:00 UTC

   Between 18:04 and 19:10 UTC, workflows were unable to be viewed in the Dashboard. All workflows continued to run and were otherwise operational. This issue has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Workflows

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 14:45 UTC

   We are working on resolving the issue.

2. identified 2026-03-25 16:40 UTC

   The issue has been identified, and there should be no issues scheduling tasks at this time. We are still working to ensure it is fully resolved.

3. monitoring 2026-03-26 17:54 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-03-26 19:51 UTC

   This issue is now resolved. A full RCA will be available in the incident page within the next two weeks.

5. postmortem 2026-04-14 13:23 UTC

   Affected customers have been contacted directly. If you would like more details, please contact support at [support@render.com](mailto:support@render.com) or reach out through the chat widget in the Render dashboard.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Metrics/Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-24 13:09 UTC

   The issue has been identified, and we are already monitoring recovery.

2. monitoring 2026-03-24 13:12 UTC

   We are monitoring recovery.

3. resolved 2026-03-24 13:31 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 15:51 UTC

   We are observing a recurrence of the previous incident (https://status.render.com/incidents/d9k4p51v1y7g). The current impact appears to be significantly lower. We are proactively investigating and closely monitoring the situation internally to ensure minimal impact on users.

2. monitoring 2026-03-13 15:53 UTC

   We are currently monitoring.

3. resolved 2026-03-13 18:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Builds and Deploys, Web Services - Free Tier

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 08:52 UTC

   Builds and deployments in the Singapore region are currently experiencing degraded performance. You may notice longer than usual completion times.

2. investigating 2026-03-13 09:27 UTC

   We have disabled services using free instance types in the Singapore region

3. monitoring 2026-03-13 10:18 UTC

   We have re-enabled services using the free instance types in the Singapore region and are currently monitoring the impact.

4. resolved 2026-03-13 11:09 UTC

   We believe this incident has been successfully mitigated. If you continue to experience any issues, please contact support@render.com.

Excerpts are shortened. Read the full incident on Render's status page.

Affected: Custom Domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-09 20:19 UTC

   We are currently investigating this issue.

2. resolved 2026-03-09 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Render's status page.