---
title: Metrics
description: Discover resource usage for your services on Railway via the Metrics tab.
---
Railway provides resource usage information on deployments within a service, which can be used to diagnose issues with a project's performance.

## How it works

For each service, Railway captures metric data. These metrics are then made available in graphs within a service's panel, under the metrics tab.

## Accessing service metrics

Access a service's metrics by clicking on a service in the project canvas, and going to the "Metrics" tab.

<Image src="https://res.cloudinary.com/railway/image/upload/v1758559063/docs/metrics-sum_tvdwlc.png"
alt="Screenshot of Metrics Page"
layout="intrinsic"
width={1576} height={1100} quality={80} />

## Provided metrics

The following metrics are provided:

- **CPU** - Processor usage
- **Memory** - RAM consumption
- **Disk Usage** - Storage utilization
- **Network** - Inbound and outbound traffic

Application-level metrics such as request latency, error rates, or business KPIs are not collected by Railway. To capture these, ship telemetry to a third-party tool. See [Connect a Third-Party Observability Tool](/guides/third-party-observability) for the vendor SDK and OpenTelemetry options.

## Understanding the metrics graphs

Graphs include dotted lines to indicate when new deployments began. Up to 30 days of data is available for each project.

<Image src="https://res.cloudinary.com/railway/image/upload/v1645223703/docs/usage-commit_fkvbqj.png"
alt="Screenshot of Metric Timeseries Commit Information"
layout="responsive"
width={904} height={726} quality={80} />

Projects maintain a continuous time-series for all deployments within a service, not just the latest one. Deployments appear on the graph so users can see which commit may have caused a spike in resources.

## Metrics with multiple replicas

When a service runs multiple [replicas](/deployments/scaling#horizontal-scaling-with-replicas), you can view metrics in two ways: **Sum** or **Replica**.

_Note: Public network traffic metrics are only available in the Sum view._

### Sum view

<Image src="https://res.cloudinary.com/railway/image/upload/v1758559063/docs/metrics-sum_tvdwlc.png"
alt="Viewing the sum of all replica metrics"
layout="intrinsic"
width={1576} height={1100} quality={80} />

In **Sum** view, metrics from all replicas are combined. For example, if you have two replicas using 100 MB of memory each, the metrics tab will show 200 MB.

### Replica view

<Image src="https://res.cloudinary.com/railway/image/upload/v1758559063/docs/metrics-per-replica_skc17b.png"
alt="Viewing metrics of individual replicas"
layout="intrinsic"
width={1576} height={1100} quality={80} />

In **Replica** view, you can see metrics for each replica individually. This is useful for diagnosing issues with specific replicas or spotting if some regions are under- or overutilized.

The total from all replicas may differ slightly from the Sum view due to rounding or overlapping instances during zero-downtime deployments.

## Troubleshooting

Having issues understanding your metrics? Check out the [Troubleshooting guide](/troubleshooting) or reach out on the <a href="https://discord.gg/railway" target="_blank">Railway Discord</a>.