Subject: NPM Cache Corruption After Docker Build Cloud Outage - Service

f9f1ed6a-fefd-4996-98c2-01834adb0725

Hello Railway Support Team,

We're experiencing a critical deployment issue that appears to be related to

the Docker Build Cloud outage that occurred earlier today (October 20, 2025).

Issue:

All deployments for our Next.js application are failing during the npm install

phase with exit code 1. The builds consistently fail after ~400ms at the npm ci

step.

Service Details:

- Service ID: f9f1ed6a-fefd-4996-98c2-01834adb0725

- Project: Bloffee.com-mg

- Repository: https://github.com/Dries1971/Bloffee.com-mg

- Branch: production

- Last successful deployment: a6f41f25 (October 14, 2025)

- Current failing commit: 8c45c83

Error from Build Logs:

RUN --mount=type=cache,id=s/f9f1ed6a-fefd-4996-98c2-01834adb0725-/root/npm,targ

et=/root/.npm npm ci --legacy-peer-deps

ERROR: failed to build: failed to solve: process "/bin/bash -ol pipefail -c npm

ci --legacy-peer-deps" did not complete successfully: exit code: 1

What We've Tried:

- npm install without package-lock.json

- npm cache clean --force

- Restoring a known working package-lock.json

- Multiple redeploy attempts

- Different npm install strategies

Root Cause:

We believe the npm cache mount (cache ID:

s/f9f1ed6a-fefd-4996-98c2-01834adb0725-/root/npm) became corrupted during

today's Docker Build Cloud outage.

Request:

Could you please manually clear the build cache for our service? We have

critical business landing pages that need to be deployed.

Question:

Is there a way to disable or bypass the cache mount temporarily so we can

complete this deployment?

Thank you for your assistance.