Hello to those of you reading this changelog with your brand new 

To the rest of you, please put on whatever ski, swim, chemistry, woodworking, or mountaineering goggles you might have lying around the house — we wouldn’t want you to feel left out.

The show is about to begin, we wish you a pleasant journey. 

Templates now provide more information about health and deployment numbers

A template is a fully configured project that’s meant to work out of the box … but what if it doesn’t work? 

We’re busy making tools to increase the trustworthiness and reliability of templates. In particular, we’ve recently added a health score to each template that takes into account recent successful or unsuccessful deployments.

We’ve also made it more clear how popular the template is and what you’ll be getting from the template. Best of all, this is all available now within the command palette (⌘ + K) in the Railway application.

We have lots more planned for templates soon. 

 in payouts awarded to template creators through the 

That’s what we experienced during the peak of a DDoS attack directed at us this past week.

As a cloud platform with a rapidly growing user base, we’re unfortunately a target for some occasional bad actors. This past week we experienced a number of sophisticated DDoS attacks that caused production outages for some users. 

These attacks were extreme in nature and although they resulted in some downtime (and lots of time spent hardening some things instead of shipping new features this past week), we think the 

We hope you’ll take a chance to read about how we treat events like these — it’s our policy always to share the public details of what occurred.

Want to learn about some of the fine Product Engineers and Designers bringing you Railway? 

We’re rolling out a new blog series this week to do just that.

 to learn about one of the most important teams at Railway — the Product Engineering team! 

We hope you enjoy a little bit of an inside look at how we operate. If you like what you read, 

Due to the DDoS events this past week, we’ve extended the final Plugin deprecation date to 

If you do not migrate before then, your running plugins will be archived for 6 months, after which they will be permanently deleted. 

Locked plugins (stopped because they ran out of credits) will 

 be archived. They will be deleted permanently on February 23, 2024. 

For full timeline and details, check out the 

We fixed an issue where connections on internal private networks would “blip”

We improved a number of automated emails around usage limits and failed build notifications

We fixed a bug in which deleted services would sometimes appear in Staged Changes

We fixed an issue where team members sometimes couldn’t edit templates

https://res.cloudinary.com/railway/image/upload/v1706926677/2024-0202_csieqz.png

Template Health, DDoS Event, Product Engineering Spotlight, Plugin Deprecation

Changelog #0171