Render Outage History
Render is up right nowPingoru has recorded 82 incidents for Render: 77 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 8 | 16 of 720 (2%) |
| May 2026 | 6 | 4 of 744 (1%) |
| June 2026 | 10 | 12 of 720 (2%) |
| July 2026 | 9 | 43 of 744 (6%) |
| August 2026 | 3 | 6 of 744 (1%) |
| September 2026 | 5 | 2 of 720 (0%) |
| October 2026 | 6 | 11 of 737 (1%) |
Incidents, newest first
Notice October 24, 2026 Platform emails not being sent 29m
Started Oct 24, 2026, 07:11 AM UTC· resolved Oct 24, 2026, 07:41 AM UTC
- identified Oct 24, 2026, 07:11 AM UTC
Transactional emails for platform events, including but not limited to new account sign-up email confirmations, service build/deploy failure notifications, password resets, etc. are currently failing to send. We are currently addressing the issue.
- monitoring Oct 24, 2026, 07:30 AM UTC
We have applied a fix and see messages successfully delivering. We are monitoring for any further issues.
- resolved Oct 24, 2026, 07:41 AM UTC
This incident has been resolved.
Minor October 23, 2026 Degraded network performance 1h 28m Web Services, Web Services, Static Sites
Started Oct 23, 2026, 04:05 PM UTC· resolved Oct 23, 2026, 05:34 PM UTC
- identified Oct 23, 2026, 04:05 PM UTC
We have identified degraded networking performance linked to an upstream provider - we will continue to provide updates here.
- identified Oct 23, 2026, 04:09 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 23, 2026, 04:10 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 23, 2026, 04:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 23, 2026, 05:34 PM UTC
This incident has been resolved.
Minor October 20, 2026 Deploying from GitLab may intermittently fail 3h 40m
Started Oct 20, 2026, 08:48 PM UTC· resolved Oct 21, 2026, 12:29 AM UTC
- investigating Oct 20, 2026, 08:48 PM 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.
- identified Oct 20, 2026, 09:16 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 20, 2026, 10:23 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 20, 2026, 11:46 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 21, 2026, 12:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 21, 2026, 12:29 AM UTC
This incident has been resolved.
Minor October 15, 2026 Dashboard not updating in real time; Some Workflows SDK requests timing out 1h 35m Render Dashboard, Workflows, Workflows, Workflows and 2 more
Started Oct 15, 2026, 08:58 PM UTC· resolved Oct 15, 2026, 10:33 PM UTC
- identified Oct 15, 2026, 08:58 PM 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 state. - SDK calls that wait for a task run to finish may fail with a 500 error after about 60 seconds. The task runs themselves keep running and complete normally. To check a task run's status, use GET /v1/task-runs/{taskRunId}. Deploys, running services, databases, and logs are not affected.
- monitoring Oct 15, 2026, 09:53 PM UTC
Our upstream provider has resolved the issue, and affected Render services have recovered. We’re continuing to monitor.
- resolved Oct 16, 2026, 01:12 AM UTC
This incident has been resolved.
Major October 14, 2026 Builds, deploys, and queued deploys are not starting in all regions 2h 45m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Oct 14, 2026, 07:32 PM UTC· resolved Oct 14, 2026, 10:18 PM UTC
- investigating Oct 14, 2026, 07:32 PM UTC
We are currently investigating this issue.
- identified Oct 14, 2026, 07:39 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 14, 2026, 07:45 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 14, 2026, 07:47 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 14, 2026, 08:41 PM UTC
We are temporarily pausing deploys to free services.
- identified Oct 14, 2026, 08:55 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 14, 2026, 08:57 PM 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.
- monitoring Oct 14, 2026, 09:43 PM 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.
- resolved Oct 14, 2026, 10:18 PM UTC
This incident has been resolved.
- postmortem Oct 22, 2026, 05:58 PM UTC
### Summary On October 14, 2026, between 12:12 and 15:08 PDT \(19:12 - 22:08 UTC\), builds and deploys across all regions failed to start, stalled, or were significantly delayed during two periods of impact totaling about 2 hours and 20 minutes. The cause was a database schema migration run as part of a planned version upgrade of our internal job scheduler that coordinates builds, deploys, and other critical platform operations. The migration led to high load and a longer-than-expected recovery time of this system’s database. We will change how we perform upgrades and modifications of this system in a highly available fashion in the future so that a similar change cannot cause an outage again. ### Impact There were two periods of impact. During this time, live user services were not affected, but builds and deploys across all regions failed to start, failed to finish, or were significantly delayed. **Period 1: 12:12 - 12:40 PDT \(19:12 - 19:40 UTC\), about 28 minutes** * New builds and deploys did not start. Deploys in progress stalled. * Some requests to create a deploy through the Dashboard, API, and CLI returned errors \(HTTP 500\). **Partial recovery: 12:40 - 13:18 PDT \(19:40 - 20:18 UTC\)** * Builds and deploys ran, but deploys took about 20 seconds to start instead of a few hundred milliseconds. **Period 2: 13:18 - 15:08 PDT \(20:18 - 22:08 UTC\), about 1 hour 50 minutes** * Builds and deploys were delayed, stalled in progress \(including in pre-deploy\), or failed. From 13:51 PDT, almost no new builds were able to start. * Some queued deploys did not start after recovery, and cancelling them through the API had no effect. Users needed to retry these deploys. ### Root Cause Render uses an internal job scheduler system to coordinate builds, deploys, and other critical platform operations. We were rolling out improvements to how it distributes work, and began a planned version upgrade of this system in production after a successful practice run in a test environment. The upgrade included a database schema migration that locked a large table and drove database CPU utilization to 100%. This database stores both the system’s core job state and secondary data used for search and reporting. The system could not read or write job state reliably, so builds and deploys stopped or slowed. Engineers were alerted to the issue quickly and reverted the upgrade. However, three factors extended the impact: * A pre-upgrade step to create a database clone for rollback could not be completed due to an error from the underlying cloud provider, so a fast rollback was not available. * The migration continued to run on the database after the client performing the upgrade was stopped and the upgrade reverted. It was found and terminated at 13:49 PDT, about 1.5 hours after it started. * An attempt to add capacity to the database failed due to an error from the underlying cloud provider. ### Timeline All times are PDT on 2026-10-14 \(UTC-7\). * **12:13** - The upgrade is started, including the database schema migration. Database load rises and builds and deploys stop starting. * **12:24** - Impact to builds and deploys identified. Incident escalated. * **12:33** - Status page incident opened. * **12:34** - Engineers revert the upgrade and stop the client performing the schema migration. * **12:37** - Job scheduler system recovers. Builds and deploys resume, with slower deploy start times. End of Period 1. * **13:17** - Engineers restart one unhealthy instance of the system to rebalance load. Database connections and errors increase across the system. Start of Period 2. * **13:37** - Free-tier deploys paused to reduce load. * **13:49** - Engineers find the schema migration still running on the database and terminate it. * **14:16** - Database restarted. An attempt to add database capacity fails because of an error from the underlying cloud provider. * **14:27** - Remaining components of the system restarted. * **14:30** - Builds and deploys start to recover, with slower than usual build and deploy times as the backlog is processed. * **15:08** - Deploy start times return to normal and database load returns to pre-incident levels. End of Period 2. * **15:11** - Free-tier deploys and spin-ups gradually re-enabled. * **15:18** - Incident resolved. ### Mitigations **Completed during the incident** * Reverted the job scheduler component upgrade and configuration change \(12:34 PDT\). * Paused free-tier deploys and spin-ups to reduce load, then re-enabled them gradually after recovery. * Terminated the schema migration that was still running on the database \(13:49 PDT\). * Restarted the database and the job scheduler system to restore normal operation. * Paused the upgrade in production until the upgrade process is changed. **Ongoing \(started during the incident\)** * This database is being upgraded to support cross-zone High Availability. **Planned** * Implement a new upgrade and deployment practice for this component: we will implement blue-green deploys to avoid upgrading this system under load in the future. * Adjust the underlying storage mechanisms for the job scheduler to be better suited to this workload type, after we have implemented blue-green deploys.
Minor October 3, 2026 Degraded Dashboard Performance; Degraded builds & deploys in Oregon 46m Render Dashboard, Builds and Deploys
Started Oct 03, 2026, 07:35 PM UTC· resolved Oct 03, 2026, 08:21 PM UTC
- investigating Oct 03, 2026, 07:35 PM UTC
We are currently investigating this issue.
- investigating Oct 03, 2026, 07:53 PM UTC
We are continuing to investigate this issue.
- monitoring Oct 03, 2026, 08:13 PM UTC
Impacted components are recovering. We are monitoring the situation.
- resolved Oct 03, 2026, 08:21 PM UTC
This incident has been resolved.
Minor September 27, 2026 Observing service instability from our upstream provider AWS in Oregon region 1h 36m Web Services, Cron Jobs, Background Workers, Builds and Deploys and 5 more
Started Sep 27, 2026, 01:24 AM UTC· resolved Sep 27, 2026, 03:01 AM UTC
- investigating Sep 27, 2026, 01:24 AM UTC
We are currently investigating this issue.
- monitoring Sep 27, 2026, 01:36 AM UTC
Our upstream provider has begun recovering. Services in Oregon are improving, and we're continuing to monitor.
- monitoring Sep 27, 2026, 02:17 AM UTC
All services, except for the free web services tier, have recovered. We continue to monitor.
- resolved Sep 27, 2026, 03:01 AM UTC
This incident has been resolved.
Major September 25, 2026 Build and deploy failures in Oregon 12m Builds and Deploys
Started Sep 25, 2026, 06:26 PM UTC· resolved Sep 25, 2026, 06:38 PM UTC
- investigating Sep 25, 2026, 06:26 PM UTC
We are currently investigating this issue.
- resolved Sep 25, 2026, 06:38 PM UTC
Builds and deploys failed for a subset of services in Oregon. Services using a prebuilt Docker image and static sites were unaffected.
Minor September 23, 2026 Key Value service restarts –
Started Sep 23, 2026, 11:30 PM UTC· resolved Sep 23, 2026, 11:30 PM UTC
- resolved Sep 24, 2026, 11:36 PM 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.
Minor September 9, 2026 Elevated Build and Deploy Times in the Oregon Region 11m Builds and Deploys
Started Sep 09, 2026, 09:26 PM UTC· resolved Sep 09, 2026, 09:38 PM UTC
- investigating Sep 09, 2026, 09:26 PM UTC
We are currently investigating this issue.
- investigating Sep 09, 2026, 09:31 PM UTC
We are continuing to investigate this issue.
- investigating Sep 09, 2026, 09:32 PM UTC
We are continuing to investigate this issue.
- identified Sep 09, 2026, 09:34 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Sep 09, 2026, 09:38 PM UTC
This incident has been resolved.
Major September 2, 2026 Degraded builds/deploys 20m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Sep 02, 2026, 05:19 PM UTC· resolved Sep 02, 2026, 05:40 PM UTC
- investigating Sep 02, 2026, 05:19 PM UTC
We are currently investigating this issue.
- monitoring Sep 02, 2026, 05:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 02, 2026, 05:40 PM UTC
This incident has been resolved.
Minor August 31, 2026 Some Web services in Oregon unavailable 10m
Started Aug 31, 2026, 07:20 PM UTC· resolved Aug 31, 2026, 07:30 PM UTC
- resolved Aug 31, 2026, 08:24 PM UTC
Some web services in Oregon were unavailable between 19:20 and 19:30 UTC.
Major August 31, 2026 Service instability in Singapore 2h 21m Web Services, Builds and Deploys
Started Aug 31, 2026, 03:47 PM UTC· resolved Aug 31, 2026, 06:09 PM UTC
- investigating Aug 31, 2026, 03:47 PM 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 as more information becomes available.
- investigating Aug 31, 2026, 04:08 PM UTC
We've observed that deploys are primarily affected by this.
- investigating Aug 31, 2026, 04:33 PM 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.
- monitoring Aug 31, 2026, 05:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 31, 2026, 06:09 PM UTC
This incident has been resolved.
Major August 20, 2026 Deployment Issues 3h 53m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Aug 20, 2026, 03:47 PM UTC· resolved Aug 20, 2026, 07:40 PM UTC
- investigating Aug 20, 2026, 03:47 PM UTC
We are currently investigating this issue.
- identified Aug 20, 2026, 04:12 PM 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.
- monitoring Aug 20, 2026, 05:27 PM 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.
- monitoring Aug 20, 2026, 05:45 PM UTC
We have observed full recovery. We are continuing to monitor for any further issues.
- resolved Aug 20, 2026, 07:40 PM UTC
This incident has been resolved.
Minor July 27, 2026 Degraded dashboard performance 1d 4h Render Dashboard, Render REST API
Started Jul 27, 2026, 02:43 PM UTC· resolved Jul 28, 2026, 07:35 PM UTC
- investigating Jul 27, 2026, 02:43 PM UTC
Requests through the dashboard may be slower than usual. We're currently investigating the issue.
- investigating Jul 27, 2026, 04:20 PM UTC
We are continuing to investigate this issue.
- investigating Jul 27, 2026, 05:59 PM UTC
We are continuing to investigate this issue.
- investigating Jul 27, 2026, 06:27 PM 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.
- monitoring Jul 27, 2026, 08:18 PM 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.
- monitoring Jul 27, 2026, 11:58 PM 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).
- resolved Jul 28, 2026, 07:35 PM UTC
We've continued to observe no further issues and deploy failure reasons have been re-enabled.
Critical July 24, 2026 Service Disruption in Oregon 2h 14m Web Services
Started Jul 24, 2026, 11:16 AM UTC· resolved Jul 24, 2026, 01:30 PM UTC
- investigating Jul 24, 2026, 11:16 AM 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.
- monitoring Jul 24, 2026, 11:27 AM UTC
We've observed recovery across all services and are now monitoring the situation.
- monitoring Jul 24, 2026, 11:44 AM UTC
We believe the issue was caused by an upstream provider. We're continuing to monitor the situation.
- resolved Jul 24, 2026, 01:30 PM UTC
This incident has now been resolved.
Minor July 20, 2026 Degraded builds/deploys (all regions) 1h 29m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Jul 20, 2026, 12:41 AM UTC· resolved Jul 20, 2026, 02:11 AM UTC
- investigating Jul 20, 2026, 12:41 AM UTC
We are currently investigating this issue.
- identified Jul 20, 2026, 12:55 AM UTC
GitHub continues to report an outage, https://www.githubstatus.com. This is causing authentication failures when trying to deploy from a GitHub repository.
- monitoring Jul 20, 2026, 01:54 AM UTC
We are now seeing a recovery in our build failure rate. We are continuing to monitor the issue.
- resolved Jul 20, 2026, 02:11 AM UTC
Builds failure rates have recovered. Resolving.
Critical July 19, 2026 GitHub git clone 403 errors 5h 36m Builds and Deploys
Started Jul 19, 2026, 03:44 AM UTC· resolved Jul 19, 2026, 09:20 AM UTC
- investigating Jul 19, 2026, 03:44 AM UTC
We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.
- identified Jul 19, 2026, 03:55 AM 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.
- identified Jul 19, 2026, 05:57 AM 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.
- identified Jul 19, 2026, 08:29 AM UTC
We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.
- monitoring Jul 19, 2026, 09:10 AM UTC
Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.
- resolved Jul 19, 2026, 09:20 AM UTC
This incident has been resolved.
Critical July 16, 2026 GitHub outage affecting new service creation and service deploys 1h 32m Builds and Deploys, Builds and Deploys, Builds and Deploys, Builds and Deploys and 1 more
Started Jul 16, 2026, 10:42 PM UTC· resolved Jul 17, 2026, 12:14 AM UTC
- investigating Jul 16, 2026, 10:42 PM UTC
We are currently investigating this issue.
- investigating Jul 16, 2026, 10:42 PM UTC
We are continuing to investigate this issue.
- identified Jul 16, 2026, 11:09 PM UTC
GitHub has updated its status page to report degraded REST API availability: https://www.githubstatus.com/incidents/gxycch3076xk
- monitoring Jul 17, 2026, 12:13 AM UTC
GitHub reports that they have mitigated their incident and are monitoring to ensure stability.
- resolved Jul 17, 2026, 12:14 AM UTC
This incident has been resolved.
Major July 15, 2026 Some users enrolled in 2FA are experiencing login issues 1h 5m Render Dashboard
Started Jul 15, 2026, 09:50 PM UTC· resolved Jul 15, 2026, 10:56 PM UTC
- investigating Jul 15, 2026, 09:50 PM UTC
Some users enrolled in 2FA report login loops when attempting to access the Render dashboard. We're investigating.
- identified Jul 15, 2026, 09:55 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 15, 2026, 10:06 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 15, 2026, 10:56 PM UTC
This incident has been resolved.
Critical July 15, 2026 Render Dashboard Unavailable 31m Render Dashboard
Started Jul 15, 2026, 12:22 AM UTC· resolved Jul 15, 2026, 12:54 AM UTC
- investigating Jul 15, 2026, 12:22 AM UTC
We are currently investigating an issue with the availability of the Render Dashboard.
- monitoring Jul 15, 2026, 12:51 AM 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.
- resolved Jul 15, 2026, 12:54 AM UTC
This issue has been resolved.
Major July 9, 2026 Some services and datastores in Singapore experiencing brief disruptions 26m Web Services, Cron Jobs, Background Workers, PostgreSQL and 2 more
Started Jul 09, 2026, 06:18 PM UTC· resolved Jul 09, 2026, 06:44 PM UTC
- monitoring Jul 09, 2026, 06:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 09, 2026, 06:44 PM UTC
This incident has been resolved.
Minor July 2, 2026 Delayed wildcard issuance or renewal 50m Custom Domains
Started Jul 02, 2026, 07:09 PM UTC· resolved Jul 02, 2026, 07:59 PM UTC
- identified Jul 02, 2026, 07:09 PM UTC
Due to an ongoing LetsEncrypt incident, wildcard certificates may be slow to issue/renew. We are actively monitoring the situation.
- resolved Jul 02, 2026, 07:59 PM UTC
Issuance has returned to expected performance and we've observed no further impact.
Minor June 23, 2026 External connections to Postgres services may terminate intermittently 1h 45m PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL and 1 more
Started Jun 23, 2026, 11:59 PM UTC· resolved Jun 24, 2026, 01:45 AM UTC
- investigating Jun 24, 2026, 12:00 AM UTC
We are currently investigating this issue.
- monitoring Jun 24, 2026, 12:32 AM UTC
We have rolled out a fix for this issue and are now monitoring it before confirming the resolution.
- monitoring Jun 24, 2026, 01:44 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 24, 2026, 01:45 AM UTC
This has now been resolved. Customers will have seen an impact from Jun 22, 2026, at 11:50 UTC.
Minor June 18, 2026 Slow/failing wildcard certificates related to LetsEncrypt incident 3h 11m Custom Domains
Started Jun 18, 2026, 09:06 PM UTC· resolved Jun 19, 2026, 12:17 AM UTC
- identified Jun 18, 2026, 09:06 PM 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.
- monitoring Jun 18, 2026, 11:15 PM UTC
We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.
- resolved Jun 19, 2026, 12:17 AM UTC
We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.