Render Outage History

Render is up right now

Render had 74 outages in the last 2 years totaling 58h 39m of downtime — averaging 3 incidents per month.

There were 74 Render outages since September 17, 2025 totaling 58h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.render.com

Minor July 27, 2026

Degraded dashboard performance

Detected by Pingoru
Jul 27, 2026, 02:43 PM UTC
Resolved
Jul 28, 2026, 07:35 PM UTC
Duration
1d 4h
Affected: Render DashboardRender REST API
Timeline · 7 updates
  1. investigating Jul 27, 2026, 02:43 PM UTC

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

  2. investigating Jul 27, 2026, 04:20 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 27, 2026, 05:59 PM UTC

    We are continuing to investigate this issue.

  4. 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.

  5. 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.

  6. 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).

  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.

Read the full incident report →

Critical July 24, 2026

Service Disruption in Oregon

Detected by Pingoru
Jul 24, 2026, 11:16 AM UTC
Resolved
Jul 24, 2026, 01:30 PM UTC
Duration
2h 14m
Affected: Web Services
Timeline · 4 updates
  1. 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.

  2. monitoring Jul 24, 2026, 11:27 AM UTC

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

  3. 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.

  4. resolved Jul 24, 2026, 01:30 PM UTC

    This incident has now been resolved.

Read the full incident report →

Minor July 20, 2026

Degraded builds/deploys (all regions)

Detected by Pingoru
Jul 20, 2026, 12:41 AM UTC
Resolved
Jul 20, 2026, 02:11 AM UTC
Duration
1h 29m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 4 updates
  1. investigating Jul 20, 2026, 12:41 AM UTC

    We are currently investigating this issue.

  2. 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.

  3. 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.

  4. resolved Jul 20, 2026, 02:11 AM UTC

    Builds failure rates have recovered. Resolving.

Read the full incident report →

Critical July 19, 2026

GitHub git clone 403 errors

Detected by Pingoru
Jul 19, 2026, 03:44 AM UTC
Resolved
Jul 19, 2026, 09:20 AM UTC
Duration
5h 36m
Affected: Builds and Deploys
Timeline · 6 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. resolved Jul 19, 2026, 09:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 16, 2026

GitHub outage affecting new service creation and service deploys

Detected by Pingoru
Jul 16, 2026, 10:42 PM UTC
Resolved
Jul 17, 2026, 12:14 AM UTC
Duration
1h 32m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 5 updates
  1. investigating Jul 16, 2026, 10:42 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 16, 2026, 10:42 PM UTC

    We are continuing to investigate this issue.

  3. 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

  4. monitoring Jul 17, 2026, 12:13 AM UTC

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

  5. resolved Jul 17, 2026, 12:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 15, 2026

Some users enrolled in 2FA are experiencing login issues

Detected by Pingoru
Jul 15, 2026, 09:50 PM UTC
Resolved
Jul 15, 2026, 10:56 PM UTC
Duration
1h 5m
Affected: Render Dashboard
Timeline · 4 updates
  1. 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.

  2. identified Jul 15, 2026, 09:55 PM UTC

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

  3. monitoring Jul 15, 2026, 10:06 PM UTC

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

  4. resolved Jul 15, 2026, 10:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 15, 2026

Render Dashboard Unavailable

Detected by Pingoru
Jul 15, 2026, 12:22 AM UTC
Resolved
Jul 15, 2026, 12:54 AM UTC
Duration
31m
Affected: Render Dashboard
Timeline · 3 updates
  1. investigating Jul 15, 2026, 12:22 AM UTC

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

  2. 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.

  3. resolved Jul 15, 2026, 12:54 AM UTC

    This issue has been resolved.

Read the full incident report →

Major July 9, 2026

Some services and datastores in Singapore experiencing brief disruptions

Detected by Pingoru
Jul 09, 2026, 06:18 PM UTC
Resolved
Jul 09, 2026, 06:44 PM UTC
Duration
26m
Affected: Web ServicesCron JobsBackground WorkersPostgreSQLRedisWeb Services - Free Tier
Timeline · 2 updates
  1. monitoring Jul 09, 2026, 06:18 PM UTC

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

  2. resolved Jul 09, 2026, 06:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 2, 2026

Delayed wildcard issuance or renewal

Detected by Pingoru
Jul 02, 2026, 07:09 PM UTC
Resolved
Jul 02, 2026, 07:59 PM UTC
Duration
50m
Affected: Custom Domains
Timeline · 2 updates
  1. 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.

  2. resolved Jul 02, 2026, 07:59 PM UTC

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

Read the full incident report →

Minor June 23, 2026

External connections to Postgres services may terminate intermittently

Detected by Pingoru
Jun 23, 2026, 11:59 PM UTC
Resolved
Jun 24, 2026, 01:45 AM UTC
Duration
1h 45m
Affected: PostgreSQLPostgreSQLPostgreSQLPostgreSQLPostgreSQL
Timeline · 4 updates
  1. investigating Jun 24, 2026, 12:00 AM UTC

    We are currently investigating this issue.

  2. 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.

  3. monitoring Jun 24, 2026, 01:44 AM UTC

    We are continuing to monitor for any further issues.

  4. 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.

Read the full incident report →

Minor June 18, 2026

Slow/failing wildcard certificates related to LetsEncrypt incident

Detected by Pingoru
Jun 18, 2026, 09:06 PM UTC
Resolved
Jun 19, 2026, 12:17 AM UTC
Duration
3h 11m
Affected: Custom Domains
Timeline · 3 updates
  1. 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.

  2. monitoring Jun 18, 2026, 11:15 PM UTC

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

  3. 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.

Read the full incident report →

Minor June 11, 2026

Stuck queued deploys

Detected by Pingoru
Jun 11, 2026, 07:42 PM UTC
Resolved
Jun 11, 2026, 08:32 PM UTC
Duration
49m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
  1. investigating Jun 11, 2026, 07:42 PM 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 "Wait"

  2. monitoring Jun 11, 2026, 07:59 PM UTC

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

  3. resolved Jun 11, 2026, 08:32 PM 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.

Read the full incident report →

Minor June 11, 2026

Failed or delayed autodeploys

Detected by Pingoru
Jun 11, 2026, 06:56 PM UTC
Resolved
Jun 11, 2026, 07:17 PM UTC
Duration
21m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
  1. investigating Jun 11, 2026, 06:56 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 11, 2026, 07:06 PM UTC

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

  3. resolved Jun 11, 2026, 07:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

Queued deploys stuck

Detected by Pingoru
Jun 11, 2026, 04:01 PM UTC
Resolved
Jun 11, 2026, 06:12 PM UTC
Duration
2h 10m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
  1. identified Jun 11, 2026, 04:01 PM UTC

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

  2. identified Jun 11, 2026, 04:44 PM 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 Deploy Policy back to "Wait"

  3. resolved Jun 11, 2026, 06:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

Platform latency

Detected by Pingoru
Jun 11, 2026, 02:37 PM UTC
Resolved
Jun 11, 2026, 02:57 PM UTC
Duration
19m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
  1. investigating Jun 11, 2026, 02:37 PM UTC

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

  2. monitoring Jun 11, 2026, 02:56 PM 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 Jun 11, 2026, 02:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026

Delayed/missing autodeploys

Detected by Pingoru
Jun 09, 2026, 08:01 PM UTC
Resolved
Jun 09, 2026, 09:09 PM UTC
Duration
1h 8m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 3 updates
  1. investigating Jun 09, 2026, 08:01 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 09, 2026, 08:55 PM UTC

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

  3. resolved Jun 09, 2026, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 5, 2026

Issues with GitHub connections

Detected by Pingoru
Jun 05, 2026, 04:21 PM UTC
Resolved
Jun 05, 2026, 05:14 PM UTC
Duration
53m
Timeline · 3 updates
  1. investigating Jun 05, 2026, 04:21 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 05, 2026, 04:48 PM UTC

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

  3. resolved Jun 05, 2026, 05:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 4, 2026

Emails, including notifications, are delayed

Detected by Pingoru
Jun 04, 2026, 11:27 PM UTC
Resolved
Jun 05, 2026, 12:39 AM UTC
Duration
1h 11m
Affected: Render Dashboard
Timeline · 4 updates
  1. investigating Jun 04, 2026, 11:27 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 04, 2026, 11:38 PM 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 Jun 04, 2026, 11:43 PM UTC

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

  4. resolved Jun 05, 2026, 12:39 AM UTC

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

Read the full incident report →

Major June 1, 2026

Unable to load metrics for some services in Oregon

Detected by Pingoru
Jun 01, 2026, 09:25 PM UTC
Resolved
Jun 01, 2026, 09:45 PM UTC
Duration
20m
Affected: Metrics/Logs
Timeline · 3 updates
  1. investigating Jun 01, 2026, 09:25 PM UTC

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

  2. monitoring Jun 01, 2026, 09:32 PM UTC

    We're seeing recovery and are monitoring.

  3. resolved Jun 01, 2026, 09:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 22, 2026

Upstream provider outage causing delays provisioning custom domains

Detected by Pingoru
May 22, 2026, 03:53 PM UTC
Resolved
May 22, 2026, 04:37 PM UTC
Duration
44m
Affected: Custom Domains
Timeline · 3 updates
  1. investigating May 22, 2026, 03:53 PM UTC

    We are currently investigating this issue.

  2. monitoring May 22, 2026, 04:25 PM UTC

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

  3. resolved May 22, 2026, 04:37 PM UTC

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

Read the full incident report →

Minor May 20, 2026

Investigating Intermittent Postgres Connectivity Issues in the Oregon Region

Detected by Pingoru
May 20, 2026, 06:01 PM UTC
Resolved
May 20, 2026, 06:57 PM UTC
Duration
55m
Affected: PostgreSQL
Timeline · 4 updates
  1. investigating May 20, 2026, 06:01 PM UTC

    We are currently investigating this issue.

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

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

  3. monitoring May 20, 2026, 06:23 PM UTC

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

  4. resolved May 20, 2026, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 12, 2026

Logs unavailable for some services in all regions

Detected by Pingoru
May 12, 2026, 10:29 PM UTC
Resolved
May 12, 2026, 08:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 12, 2026, 10:29 PM 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.

Read the full incident report →

Major May 8, 2026

Certificate issuance paused for Let's Encrypt

Detected by Pingoru
May 08, 2026, 08:22 PM UTC
Resolved
May 08, 2026, 09:06 PM UTC
Duration
44m
Affected: Custom Domains
Timeline · 2 updates
  1. monitoring May 08, 2026, 08:22 PM 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 May 08, 2026, 09:06 PM UTC

    Let's Encrypt has resumed certificate issuance.

Read the full incident report →

Major May 7, 2026

HA Postgres Unavailability

Detected by Pingoru
May 07, 2026, 02:00 AM UTC
Resolved
May 07, 2026, 02:54 AM UTC
Duration
53m
Affected: PostgreSQLPostgreSQLPostgreSQLPostgreSQLPostgreSQLWorkflowsWorkflowsWorkflowsWorkflowsWorkflows
Timeline · 8 updates
  1. investigating May 07, 2026, 02:00 AM 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 May 07, 2026, 02:01 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 07, 2026, 02:07 AM UTC

    We are continuing to investigate this issue.

  4. identified May 07, 2026, 02:21 AM UTC

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

  5. identified May 07, 2026, 02:34 AM UTC

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

  6. identified May 07, 2026, 02:38 AM UTC

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

  7. identified May 07, 2026, 02:47 AM 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 May 07, 2026, 02:54 AM 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.

Read the full incident report →

Minor April 23, 2026

Delayed deployment for new services in Oregon region

Detected by Pingoru
Apr 23, 2026, 04:51 PM UTC
Resolved
Apr 23, 2026, 05:21 PM UTC
Duration
30m
Affected: Web Services
Timeline · 4 updates
  1. investigating Apr 23, 2026, 05:10 PM UTC

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

  2. identified Apr 23, 2026, 05:11 PM UTC

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

  3. monitoring Apr 23, 2026, 05:12 PM UTC

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

  4. resolved Apr 23, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →