Hello Railway Team,

I’m reaching out regarding the recent CDN incident you reported, where cached GET responses were incorrectly served across different users.

Unfortunately, my platform was among the affected (~0.05%), and I was alerted by multiple users experiencing highly concerning behavior — specifically, being logged into other users’ accounts or seeing data that did not belong to them.

At the time, this appeared to be a critical flaw in my own system, and I spent several hours investigating what I believed to be a severe backend or authentication issue. Only later did your notification clarify that the root cause was on the CDN layer.

While I understand that incidents can happen, this particular issue represents a serious breach of user isolation and trust. The fact that user-specific responses were served to other users introduces significant security implications, regardless of the scale or duration.

Even though the overall impact on my platform was limited, this situation caused:

• Loss of time and resources spent investigating a non-existent internal issue
• Reputational risk and user confusion due to account/session inconsistencies
• Exposure of user-specific data

Given the severity and nature of this incident, I would like to request appropriate compensation, such as service credits or other forms of account adjustment.

I value Railway as a platform and appreciate your transparency in reporting the issue. However, incidents involving cross-user data exposure are critical by nature, and I believe a gesture of compensation would be appropriate in this case.

Thank you for your time, and I look forward to your response.

Best regards,

Strahinja Popovic from Balkanflix.