Skip to content
Major Outage Effects
Anonymous
OP

a month ago

Dear Railway Support Team,

I am writing to formally request compensation for the financial losses I incurred as a result of Railway's recent 22-hour service outage.

During this extended disruption, my services were affected, resulting in a total estimated financial loss of $112.35 USD.

As a Railway customer, I rely on your platform to maintain reliable service availability. Unfortunately, an outage of this duration has significant consequences, particularly when applications and services depend on continuous uptime.

I would therefore like to request the following resolution:

Preferred resolution: Financial compensation of $112.35 USD to cover my documented losses resulting from the outage.

Alternative resolution: If direct monetary compensation is not possible under Railway's policies, I would be willing to accept $112.35 USD in Railway service credits or an equivalent paid-plan subscription offer.

I believe this is a reasonable request given the duration of the disruption and its financial impact.

I would appreciate it if your team could:

Review the outage and its impact on my services.

Consider my request for compensation or equivalent service credits.

Explain the available compensation options and expected resolution timeline.

I am happy to provide additional information or supporting documentation regarding the financial losses if necessary.

I value Railway's services and hope we can reach a fair and satisfactory resolution.

Thank you for your attention. I look forward to your response.

Best regards,

Railway Customer

Solved

6 Replies

Railway
BOT

a month ago

We looked at your services and can't tie the disruption you describe to a Railway-side incident affecting them. Your most recent deployments today are completing normally, apart from one that failed its healthcheck, which points to the application not answering its health check rather than a platform outage.


Status changed to Awaiting User Response Railway • 26 days ago


Railway

We looked at your services and can't tie the disruption you describe to a Railway-side incident affecting them. Your most recent deployments today are completing normally, apart from one that failed its healthcheck, which points to the application not answering its health check rather than a platform outage.

Anonymous
OP

a month ago

I was talking about the incident that took place between October 21-23. Here is the evidence: https://status.railway.com/incident/QH8L8B3E. During the builds and deployments were off, my services got disrupted, which eventually led to financial loss.


Status changed to Awaiting Railway Response Railway • 26 days ago


Railway
BOT

a month ago

Thanks for pointing us to the October 21-23 incident. On Trial, Hobby, and Pro plans, we don't offer financial compensation, service credits, or plan offers for platform incidents. Service credits for downtime are only part of Enterprise agreements that include a contractual SLA.

That means we can't grant the $112.35 or an equivalent credit. We're sorry we can't do more here.


Status changed to Awaiting User Response Railway • 26 days ago


Railway

Thanks for pointing us to the October 21-23 incident. On Trial, Hobby, and Pro plans, we don't offer financial compensation, service credits, or plan offers for platform incidents. Service credits for downtime are only part of Enterprise agreements that include a contractual SLA. That means we can't grant the $112.35 or an equivalent credit. We're sorry we can't do more here.

Anonymous
OP

a month ago

I want a real Railway worker to review my answer, as this automated bot doesn't understand the request properly!


Status changed to Awaiting Railway Response Railway • 26 days ago


Railway

Thanks for pointing us to the October 21-23 incident. On Trial, Hobby, and Pro plans, we don't offer financial compensation, service credits, or plan offers for platform incidents. Service credits for downtime are only part of Enterprise agreements that include a contractual SLA. That means we can't grant the $112.35 or an equivalent credit. We're sorry we can't do more here.

Anonymous
OP

a month ago

At least, can you provide a plan offer or credits, since our confidential tokens/keys were stolen and later decrypted during Railway's Read Team investigation?


Status changed to Awaiting Railway Response Railway • 26 days ago


dizzydes90
EMPLOYEE

25 days ago

Hi Qilichbek,

We're still working out how we'll handle service credits for the October 20-22 incident, and the earlier automated replies shouldn't have pointed at the Enterprise SLA as the reason: that policy is about downtime, and this was a security incident. No decision on credits has been made yet for any plan, and we'll reply on this thread once it has.

On your keys: we can't confirm from support which variables were read, and we don't share access logs. The access we identified was to stored environment variables, as described in the preliminary report: https://blog.railway.com/p/preliminary-report-october-security-incident. Treat every key that was stored in Railway variables as exposed and rotate it, and check each provider's usage logs for activity after October 21. The October 24 notice at https://status.railway.com/incident/8E4V5WLD covers keys that AI providers revoked as a precaution after that; those revocations don't mean your replacement keys were compromised.


Status changed to Awaiting User Response Railway • 25 days ago


Railway
BOT

18 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...