Render down? The answer is at the top of this page. Appys checks Render’s official status page as you arrive, so what you see is never more than a few minutes old. Below is what to check on your side, what to do while you wait, and how to hear when it’s fixed.
Render down for everyone, or just you?
If the status above says Render is working normally but it isn’t working for you, the problem is most likely closer to home. Press Is it just me? at the top of the page: your own device and our server both try to reach render.com, and the answer tells you which side the problem is on.
Then try these quick checks:
- Open Render on another network, such as mobile data instead of Wi-Fi.
- Try a different browser or a private window, to rule out an old cache or a browser extension.
- Restart your router if lots of websites are slow, not just this one.
- Make sure your device’s date and time are set automatically: a wrong clock can stop secure connections.
- If you build on it, look at your own logs and dashboard too: an error from your own server or code can look just like an outage.
Render down? What to do while you wait
- Check which part is affected. Render splits its status into 10 parts, listed under What Render reports on above, so a problem in one may not touch the ones you use.
- Hold off on big changes. Deploys, settings changes and DNS edits made during an outage can fail halfway and be hard to undo.
- Retry rather than rebuild. Most outages are fixed on the provider’s side, so reinstalling or reconfiguring rarely helps.
- Tell your own users. A short note saying the problem is with Render, with a link to this page, saves a pile of support messages.
- Keep this page open: the status changes by itself when Render posts the fix, so there’s no need to keep refreshing.
If it drags on and the work can’t wait, the alternatives near the top of this page are other app hosting services that are working right now.
Why apps like Render go down
Most outages at developer platforms start with a change: a new release, a configuration change or a network route that goes wrong. Even big outages are often partial, hitting one feature, one region or one group of users rather than everyone. That’s why Render can work fine for you while its status page reports a problem, or the other way round.
How Appys checks Render
Every status on this page comes from Render’s official status page, where Render’s own team posts problems and fixes. Its status page covers 10 parts: Render Dashboard, Render Website, Render Platform API, Render REST API, Static Sites, Custom Domains, One-Off Jobs, Oregon, Frankfurt and Ohio. Appys reads it whenever someone opens this page and regularly in between, keeps a record of every problem it posts and works out the 90-day uptime from that record. We never change what Render says, and nobody can pay to change a status or a record.
A quiet status page doesn’t always mean nothing is wrong: some companies post small problems late, or not at all. That’s why this page also shows how openly Render reports its problems.
How long do Render outages last?
It depends on what broke. Small problems are often fixed within the hour, while a big outage can take most of a day. The history above lists every problem Render has posted recently, when each one started and how long it took to fix, so you can see what’s normal for Render rather than guessing. While a problem is open, the latest update from Render is shown at the top of this page.
About Render
Cloud hosting for web apps, APIs and databases.
On Appys it’s listed under Developer tools and hosting, with the other app hosting services we follow.
Hear when Render is back
Send one email to [email protected] with Watch Render in the subject and we’ll email you when Render reports a major outage, and again when it’s fixed. You can also follow its problems in a feed reader or a Slack channel, or add a live badge to your own site; both are explained above.
Spotted Render down? Share this page so other people can check too. This is the picture they’ll see:
