a month ago
Project ID: 4039ee2e-05f6-4946-a1e8-b3fb6c0ae947
Service: ddq-assistant
Domain: ddq-assistant.com
Current deployment ID: da4a7560-2551-4dc8-bceb-6349b55d0ef8
Stale instance still receiving traffic: 6d658eab-3836-4385-97fa-71b3709932a3
Timeline: Plan upgraded ~15:30 UTC, service became inaccessible, restart did not fix it
This is a load balancer registration bug triggered by the plan upgrade—the proxy is stuck routing to a stale container instance that no longer exists. This requires:
Manual load balancer re-registration to point to the current deployment instance
Or a rollback of the plan upgrade to restore the previous working state
Pinned Solution
a month ago
Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Also, Cloudflare currently has an incident related to certificates so it may or may not be causing this issue. (https://new.cloudflarestatus.com/incidents/j17t8xz91xs0)
1 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Also, Cloudflare currently has an incident related to certificates so it may or may not be causing this issue. (https://new.cloudflarestatus.com/incidents/j17t8xz91xs0)
Status changed to Solved 0x5b62656e5d • about 1 month ago