gazhay
PROOP
2 months ago
Currently experiencing problems with egress.
All fetches are timing out to host api.zwiftracing.app
project 6a6c4123-f4c9-4c41-ba5f-c3115ddc1753
They have confirmed there is no rate-limiting at their end, but it seems our deployment is just not resolving the host at all.
9 Replies
2 months ago
Worth noting that this service is also hosted on Railway.
It seems to be routing issues
2 months ago
Just pointing it out in case any team members come along to assist. It's possible that Railway does different routing for egress that comes back into Railway, and it could be causing issues.
2 months ago
i.e. this could be a Railway problem and not just a buggy third-party service.
Sorry, wrong url above, seems it is routing (now)
(To exit, press Ctrl+C again or Ctrl+D or type .exit)
> fetch("https://api.zwiftracing.app").then(a=>console.log(a));
Promise {
,
[Symbol(async_id_symbol)]: 360,
[Symbol(trigger_async_id_symbol)]: 359
}
> Response {
status: 404,
statusText: 'Not Found',
headers: Headers {
'access-control-allow-origin': '*',
'content-length': '139',
'content-security-policy': "default-src 'none'",
'content-type': 'text/html; charset=utf-8',
'cross-origin-opener-policy': 'same-origin',
'cross-origin-resource-policy': 'same-origin',
date: 'Tue, 06 Jan 2026 23:19:54 GMT',
'origin-agent-cluster': '?1',
'referrer-policy': 'no-referrer',
server: 'railway-edge',
'strict-transport-security': 'max-age=15552000; includeSubDomains',
'x-content-type-options': 'nosniff',
'x-dns-prefetch-control': 'off',
'x-download-options': 'noopen',
'x-frame-options': 'SAMEORIGIN',
'x-permitted-cross-domain-policies': 'none',
'x-railway-edge': 'railway/europe-west4-drams3a',
'x-railway-request-id': 'BJMPCrUHTmm66k0NjUJq2g',
'x-xss-protection': '0'
},
body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true },
bodyUsed: false,
ok: false,
redirected: false,
type: 'basic',
url: 'https://api.zwiftracing.app/'
}