Render Outage History

85 incidents recorded over the last 365 days, 82 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Render status98.69% uptime history

Every Recorded Render Incident

Render incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026Deployment IssuesThis incident has been resolved.3h 53mResolved
Jul 27, 2026Degraded dashboard performanceWe've continued to observe no further issues and deploy failure reasons have been re-enabled.28h 52mResolved
Jul 24, 2026Service Disruption in OregonThis incident has now been resolved.2h 14mResolved
Jul 20, 2026Degraded builds/deploys (all regions)Builds failure rates have recovered. Resolving.1h 29mResolved
Jul 19, 2026GitHub git clone 403 errorsThis incident has been resolved.5h 36mResolved
Jul 16, 2026GitHub outage affecting new service creation and service deploysThis incident has been resolved.1h 32mResolved
Jul 15, 2026Some users enrolled in 2FA are experiencing login issuesThis incident has been resolved.1h 5mResolved
Jul 15, 2026Render Dashboard UnavailableThis issue has been resolved.31 minResolved
Jul 9, 2026Some services and datastores in Singapore experiencing brief disruptionsThis incident has been resolved.26 minResolved
Jul 8, 2026Render Maintenance PeriodThe scheduled maintenance has been completed.1h 0mScheduled
Jul 2, 2026Delayed wildcard issuance or renewalIssuance has returned to expected performance and we've observed no further impact.50 minResolved
Jun 23, 2026External connections to Postgres services may terminate intermittentlyThis has now been resolved. Customers will have seen an impact from Jun 22, 2026, at 11:50 UTC.1h 45mResolved
Jun 18, 2026Slow/failing wildcard certificates related to LetsEncrypt incidentWe have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.3h 11mResolved
Jun 11, 2026Stuck queued deploysThis 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.49 minResolved
Jun 11, 2026Failed or delayed autodeploysThis incident has been resolved.21 minResolved
Jun 11, 2026Queued deploys stuckThis incident has been resolved.2h 10mResolved
Jun 11, 2026Platform latencyThis incident has been resolved.19 minResolved
Jun 9, 2026Delayed/missing autodeploysThis incident has been resolved.1h 8mResolved
Jun 5, 2026Issues with GitHub connectionsThis incident has been resolved.53 minResolved
Jun 4, 2026Emails, including notifications, are delayedOutstanding emails have been sent and processing has returned to expected operation.1h 11mResolved
Jun 1, 2026Unable to load metrics for some services in OregonThis incident has been resolved.20 minResolved
May 27, 2026Render Maintenance PeriodThe scheduled maintenance has been completed.1h 0mScheduled
May 22, 2026Upstream provider outage causing delays provisioning custom domainsOur upstream provider has resolved the issue and custom domain provisioning has recovered.44 minResolved
May 20, 2026Investigating Intermittent Postgres Connectivity Issues in the Oregon RegionThis incident has been resolved.55 minResolved
May 12, 2026Logs unavailable for some services in all regionsBetween 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.-149 minResolved
May 11, 2026Degraded builds/deploys (all regions)This incident has been resolved.11 minResolved
May 8, 2026Certificate issuance paused for Let's EncryptLet's Encrypt has resumed certificate issuance.44 minResolved
May 7, 2026HA Postgres UnavailabilityEverything 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.53 minResolved
Apr 23, 2026Delayed deployment for new services in Oregon regionThis incident has been resolved.30 minResolved
Apr 16, 2026Some web services and databases in Oregon are unresponsiveThis incident has been resolved.14 minResolved
Apr 14, 2026BitBucket account connection issuesThis incident has been resolved.1h 33mResolved
Apr 13, 2026Image pull failures in OregonThis incident has been resolved.23 minResolved
Apr 10, 2026Infrastructure maintenance operations are currently in progress for outbound IPs in the Oregon regionThe maintenance has been completed successfully.15 minResolved
Apr 8, 2026Delays in stateful service creation in OregonBetween 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.-407 minResolved
Apr 8, 2026Disruption affecting the provisioning of new instances in Singapore and partially in OregonWe've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.12h 14mResolved
Apr 7, 2026Unable to view workflows in the DashboardBetween 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.-93 minResolved
Mar 25, 2026Some Render Workflows tasks are not being scheduledAffected 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.29h 5mResolved
Mar 24, 2026Some users may experience delayed logs in the Oregon regionThe issue is fixed.22 minResolved
Mar 13, 2026Degraded builds and deployments in the Singapore regionThis incident has been resolved.2h 15mResolved
Mar 13, 2026Degraded builds and deployments in the Singapore regionWe believe this incident has been successfully mitigated. If you continue to experience any issues, please contact support@render.com.2h 17mResolved
Mar 9, 2026Custom domains are unable to be createdThis incident has been resolved.20 minResolved
Mar 9, 2026Urgent maintenance to build infra for some Oregon usersThe scheduled maintenance has been completed.1h 0mScheduled
Mar 3, 2026Ohio Services with Disks, Data Persistence failingAll affected services have been migrated to new hosts and are running at this time. This incident has been resolved.19 minResolved
Feb 11, 2026Some deploys may be slow or hangingThis incident has been resolved.3h 8mResolved
Feb 4, 2026Elevated latency for some new services when using the onrender.com addressLatency has returned to expected levels. Affected services were those created between 2026-02-04T16:30Z and 2026-02-04T18:17Z. Services created outside that period were not affected.1h 29mResolved
Feb 3, 2026Degraded deploys in Ohio and VirginiaWe implemented updates to builds and deploys to improve handling of slow updates. As a result of these changes, build and deploy performance has recovered.55h 6mResolved
Feb 3, 2026Degraded Deploys in Singapore RegionThis incident has been resolved.36 minResolved
Feb 2, 2026Degraded deploys in all regionsThis incident has been resolved.49 minResolved
Jan 30, 2026External connectivity issues with Postgres databases hosted in SingaporeThis incident has been resolved. Please reach out to support@render.com for any follow-up questions.57 minResolved
Jan 23, 2026Metrics impacted for some services in OregonThis incident has been resolved.56 minResolved
Jan 17, 2026Delays in starting instances on servicesInstance creation times have been restored to expected timerames. This issue has been resolved.12 minResolved
Jan 12, 2026Some application and build logs are missing on the dashboardThis incident has been resolved.5h 11mResolved
Jan 8, 2026Deploy delays in OregonThis incident has been resolved.2h 1mResolved
Dec 10, 2025Unable to view service eventsThis incident has been resolved.6 minResolved
Dec 10, 2025Deploy delays in VirginiaDeploy performance has returned to expected levels.27h 6mResolved
Dec 5, 2025Elevated Latency for Requests to Web Services and Static Sites in FrankfurtThis incident has been resolved.49 minResolved
Dec 5, 2025Services not accessibleFrom 08:47 to 09:11 UTC, all incoming web traffic in every region failed to reach services and returned 500 errors instead. Our dashboard and API were down too. Background workers, private services, and cron jobs were…35 minResolved
Dec 2, 2025Increased Latency in Updates to Oregon ServicesThis incident has been resolved.1h 37mResolved
Dec 2, 2025Custom Domains: New certificates stuck on pendingWe understand the issue is resolved now. If you're still seeing issues, please reach out.1h 27mResolved
Nov 25, 2025Web services (Oregon) and static sites availability disruptionThis incident has been resolved.13 minResolved
Nov 20, 2025Increased slowness in DashboardThe incident has been resolved.7h 29mResolved
Nov 20, 2025Elevated rates of deploy failuresThis incident has been resolved.2h 3mResolved
Nov 18, 2025GitHub-backed services failing to build in all regionsThis incident has been resolved.56 minResolved
Nov 18, 2025An upstream provider major incident is affecting some Render servicesWe have observed no further impact and the upstream provider has affirmed full resolution.6h 26mResolved
Nov 14, 2025Metrics/Logs missing for Oregon servicesThis incident has been resolved.23 minResolved
Nov 13, 2025Cron Job runs cannot be cancelled from our dashboard or the APIThis incident has been resolved.7h 20mResolved
Nov 5, 2025Increased 404s in Oregon (Web Services) and Static Sites# Summary As an infrastructure provider, providing a reliable platform that allows our customers to build and scale their applications with confidence is our highest obligation. We invest heavily to ensure our platform…2h 33mResolved
Oct 30, 2025Failure to spin free web services back up after inactivityBetween 2025-10-28 at 17:00 UTC and 2025-10-30 at 17:22 UTC, a change was active that caused some free web services to fail to spin back up after inactivity. Most free web services were unaffected. While the change was…-128 minResolved
Oct 28, 2025Degraded builds and deploys in VirginiaThis incident has been resolved.51 minResolved
Oct 23, 2025Pre-deploys are failing in some regionsThis incident has been resolved.1h 47mResolved
Oct 20, 2025An upstream provider is experiencing some issues that are affecting parts of our platform (Virginia)This incident has been resolved.13h 18mResolved
Oct 10, 2025Incorrect IP allowlists configured for new Environments created via REST APIChanges were deployed to fix the issue with new Environments created via the REST API. All affected Environments have been updated to be their default Allow-All if not otherwise specified in the API call's parameters…1h 43mResolved
Oct 7, 2025Increased latency in Oregon regionLatency has returned to baseline levels since 16:40 UTC and no further impact has been observed.41 minResolved
Oct 1, 2025Unable to create Postgres services or update their instance type in OregonThis incident has now been resolved. A subset of customers in Oregon, but not all, were impacted. Affected customers were unable to create Postgres services or update the instance type of Postgres services between…1h 0mResolved
Oct 1, 2025Partial degradation of service creation and deploys in OregonThis incident has been resolved.49 minResolved
Sep 25, 2025Image-based deploys failing due to upstream providerThis incident has been resolved.1h 28mResolved
Sep 23, 2025Dashboard operations degraded or failingDashboard operations were degraded for ~30 minutes, and within that period operations were mostly failing for ~5 mins.-2817 minResolved
Sep 23, 2025Small number of users impacted by stuck buildsThis incident has been resolved.71h 48mResolved
Sep 22, 2025Some Postgres databases can’t be created in FrankfurtThis incident has been resolved.1h 9mResolved
Sep 17, 2025Issues with deploys and spinning down free services in VirginiaBetween 20:35 UTC and 20:53 UTC today, a process was unavailable that is responsible for handling port detection and deploys that were waiting due to a workspace's overlapping deploy policy. Queued deploys will proceed…-73 minResolved
Sep 15, 2025Deploy failure when using some public repos from GitHubThis incident has been resolved.2h 35mResolved
Sep 15, 2025Failure to pull some images from GitHub Container RegistryWe no longer see elevated failure rates for images pulled from GitHub Container Registry. If the problem persists please contact GitHub or Render's support team.23h 45mResolved
Sep 11, 2025Some slack notifications failing August 1 - September 11We have completed monitoring our fix, and will publish an RCA attached to this incident.1h 3mResolved
Sep 9, 2025Builds and Deploys erroring on Oregon servicesThis incident has been resolved.30 minResolved
Aug 26, 2025Incorrect bandwidth billing data in the DashboardThis incident has been resolved.25h 12mResolved

How to Read This Render Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Render acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Render outage in this window ran 2d 23h, against a mean recovery of 4h 58m. If you depend on Render in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.