PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Railway is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Railway. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Railway issues today?

As of Sep 26, 2026 04:07 UTC, 0 users had reported issues with Railway in the previous 24 hours.

How can I report a Railway outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Railway down right now?

NormalOfficial status last polled Sep 26, 2026 04:05 UTCrailway.app Official status page

Railway deployment platform, databases, networking, dashboard, and infrastructure availability.

Are you on the Railway team and see something inaccurate? Report it to us. We respond within one business day.

Is Railway down right now?

No. Railway has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 26, 2026 04:07 UTC

Normal

Railway is operating normally

As of Sep 26, 2026 04:07 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

May 4, 2026 20:33 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Railway.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Railway. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Railway outage on May 4 — 19-minute disruption

May 4, 08:13 PM → May 4, 08:33 PM · 19 minutes · medium

The Railway service experienced an outage beginning on May 4, 2026, at 20:13 UTC. This disruption was detected through user reports. Service was fully restored on May 4, 2026, at 20:33 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

19 minutes

until recovery

Impact

Users reported issues with the Railway service, leading to the detection of this outage. A peak of 4 user reports were received within a 15-minute period. No specific issue types or geographical regions were predominantly identified among the reports. The incident resulted in a 19-minute period of service disruption for affected users.

Outage timeline

May 4, 08:13 PM
PulseWatch detected elevated report volume (medium severity)
May 4, 08:15 PM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 4, 08:33 PM
Report volume returned to baseline — incident resolved

Official updates

May 4, 08:13 PM
Railway status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.99%

Calculated from Railway's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.