a month ago
Some users are experiencing timeouts where TCP connection succeeds but HTTP response never returns. Works fine for other users from same endpoint.
- Service: web (api.simmer.markets)
- Affected IP: 2604:a00:50:160:216:3eff:fe32:8f8 (IPv6)
- Symptom: 30-60s timeout on all endpoints, even unauthenticated
- Requests don't appear in our application logs
- Our tests from other IPs work fine (<3s response)
Is there IP-based filtering or routing issue at the edge?
2 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
I have been having what seems to be the same issue for weeks, no one from railway will reply. The requests dont appear in my logs but when/if they finally do, my app handles them in a few ms.
Sorry you are having this issue, railway just auto sets it to public and throws a bounty on it. Not sure if you use cloudflare proxy, but if you are, just toggle that off and back on, that gets me back going