Railway - Notice history

Dashboard - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025
100% - uptime

Builders - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 99.97%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Image Registry - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 99.98%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Deploy - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Third-Party: npm Registry - Operational

Third-Party: Github Integrations - Operational

Third Party: Docker Hub - Operational

Third-Party: GitHub Container Registry - Operational

100% - uptime

EU West (europe-west4 / Amsterdam, Netherlands) - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

US East (us-east4 / Virginia, USA) - Operational

100% - uptime
Dec 2024 · 99.95%Jan 2025 · 99.96%Feb · 99.99%
Dec 2024
Jan 2025
Feb 2025

US West (us-west1 / Oregon, USA) - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 99.98%
Dec 2024
Jan 2025
Feb 2025

Southeast Asia (asia-southeast1 / Singapore) - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025
100% - uptime

US West (us-west1 / Oregon, USA) - Operational

100% - uptime
Dec 2024 · 99.95%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

US East (us-east4 / Virginia, USA) - Operational

100% - uptime
Dec 2024 · 99.95%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

EU West (europe-west4 / Amsterdam, Netherlands) - Operational

100% - uptime
Dec 2024 · 99.95%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Southeast Asia (asia-southeast1 / Singapore) - Operational

100% - uptime
Dec 2024 · 99.95%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

TCP Proxy - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025
100% - uptime

DNS - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Traffic - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025
100% - uptime

Logs - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Metrics - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 99.99%
Dec 2024
Jan 2025
Feb 2025
100% - uptime

Payments - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Notice history

Feb 2025

TCP Proxy Upgrades
  • Completed
    February 15, 2025 at 2:00 AM
    Completed
    February 15, 2025 at 2:00 AM
    Maintenance has completed successfully
  • In progress
    February 14, 2025 at 11:00 PM
    In progress
    February 14, 2025 at 11:00 PM
    Maintenance is now in progress
  • Update
    February 14, 2025 at 11:00 PM
    Planned
    February 14, 2025 at 11:00 PM

    We will be provisioning more domains for TCP Proxy allocations. During this time the new domain may not proxy traffic while the global TCP Proxy system picks up these changes. We expect this window to only be a few minutes.

    All existing TCP Proxy domains will continue to work. Connections may be closed due to reloads though and reconnecting will work. This is expected behaviour whenever we have pushed updates to this service in the past.

    These changes will allow us to live reload more configs in the future, minimizing the needs for "hard reloads" which may drop connections. We recommend people use the private network when possible, for which this is a non-issue.

  • Planned
    February 14, 2025 at 9:44 PM
    Planned
    February 14, 2025 at 9:44 PM

    A note; this will only, potentially, affect services which are dialing a Railway database from OUTSIDE Railway, via the TCP proxy (viaduct.rlwy.net, monorail.rwly.net, etc)

    Private network connections (myservice.railway.internal) will be unaffected

Jan 2025

Dec 2024

Dec 2024 to Feb 2025

Next