Every deployment of my service fails at "Build > Build Image" after

almost exactly 7 seconds. The Build Logs tab is completely empty apart

from a single line:

Failed to connect before the deadline

No Nix output, no package install output, no output of any kind -- the

builder fails before it starts building. Railway's own Diagnose feature

also returns "Diagnosis failed for this deployment."

TIMELINE (all UTC)

2026-08-18 17:14 last SUCCESSFUL build, same repo, same config

2026-08-18 21:45 incident 7M7CBL9X opened ("Deployments are slow

                 to progress")

2026-08-18 21:57 my first failed build <-- inside the incident window

2026-08-18 22:40 incident 7M7CBL9X marked RESOLVED

2026-08-19 05:40 failed again (deployment 101a3258)

2026-08-19 05:44 failed again (deployment 82341c9d)

2026-08-19 06:35 failed again -- 5th consecutive failure

WHY I'M POSTING

My first failure is clearly explained by incident 7M7CBL9X. But the

incident has been resolved for ~8 hours and my builds still fail in

exactly the same way. I already followed the advice given to other

affected users in this forum ("retry once the incident is resolved") --

it did not help.

The failure takes almost exactly 7 seconds every single time, which

looks deterministic rather than like residual slowness. That makes me

suspect my service is stuck in a bad state left over from the incident,

rather than still being affected by it.

WHY IT'S NOT MY CODE

• Build config unchanged since the last successful build

• The only commits since then touch two Python files unrelated to the

  build (an application module and a test file) -- no dependency,

  Dockerfile or config changes

• The build produces zero output, so my code is never even read

• The previously deployed container is still running and healthy

SETUP

Builder: Nixpacks

Root Directory: a subdirectory of the repo

Plan: Trial (credit remaining, not exhausted)

Note: I found two other reports of the identical failure (empty build

log + "failed to connect before the deadline") in the same window, one

of them on Railpack rather than Nixpacks -- so this does not appear to

be builder-specific.

QUESTION

Is there residual impact from 7M7CBL9X, or is my service stuck in a

state that needs to be cleared on your side? Since the build log is

completely empty I have no way to diagnose this myself.