Official Status
Official outage and maintenance updates for Render.
Live Domain Check
Check if Render is down right now (render.com). Run a live multi-region check to see whether Render is offline for everyone or just you.
Get official Render outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Render incidents often begin as partial failures before they become broader outages. You may see intermittent errors or feature-specific failures while other pages still load.
For Render, check API, build, and platform behavior. If results are mixed across regions, compare official sources with this checker before making account or infrastructure changes.
Use official sources first, then compare with the live probe results above to separate provider incidents from local route issues.
Official outage and maintenance updates for Render.
Directly test the official Render website entrypoint.
Official support resources for Render account and service issues.
Follow real-time social outage updates related to Render.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when render.com seems down. Use this checklist to confirm whether Render is down for everyone or only for you.
Run render.com in WebsiteDown.org first, then open render.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Render service status page and compare timestamps with your failed checks.
Test related hosts such as www.render.com, status.render.com. If they work while render.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for render.com, then share those details with Render support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Render seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open render.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on render.com. Avoid repeated password or security resets until you confirm this is not a broader Render issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Render support.
Run the automatic multi-region check on this page for render.com. If most regions fail together, it is likely a broader incident.
If only one or two regions fail, your local route is more likely the issue.
Use official status, support, and social links on this page first, then compare with live probe results.
Common causes include DNS resolver variance, ISP routing issues, VPN/proxy filters, stale sessions, and temporary rate limits.
Run the check, verify official updates, test another network, and capture exact error details before changing account settings.