Render Outage History

Render is up right now

There were 17 Render outages since February 3, 2026 totaling 107h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.render.com

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 →

Minor April 14, 2026

BitBucket account connection issues

Detected by Pingoru
Apr 14, 2026, 02:31 PM UTC
Resolved
Apr 14, 2026, 04:04 PM UTC
Duration
1h 33m
Affected: Render Dashboard
Timeline · 3 updates
  1. investigating Apr 14, 2026, 02:31 PM 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 Apr 14, 2026, 03:12 PM UTC

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

  3. resolved Apr 14, 2026, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 13, 2026

Image pull failures in Oregon

Detected by Pingoru
Apr 13, 2026, 10:03 PM UTC
Resolved
Apr 13, 2026, 10:26 PM UTC
Duration
23m
Affected: Builds and Deploys
Timeline · 3 updates
  1. identified Apr 13, 2026, 10:03 PM UTC

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

  2. monitoring Apr 13, 2026, 10:18 PM UTC

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

  3. resolved Apr 13, 2026, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 10, 2026

Infrastructure maintenance operations are currently in progress for outbound IPs in the Oregon region

Detected by Pingoru
Apr 10, 2026, 02:41 PM UTC
Resolved
Apr 10, 2026, 02:56 PM UTC
Duration
15m
Timeline · 2 updates
  1. investigating Apr 10, 2026, 02:41 PM 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 Apr 10, 2026, 02:56 PM UTC

    The maintenance has been completed successfully.

Read the full incident report →

Minor April 8, 2026

Delays in stateful service creation in Oregon

Detected by Pingoru
Apr 08, 2026, 07:17 PM UTC
Resolved
Apr 08, 2026, 12:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 08, 2026, 07:17 PM 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.

Read the full incident report →

Major April 8, 2026

Disruption affecting the provisioning of new instances in Singapore and partially in Oregon

Detected by Pingoru
Apr 08, 2026, 09:57 AM UTC
Resolved
Apr 08, 2026, 10:11 PM UTC
Duration
12h 14m
Affected: Web ServicesWeb ServicesCron JobsCron JobsBackground WorkersBackground WorkersBuilds and DeploysBuilds and DeploysWeb Services - Free TierWeb Services - Free Tier
Timeline · 13 updates
  1. investigating Apr 08, 2026, 09:57 AM 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 Apr 08, 2026, 10:31 AM UTC

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

  3. investigating Apr 08, 2026, 10:54 AM 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 Apr 08, 2026, 11:22 AM UTC

    We are continuing to investigate this issue.

  5. identified Apr 08, 2026, 11:23 AM UTC

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

  6. identified Apr 08, 2026, 02:42 PM 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 Apr 08, 2026, 03:02 PM UTC

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

  8. monitoring Apr 08, 2026, 03:02 PM UTC

    We're seeing recovery across all regions.

  9. monitoring Apr 08, 2026, 04:05 PM UTC

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

  10. monitoring Apr 08, 2026, 06:08 PM UTC

    We are continuing to monitor for any further issues.

  11. monitoring Apr 08, 2026, 06:48 PM 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 Apr 08, 2026, 07:44 PM 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 Apr 08, 2026, 10:11 PM UTC

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

Read the full incident report →

Minor April 7, 2026

Unable to view workflows in the Dashboard

Detected by Pingoru
Apr 07, 2026, 07:33 PM UTC
Resolved
Apr 07, 2026, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 07, 2026, 07:33 PM 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.

Read the full incident report →

Minor March 25, 2026

Some Render Workflows tasks are not being scheduled

Detected by Pingoru
Mar 25, 2026, 02:45 PM UTC
Resolved
Mar 26, 2026, 07:51 PM UTC
Duration
1d 5h
Affected: Workflows
Timeline · 5 updates
  1. investigating Mar 25, 2026, 02:45 PM UTC

    We are working on resolving the issue.

  2. identified Mar 25, 2026, 04:40 PM 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 Mar 26, 2026, 05:54 PM UTC

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

  4. resolved Mar 26, 2026, 07:51 PM UTC

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

  5. postmortem Apr 14, 2026, 01:23 PM UTC

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

Read the full incident report →

Minor March 24, 2026

Some users may experience delayed logs in the Oregon region

Detected by Pingoru
Mar 24, 2026, 01:09 PM UTC
Resolved
Mar 24, 2026, 01:31 PM UTC
Duration
22m
Affected: Metrics/Logs
Timeline · 3 updates
  1. identified Mar 24, 2026, 01:09 PM UTC

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

  2. monitoring Mar 24, 2026, 01:12 PM UTC

    We are monitoring recovery.

  3. resolved Mar 24, 2026, 01:31 PM UTC

    The issue is fixed.

Read the full incident report →

Minor March 13, 2026

Degraded builds and deployments in the Singapore region

Detected by Pingoru
Mar 13, 2026, 03:51 PM UTC
Resolved
Mar 13, 2026, 06:07 PM UTC
Duration
2h 15m
Affected: Builds and Deploys
Timeline · 3 updates
  1. investigating Mar 13, 2026, 03:51 PM 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 Mar 13, 2026, 03:53 PM UTC

    We are currently monitoring.

  3. resolved Mar 13, 2026, 06:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 9, 2026

Custom domains are unable to be created

Detected by Pingoru
Mar 09, 2026, 08:19 PM UTC
Resolved
Mar 09, 2026, 08:39 PM UTC
Duration
20m
Affected: Custom Domains
Timeline · 2 updates
  1. investigating Mar 09, 2026, 08:19 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 09, 2026, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 3, 2026

Ohio Services with Disks, Data Persistence failing

Detected by Pingoru
Mar 03, 2026, 12:41 AM UTC
Resolved
Mar 03, 2026, 01:00 AM UTC
Duration
19m
Affected: Web ServicesBackground WorkersPostgreSQLRedis
Timeline · 3 updates
  1. identified Mar 03, 2026, 12:41 AM UTC

    Services located in Ohio, both application types (Web Service, Private Service, etc.) and data types (Postgres, Key Value with persistence) are failing due to disk errors. We are working on mitigations.

  2. identified Mar 03, 2026, 12:59 AM UTC

    Many services have recovered with healthy disks on new hosts, however this issue remains open as some services are still impaired.

  3. resolved Mar 03, 2026, 01:00 AM UTC

    All affected services have been migrated to new hosts and are running at this time. This incident has been resolved.

Read the full incident report →

Major February 11, 2026

Some deploys may be slow or hanging

Detected by Pingoru
Feb 11, 2026, 04:16 PM UTC
Resolved
Feb 11, 2026, 07:25 PM UTC
Duration
3h 8m
Affected: Builds and DeploysBuilds and DeploysBuilds and DeploysBuilds and DeploysBuilds and Deploys
Timeline · 5 updates
  1. investigating Feb 11, 2026, 04:16 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 11, 2026, 04:39 PM UTC

    We have implemented a mitigation and are currently observing positive results. We are continuing to monitor deploy health across the platform.

  3. identified Feb 11, 2026, 06:24 PM UTC

    Deploy delays and failures continue to remain elevated. We are continuing to work on this issue.

  4. monitoring Feb 11, 2026, 07:15 PM UTC

    Deploy times have decreased and failures have dropped to baseline levels. We are monitoring for other impacts or other issues.

  5. resolved Feb 11, 2026, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 4, 2026

Elevated latency for some new services when using the onrender.com address

Detected by Pingoru
Feb 04, 2026, 05:13 PM UTC
Resolved
Feb 04, 2026, 06:42 PM UTC
Duration
1h 29m
Affected: Web ServicesWeb ServicesWeb ServicesWeb ServicesWeb ServicesStatic SitesWeb Services - Free TierWeb Services - Free TierWeb Services - Free TierWeb Services - Free TierWeb Services - Free Tier
Timeline · 4 updates
  1. investigating Feb 04, 2026, 05:13 PM UTC

    We are currently investigating this issue.

  2. identified Feb 04, 2026, 05:21 PM UTC

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

  3. identified Feb 04, 2026, 05:29 PM UTC

    We have determined that services are reachable through their onrender.com address. Requests will be successful but may take longer. We are continuing to work on a fix.

  4. resolved Feb 04, 2026, 06:42 PM UTC

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

Read the full incident report →

Minor February 3, 2026

Degraded deploys in Ohio and Virginia

Detected by Pingoru
Feb 03, 2026, 03:30 PM UTC
Resolved
Feb 05, 2026, 10:36 PM UTC
Duration
2d 7h
Affected: Builds and DeploysBuilds and Deploys
Timeline · 5 updates
  1. investigating Feb 03, 2026, 11:05 PM UTC

    Deploys are experiencing degraded performance and may take longer to complete.

  2. monitoring Feb 03, 2026, 11:58 PM UTC

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

  3. monitoring Feb 04, 2026, 07:04 PM UTC

    We are observing improved deploy performance and continue to monitor for any further issues.

  4. monitoring Feb 04, 2026, 09:34 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 05, 2026, 10:36 PM UTC

    We implemented updates to builds and deploys to improve handling of slow updates. As a result of these changes, build and deploy performance has recovered.

Read the full incident report →

Minor February 3, 2026

Degraded Deploys in Singapore Region

Detected by Pingoru
Feb 03, 2026, 10:32 AM UTC
Resolved
Feb 03, 2026, 11:09 AM UTC
Duration
36m
Affected: Builds and Deploys
Timeline · 3 updates
  1. investigating Feb 03, 2026, 10:32 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 03, 2026, 10:49 AM UTC

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

  3. resolved Feb 03, 2026, 11:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Render downtime and outages?

Pingoru polls Render's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Render reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Render alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Render for free

5 free monitors · No credit card required