Still issue persist not resolved.

Can you elaborate on “white screen”?

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.

The intermittent white screen on deployment — where a restart or adding a blank space to trigger a redeploy fixes it — is a classic symptom of a stale/frozen build cache serving outdated assets, combined with the ongoing Railway build infrastructure recovery from the GCP outage.

Here is what is happening and how to fix it:

Root cause: cached build artifacts being served instead of fresh ones

When Railway serves a white screen but a redeploy fixes it, the build likely completed with a stale cached chunk — old JS/CSS bundles are referenced in the HTML but the actual files are from a different build hash, causing the browser to load a blank page.

Immediate fix: disable build cache

Set this environment variable in your Railway service settings:

NIXPACKS_NO_CACHE=1

or if you're using Railpack:

RAILPACK_NO_CACHE=1

This forces a clean build every time and eliminates stale cache artifacts causing mismatched asset hashes.

For React/Next.js/Vite frontends specifically:

Make sure your build output includes a cache-busting hash in filenames (e.g. main.abc123.js) and that your index.html is never cached by the browser. Add these headers in your Railway service or web server config:

Cache-Control: no-cache, no-store, must-revalidate  (for index.html only)
Cache-Control: public, max-age=31536000, immutable  (for hashed static assets)

Why it happens intermittently:

During the current Railway build incident recovery, build machines under high load may partially use cached layers from a previous build, producing inconsistent bundles. Disabling the cache and doing a clean redeploy should stabilize this.

Could you share what framework/build tool you're using? That would help pinpoint if there's a more specific configuration needed.