Thanks for reaching out. We sincerely apologize for the service disruption.

We're seeing recovery in our API, builds, and deployments. If your service is experiencing an issue, please try redeploying it. We'll publish a public postmortem once we're fully recovered.

For all customers, we’ll publish a detailed postmortem outlining what happened and the steps we’re taking to prevent similar incidents in the future. For Enterprise customers, service credits are covered under our SLA and will be reviewed as part of our post-incident process.

Looks like they aren't even giving credits for this extended downtime. If you are using railway for business I would suggest you look elsewhere.

Thanks for confirming recovery — my app is back online.

I understand SLA service credits are reserved for Enterprise plans.

However, I'm not raising an SLA claim. I'm raising a billing-fairness

issue:

During the incident, your own dashboard's recovery path (Restart) was

broken, and I was pushed to use the billable Railway Agent to recover

my production database. It consumed over $3 of my $5 monthly credit.

The Agent also nearly triggered a destructive cross-region migration

that would have wiped my production volume — I had to manually catch

and reverse it.

I would never have spent that credit if your infrastructure had been

working. Charging me for it is not fair.

I'm formally requesting a refund of the Agent usage consumed during

this incident (May 19-20 outage). This is independent of any SLA

discussion.

Separately — while I understand downtime credits are Enterprise-only,

I'd genuinely appreciate any goodwill gesture for a 10+ hour

production outage on a paid account. I run a live marketplace and

this was a hard hit.

Please confirm the Agent refund. Thank you.

You can request a refund by following the docs at https://docs.railway.com/reference/pricing/refunds#requesting-a-refund