Railway incident

Some users might not be able to log in.

Resolved after 1 hour 4 minutes, affecting Railway (Dashboard — railway.com), on February 13, 2026.

monitoring Feb 13, 2026, 01:22 AM UTC

We implemented a fix and are currently monitoring the result. We're seeing recovery on queued deployments as well.

Started
Feb 13, 2026, 01:00 AM UTC
Resolved
Feb 13, 2026, 02:05 AM UTC
Duration
1h 4m
Detected by Pingoru
Feb 13, 2026, 01:00 AM UTC

Affected components

Railway (Dashboard — railway.com)

Update timeline

  1. investigating Feb 13, 2026, 01:00 AM UTC

    We are currently investigating this incident. All running services are fully operational, only login is affected.

  2. identified Feb 13, 2026, 01:12 AM UTC

    A Redis shard on the Dashboard is timing out. A subset of users may see dashboard timeouts

  3. monitoring Feb 13, 2026, 01:22 AM UTC

    We implemented a fix and are currently monitoring the result. We're seeing recovery on queued deployments as well.

  4. resolved Feb 13, 2026, 02:05 AM UTC

    This incident has been resolved.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →