down
Is Render down?
Check Render availability, incident history, downtime reports, and website performance.
https://render.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Render
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-11 04:06:49 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Render outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Render website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-11 03:21:35 UTC.
Checked address: https://render.com/
DNS lookup: 116 ms · TCP connection: 2 ms · TLS handshake: 12 ms. Certificate expires 2026-12-18; trusted connection: yes.
100%
Successful website checks (24h)
21 successful / 21 measurable checks
150 ms
Median response time
382 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Render official status · fetched 2026-11-11 04:06:49 UTC
62 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Render Dashboard | operational |
| Web Services | operational |
| Web Services | operational |
| Web Services | operational |
| Web Services | operational |
| Web Services | operational |
| Render Website | operational |
| Cron Jobs | operational |
| Cron Jobs | operational |
| Cron Jobs | operational |
| Cron Jobs | operational |
| Cron Jobs | operational |
| Render Platform API | operational |
| Background Workers | operational |
| Background Workers | operational |
| Background Workers | operational |
| Background Workers | operational |
| Background Workers | operational |
| Builds and Deploys | operational |
| Builds and Deploys | operational |
| Builds and Deploys | operational |
| Builds and Deploys | operational |
| Builds and Deploys | operational |
| Render REST API | operational |
| Static Sites | operational |
| PostgreSQL | operational |
| PostgreSQL | operational |
| PostgreSQL | operational |
| PostgreSQL | operational |
| PostgreSQL | operational |
| Redis | operational |
| Redis | operational |
| Redis | operational |
| Redis | operational |
| Custom Domains | operational |
| Redis | operational |
| Web Services - Free Tier | operational |
| Web Services - Free Tier | operational |
| Web Services - Free Tier | operational |
| Web Services - Free Tier | operational |
| Web Services - Free Tier | operational |
| One-Off Jobs | operational |
| Oregon | operational |
| Autoscaling | operational |
| Autoscaling | operational |
| Autoscaling | operational |
| Autoscaling | operational |
| Autoscaling | operational |
| Frankfurt | operational |
| Metrics/Logs | operational |
| Metrics/Logs | operational |
| Metrics/Logs | operational |
| Metrics/Logs | operational |
| Metrics/Logs | operational |
| Ohio | operational |
| Workflows | operational |
| Workflows | operational |
| Workflows | operational |
| Workflows | operational |
| Workflows | operational |
| Singapore | operational |
| Virginia | operational |
Official incident timeline
Issues affecting connections to a subset of Postgres Databases · resolved · 2026-11-05T23:56:11.027Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · identified
A configuration change was rolled out to a small subset of Postgres instances. The change causes 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 will remediate the connection failures. If you do not see any issues in your connections, no corrective action is needed. If you need help remediating, please reach out to Render support and we can take corrective action.
Platform emails not being sent · resolved · 2026-10-24T07:41:10.448Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We have applied a fix and see messages successfully delivering. We are monitoring for any further issues.
- · 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.
Degraded network performance · resolved · 2026-10-23T17:34:12.960Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
We are continuing to work on a fix for this issue.
- · identified
We are continuing to work on a fix for this issue.
- · identified
We have identified degraded networking performance linked to an upstream provider - we will continue to provide updates here.
Deploying from GitLab may intermittently fail · resolved · 2026-10-21T00:29:02.786Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
We are continuing to work on a fix for this issue.
- · identified
We are continuing to work on a fix for this issue.
- · identified
The issue has been identified and a fix is being implemented.
- · 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.
Dashboard not updating in real time; Some Workflows SDK requests timing out · resolved · 2026-10-16T01:15:01.509Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
Our upstream provider has resolved the issue, and affected Render services have recovered. We’re continuing to monitor.
- · 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 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/{t
Builds, deploys, and queued deploys are not starting in all regions · postmortem · 2026-10-22T18:20:35.826Z
Product match: components.
Read the provider’s incident report
- · 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 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
- · resolved
This incident has been resolved.
- · 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.
- · 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.
- · identified
The issue has been identified and a fix is being implemented.
- · monitoring
We are temporarily pausing deploys to free services.
- · monitoring
We are continuing to monitor for any further issues.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
The issue has been identified and a fix is being implemented.
- · investigating
We are currently investigating this issue.
Degraded Dashboard Performance; Degraded builds & deploys in Oregon · resolved · 2026-10-03T20:21:29.613Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
Impacted components are recovering. We are monitoring the situation.
- · investigating
We are continuing to investigate this issue.
- · investigating
We are currently investigating this issue.
Observing service instability from our upstream provider AWS in Oregon region · resolved · 2026-09-27T03:01:11.916Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
All services, except for the free web services tier, have recovered. We continue to monitor.
- · monitoring
Our upstream provider has begun recovering. Services in Oregon are improving, and we're continuing to monitor.
- · investigating
We are currently investigating this issue.
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: 150 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Render.
No active incidents recorded.
- Changes to Cloudflare Workers are not producing Event Subscription events · investigating
- Fedramp Customers have Delayed Purges · identified
About Render status on Iszdown
Check Render availability, incident history, downtime reports, and website performance.
This page combines the available Render report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
62 product-matched official components are listed above. Latest public website measurement: 2026-11-11T03:21:35.000Z.
Visit the official Render website · Official provider status · How it works
What to check when Render is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Render will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Render is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Render outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Issues affecting connections to a subset of Postgres Databases | 224 min | resolved | |
| Degraded network performance | 88 min | resolved | |
| Deploying from GitLab may intermittently fail | 221 min | resolved | |
| Dashboard not updating in real time; Some Workflows SDK requests timing out | 95 min | resolved | |
| Builds, deploys, and queued deploys are not starting in all regions | 165 min | postmortem | |
| Degraded Dashboard Performance; Degraded builds & deploys in Oregon | 46 min | resolved | |
| Observing service instability from our upstream provider AWS in Oregon region | 97 min | resolved | |
| Build and deploy failures in Oregon | 12 min | resolved |
Frequently asked questions about Render
Is Render down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T04:08:30.000Z.
How many Render outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Render show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Render feature.
When was Render status last updated?
The latest status observation was 2026-11-11T04:06:49.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Render had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Render or report a problem?
Use “Watch this service” to save Render in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Render
Check a related product separately; its status can differ from Render.