4 months ago
[CHECK-WM] Error: TypeError: fetch failed } at async d (.next/server/chunks/[root-of-the-server]__d2decd15..js:1:2197) } at async u (.next/server/chunks/[root-of-the-server]__d2decd15..js:1:7403) at async l (.next/server/chunks/[root-of-the-server]__d2decd15..js:1:8444) at async Module.b (.next/server/chunks/[root-of-the-server]__d2decd15..js:1:9522) { [cause]: Error [ConnectTimeoutError]: Connect Timeout Error (attempted addresses: 151.101.194.133:443, 151.101.66.133:443, 151.101.2.133:443, 151.101.130.133:443, timeout: 10000ms) at ignore-listed frames { code: 'UND_ERR_CONNECT_TIMEOUT' ⨯ TypeError: fetch failed at async i (.next/server/chunks/[root-of-the-server]__602d8324..js:1:1634) at async u (.next/server/chunks/[root-of-the-server]__602d8324..js:1:5472) at async d (.next/server/chunks/[root-of-the-server]__602d8324..js:1:6513) at async Module. (.next/server/chunks/[root-of-the-server]__602d8324._.js:1:7591) { [cause]: Error [ConnectTimeoutError]: Connect Timeout Error (attempted addresses: 76.223.78.9:443, 13.248.186.2:443, timeout: 10000ms) at ignore-listed frames { code: 'UND_ERR_CONNECT_TIMEOUT' } } can u cerate support ticket it woas working today.
- Project ID: 9b142b80-7968-46f1-a03d-802409e95a9c
- Environment: production
- Issue: External HTTPS fetch timeouts to multiple CDNs (Fastly, AWS CloudFront)
- IPs failing: 151.101.x.x, 76.223.78.9, 13.248.186.2
- Status: Was working today, started failing recently
- IPv6 egress: Already enabled, didn't fix it
- Impact: Production outage, all external API calls timing out
3 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
The issue is with Railway:
" Issues with outbound networking
Investigating We are currently investigating failures to reach the internet for a subset of deployments"
4 months ago
I had to move my project to the GCP e2 server because of this problem
How can we make sure problems like this won't happen again? Is there any guarantees, can I host business automations here or railaway is mostly for hobby?
24 days ago
We're aware of intermittent outbound connectivity drops affecting some services, where outbound connections fail while internal networking and DNS keep working, and we're actively investigating. If you hit it, the quickest workaround is to redeploy, which moves your service onto a fresh host and restores connectivity. If it happens again, reply here with the rough time it started and we'll jump on it while it's live. Those real-time reports are exactly what help us track down the cause.
Status changed to Awaiting User Response angelo-railway • 24 days ago
17 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 • 17 days ago