Q4 is here and we’re rolling! As we head into the final stretch of the year, the team has been busy laying the foundation for a strong finish.

This week for us was mainly focused on planning— sharpening our focus and setting the stage for what’s ahead. If you’re curious how we think about it, check out our latest post on 

why most product planning is bad (and what to do about it)

Next week, we’ll be shifting gears at our biannual company retreat, where the Railway crew comes together in person to align, jam, and recharge. That means things may be a little quieter on the feature front, but plenty is brewing behind the scenes.

Of course, planning week doesn’t mean the shipping stops — we’re introducing HTTP metrics for your services for better observability and have rolled out improvements that make working with buckets smoother.

HTTP service metrics to Priority Boarding

Service “Metrics” tab now displays HTTP metrics

On Railway, observability isn’t an afterthought, it’s built into the core of the platform. We’re shipping dashboards designed to surface the truth instantly: is your system humming along, or is something off?
Today we bring you a new addition to the metrics tab for your service: 

In addition to the existing views for CPU, Memory and Public Network Traffic, you’ll be able to view the following metrics:

Response time over time, shown as latency percentiles (p50, p90, p95, p99).

Number of HTTP responses over time, broken down by status code category (2xx, 4xx, 5xx)

This way if something is going wrong, you'll be able to quickly identify the source of the issue. 

If you run into any issues or want to share your thoughts, jump into the discussion 

Bulk add bucket secrets to a service in one click

, making it simple to connect your bucket to other services without hardcoding values. You can reference shared variables, other services’ variables, or even variables within the same service using Railway’s template syntax.

We’ve also streamlined the process of adding bucket variables to other services — now it’s just a single click:

From there, you’ll pick the target service and the SDK you’re using to interact with your bucket.

Object Storage is available in Priority Boarding

. To get started, simply right-click in your project canvas and select 

If you hit any snags or have feedback, join the conversation in this 

This quarter is all about sharpening the core of Railway while unlocking new capabilities for teams with higher security and compliance needs. On the horizon, you can expect:

 connect Railway to your existing identity provider for seamless access.

 full visibility into actions across your org, with traceability of who did what and when.

Security and compliance-focused features like:

These initiatives are aimed at giving you greater confidence, flexibility, and control over your workloads. There’s plenty to build — and we’re excited to get after it. 

feedback and feature requests on Central Station

Thanks for being on the ride with us 🚄. See you next week!

We shipped a couple of fixes to Buckets, including resolving glitches in groups and ensuring they now appear in collapsed groups

We shipped an improvement to the railway.com/dashboard page to show loading skeletons, giving you a smoother and more seamless experience

We shipped an improvement to the command palette on the deploy template page — you’ll now see a loading spinner while templates are being fetched. Before, the lack of any loading state made it feel like things were stuck or broken, but this should make the experience much smoother.

https://res.cloudinary.com/railway/image/upload/v1759513829/2025-10-03_i6nuqx.png

Changelog #0258