Render

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

• Issues affecting connections to a subset of Postgres DatabasesNov 5 20:12 UTC · resolved · minor impact
  Restoration reported
  1. Nov 5 20:12 UTC identified: A configuration change to Postgres connection settings caused connection failures for some databases that route traffic through a self managed PgBouncer instance. Updating your self managed PgBouncer to use scram-sha-256 encryption can help remediate the connection failures. If...
  2. Nov 5 23:56 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Platform emails not being sentOct 24 07:11 UTC · resolved
  Restoration reported
  1. Oct 24 07:11 UTC identified: 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.
  2. Oct 24 07:30 UTC monitoring: We have applied a fix and see messages successfully delivering. We are monitoring for any further issues.
  3. Oct 24 07:41 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Degraded network performanceOct 23 16:05 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  1. Oct 23 16:05 UTC identified: We have identified degraded networking performance linked to an upstream provider - we will continue to provide updates here.
  2. Oct 23 16:09 UTC identified: We are continuing to work on a fix for this issue.
  3. Oct 23 16:10 UTC identified: We are continuing to work on a fix for this issue.
  4. Oct 23 16:14 UTC monitoring: A fix has been implemented and we are monitoring the results.
  5. Oct 23 17:34 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Deploying from GitLab may intermittently failOct 20 20:48 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Oct 20 20:48 UTC investigating: 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. Oct 20 21:16 UTC identified: The issue has been identified and a fix is being implemented.
  3. Oct 20 22:23 UTC identified: We are continuing to work on a fix for this issue.
  4. Oct 20 23:46 UTC identified: We are continuing to work on a fix for this issue.
  5. Oct 21 00:08 UTC monitoring: A fix has been implemented and we are monitoring the results.
  6. Oct 21 00:29 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Dashboard not updating in real time; Some Workflows SDK requests timing outOct 15 20:58 UTC · resolved · minor impact
  Restoration reported
  1. Oct 15 20:58 UTC identified: 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...
  2. Oct 15 21:53 UTC monitoring: Our upstream provider has resolved the issue, and affected Render services have recovered. We’re continuing to monitor.
  3. Oct 16 01:12 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Builds, deploys, and queued deploys are not starting in all regionsOct 14 19:32 UTC · postmortem · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Oct 14 19:32 UTC investigating: We are currently investigating this issue.
  2. Oct 14 19:39 UTC identified: The issue has been identified and a fix is being implemented.
  3. Oct 14 19:45 UTC monitoring: A fix has been implemented and we are monitoring the results.
  4. Oct 14 19:47 UTC monitoring: We are continuing to monitor for any further issues.
  5. Oct 14 20:41 UTC monitoring: We are temporarily pausing deploys to free services.
  6. Oct 14 20:55 UTC identified: The issue has been identified and a fix is being implemented.
  7. Oct 14 20:57 UTC identified: 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. Oct 14 21:43 UTC monitoring: 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. Oct 14 22:18 UTC resolved: This incident has been resolved.
  10. Oct 22 17:58 UTC postmortem: ### 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...
  View on the provider's status page
• Degraded Dashboard Performance; Degraded builds & deploys in OregonOct 3 19:35 UTC · resolved · minor impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Oct 3 19:35 UTC investigating: We are currently investigating this issue.
  2. Oct 3 19:53 UTC investigating: We are continuing to investigate this issue.
  3. Oct 3 20:13 UTC monitoring: Impacted components are recovering. We are monitoring the situation.
  4. Oct 3 20:21 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Observing service instability from our upstream provider AWS in Oregon regionSep 27 01:24 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Sep 27 01:24 UTC investigating: We are currently investigating this issue.
  2. Sep 27 01:36 UTC monitoring: Our upstream provider has begun recovering. Services in Oregon are improving, and we're continuing to monitor.
  3. Sep 27 02:17 UTC monitoring: All services, except for the free web services tier, have recovered. We continue to monitor.
  4. Sep 27 03:01 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Build and deploy failures in OregonSep 25 18:26 UTC · resolved · major impact
  Investigation mentioned
  1. Sep 25 18:26 UTC investigating: We are currently investigating this issue.
  2. Sep 25 18:38 UTC resolved: Builds and deploys failed for a subset of services in Oregon. Services using a prebuilt Docker image and static sites were unaffected.
  View on the provider's status page
• Key Value service restartsSep 23 23:30 UTC · resolved · minor impact
  No classified wording
  1. Sep 24 23:36 UTC resolved: 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.
  View on the provider's status page
• Elevated Build and Deploy Times in the Oregon RegionSep 9 21:26 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  View on the provider's status page
• Degraded builds/deploysSep 2 17:19 UTC · resolved · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Some Web services in Oregon unavailableAug 31 19:30 UTC · resolved · minor impact
  Service restricted or degraded
  View on the provider's status page
• Service instability in SingaporeAug 31 15:47 UTC · resolved · major impact
  Service taken offlineInvestigation mentionedRestoration reported
  View on the provider's status page
• Deployment IssuesAug 20 15:47 UTC · resolved · major impact
  Service taken offlineInvestigation mentionedRestoration reported
  View on the provider's status page
• Degraded dashboard performanceJul 27 14:43 UTC · resolved · minor impact
  Service taken offlineService restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Service Disruption in OregonJul 24 11:16 UTC · resolved · critical impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Degraded builds/deploys (all regions)Jul 20 00:41 UTC · resolved · minor impact
  Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
  View on the provider's status page
• GitHub git clone 403 errorsJul 19 03:44 UTC · resolved · critical impact
  Investigation mentionedRestoration reported
  View on the provider's status page
• GitHub outage affecting new service creation and service deploysJul 16 22:42 UTC · resolved · critical impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Some users enrolled in 2FA are experiencing login issuesJul 15 21:50 UTC · resolved · major impact
  Sign-in disruptionInvestigation mentionedRestoration reported
  View on the provider's status page
• Render Dashboard UnavailableJul 15 00:22 UTC · resolved · critical impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Some services and datastores in Singapore experiencing brief disruptionsJul 9 18:18 UTC · resolved · major impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• Delayed wildcard issuance or renewalJul 2 19:09 UTC · resolved · minor impact
  Service restricted or degraded
  View on the provider's status page
• External connections to Postgres services may terminate intermittentlyJun 23 23:59 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  View on the provider's status page