2 days ago
Hello.
We have a production service on Railway:
https://lingerie-ai-bot-production.up.railway.app
Endpoint:
POST /api/payments/robokassa/result
Our payment provider Robokassa reports that their ResultURL callback for a real payment timed out while waiting for HTTP response. They did not receive any HTTP status code.
Robokassa RF callback IP ranges:
185.59.216.65
185.59.217.65
Incident:
InvId: 173
Endpoint:
https://lingerie-ai-bot-production.up.railway.app/api/payments/robokassa/result
Approximate time:
2026-07-05 16:33–16:37 GMT+3
What we observe:
- Manual GET to /api/payments/robokassa/result reached Railway and returned HTTP 400 in ~26 ms.
- Manual POST to /api/payments/robokassa/result reached Railway and returned HTTP 400 in ~32 ms.
- The backend logged the test requests correctly.
- However, the real Robokassa POST callback for InvId=173 is not visible in Railway HTTP Logs.
- Robokassa says their timeout occurred while waiting for HTTP response, with no HTTP status received.
Could you please check whether incoming HTTPS POST requests from Robokassa IPs 185.59.216.65 / 185.59.217.65 were blocked, filtered, timed out, or failed at Railway edge/proxy level around that time?
We need to know whether the request reached Railway edge, whether it was forwarded to the service, and whether there were TCP/TLS/backend response timeout issues.
1 Replies
2 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 days ago
a day ago
Update: the issue reproduced with a new real payment.
InvId=175
Amount: 350 RUB
Method: SBP
Payment was actually paid, fiscal receipt was issued.
Robokassa notification log shows 4 POST attempts to:
https://lingerie-ai-bot-production.up.railway.app/api/payments/robokassa/result
Times:
Jul 6 08:09 GMT+3
Jul 6 08:10 GMT+3
Jul 6 08:11 GMT+3
Jul 6 08:12 GMT+3
All attempts failed with:
"The operation has timed out"
Our app created the payment successfully:
Robokassa payment created: user=8093793456, package=rub_350, method=sbp, inv_id=175
But our backend logs do not show:
robokassa_result_received: inv_id=175
Manual POST tests to the same endpoint reach the backend quickly and return the expected bad signature response.
Could you please check whether incoming HTTPS POST requests from Robokassa reach Railway edge/proxy at all, and whether they are blocked, timed out, or not forwarded to the container?
Robokassa IP ranges:
185.59.216.65
185.59.217.65