2,188 karma · joined July 1, 2009
• Previously engineer #5 and (later) Head of Risk at Stripe
This is obviously overzealous abuse management, and we will fix our systems so this kind of thing never happens to legitimate users.
To OP and others who may have been affected, I'm deeply sorry.
We know developers don't actually care who's at fault and will move off of Render if we're down, period. Even before the incident, we'd started working on a project to eliminate the SPOF with Cloudflare, and now it's only a matter of time before we ship it.
Yes. While Cloudflare is generally rock solid, we can't let this happen again.
Everything is back up. We're waiting for Cloudflare's RCA and will follow up with additional Render context right after.
------------
(Render CEO) While Cloudflare investigates the issue on their end, we're also working on ways to bypass Cloudflare.
Really sorry about this, folks. We'll keep https://status.render.com updated and will post an RCA once things calm down.
Cloudflare have declared an incident at https://www.cloudflarestatus.com/incidents/2xffnv666yd7.
In case you're wondering, we use Cloudflare to keep Render's network up during DDoS attacks. Both Render and our customers are often targeted. We've already started building a product that lets customers bypass Cloudflare altogether, and I expect we'll see more demand for it after today's incident.
The vast, vast majority of commercial deployments are single region, as evidenced by the occasional failure of us-east1.
At runtime, Render mounts your secret file at `/etc/secrets/FILENAME` in your container. Your application can then read it like any other file on the local filesystem.
Of course, you can always store your secrets in Render environment variables and use them via ENV statements at runtime.
However, to this day, Netlify's static site product remains ahead of Render, and we haven't invested as heavily in it as other products in our portfolio. Why? Because static site hosting is now a commoditized market, and we can differentiate ourselves better elsewhere. Netlify sees this too and is changing course accordingly (based on bobfunk/Matt's comment above). I know they will be successful, and they deserve all the good things that come their way because they've materially advanced web development over the last several years (even inspiring ZEIT to pivot into Next.js+Vercel).
Jared: I think your beef might actually be with serverless compute and the restrictions that come with it, especially when vendors try to force it down developers' throats as the only way to build apps. The A in JAM can (and often should) be a long running server instead of a thin Lambda shim, but Netlify is a lot less guilty of pushing this narrative compared to their peers.
A PaaS (depending on scope) can easily be the most complicated thing to build in the cloud, so the more building blocks you have, the better.
With Render, I'd rather show than tell. As an interesting data point, we've now existed as an independent entity longer than Heroku did, and we're truly just getting started.
We're looking for great people to join our team! See render.com/careers for all open roles.
(I work there)
If the market is big enough to support AWS/GCP/Azure as $N00B businesses each, it’s not a leap to imagine a future where both Fly and Render are incredibly successful, loved, and independent businesses spanning decades. Let's keep at it.
I'm very explicit both internally and externally that an acquisition is a failure mode for Render. We're building this for the very long term and plan to keep it that way.
The team charge assigns a nominal value to the productivity boost Render gives to teams, without increasing compute prices (which stayed the same even with the change). Existing single-seat teams also got a 6-month grace period for team fees.
While our change means we're not the cheapest option on the market, we believe the DX and features we have (and will continue to add) makes Render an incredibly good deal, both now and over the long term.
This is only true for the free tier, and (hopefully) won't be true for much longer.