Railway deployment very slow amid ongoing incident
jackwelty
HOBBYOP

a month ago

Seeing ~15s response times on all requests to my deployment, including endpoints that do zero I/O (auth rejection returns 401 but takes 15s). This started ~75 minutes ago per Sentry.

Health endpoint returning 502 through Cloudflare due to timeout, also ~15s when hit directly.

Single uvicorn worker, no recent deploys. Suspect this is related to the current platform incident even though it's listed as builds-only.

Cloudflare:

curl -I https://caucus-ai.com/health

HTTP/2 502

date: Wed, 18 Feb 2026 03:58:16 GMT

content-type: text/plain; charset=UTF-8

content-length: 15

cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0

expires: Thu, 01 Jan 1970 00:00:01 GMT

referrer-policy: same-origin

x-frame-options: SAMEORIGIN

server: cloudflare

cf-ray: 9cfa9a87590aba52-SEA

alt-svc: h3=":443"; ma=86400

1 Replies

jackwelty
HOBBYOP

a month ago

If the incident is affecting live deployments, please update the status page accordingly. Presently it just says it's affecting builds, which is very misleading if it's affecting uptime for services that didn't have a deployment.


Loading...