12 hours ago
Project ID: 57876869-2717-432f-ac5b-b022f9444a90 (KAH Platform)
Environment ID: 7a33ae8a-502e-4cd8-b438-c6b777899dca (staging)
Plan: Hobby (upgraded from Trial ~19:00-19:10 UTC, 2026-08-14)
Regions tested: sfo, iad — both fail
CONTROL TEST (decisive):
Service railway-scheduler-test 7374a5ff-74b9-469a-b32a-31162dfa6547
Image nginx:alpine — no repo, no build, no vars, no volume, no deps, 1 replica
Deployments: 75f6d21e (19:51 sfo), 5666b13b (19:55 iad), 68d1433f (19:55)
All QUEUED. Only SNAPSHOT_CODE completed. Zero further events.
BUILD-COMPLETES-BUT-NEVER-LAUNCHES:
rabbitmq 152f7d02: SNAPSHOT_CODE completed, BUILD_IMAGE completed,
PUBLISH_IMAGE completed (all 19:11:24) — CREATE_CONTAINER never started.
PIPELINE PREVIOUSLY WORKED ON THIS ACCOUNT:
keycloak a87bf355 (19:03) reached CREATE_CONTAINER + HEALTHCHECK.
FREEZE ONSET: ~19:05-19:09 UTC, correlating with Trial->Hobby upgrade.
Affected: rabbitmq 705f407c / keycloak b344705e / kah-web f2dac691 /
kah-internal-api 5669671b / kah-worker 2e1a7ade / kah-outbox-worker 9c62ce2d /
kah-event-consumer c3d3a5b1 / kah-beat e6975647
Request: force-clear stuck deployments and/or check whether this
workspace/project has a Limited Access or scheduler-pause flag set.
ADDITIONAL TIMING EVIDENCE:
My Stripe receipt for the Trial->Hobby upgrade is timestamped 19:00:49 UTC.
Deployment scheduling degraded within ~5 minutes of that payment and
stopped completely by ~19:08 UTC:
19:00:49 Stripe payment processed (Trial -> Hobby)
19:03-04 Still working — keycloak reached CREATE_CONTAINER + HEALTHCHECK,
kah-internal-api reached DEPLOYING19:05-09 Progress degrades, then halts
19:08+ Total freeze — nothing schedules in any region
Nothing in this environment has advanced past QUEUED since ~19:09 UTC.
1 Replies
Status changed to Awaiting Railway Response Railway • about 5 hours ago
5 hours ago
There are no deployments stuck in the queue on your workspace right now, and your Hobby plan is active with no restrictions. The deployment freeze after the upgrade has cleared. If anything is still not progressing on your side, redeploying one of the affected services should pick up normally.
Status changed to Awaiting User Response Railway • about 5 hours ago