Multiple Railway-hosted applications are intermittently returning 403 Forbidden responses from Fastly's Singapore POP. The block occurs at the Fastly CDN edge layer before requests reach Railway origin servers.

Affected Services

• bishwasto-v2-frontend (bishwasto.com) — Next.js app, Netherlands region
• bishwasto_dev (api-dev.bishwasto.com) — Django app
• archiom-portfolio (archiom.io) — Next.js app (different project entirely)
• And more

Error Details

• HTTP Status: 403 Forbidden
• Error Code: 54113
• Varnish POP: cache-sin-wsat1880048-SIN (Singapore)
• Full error: Error 403 Forbidden — Forbidden — Error 54113 — Details: cache-sin-wsat1880048-SIN 1771663479 4089536354 — Varnish cache server

Behavior

• Intermittent: some requests pass through, others return 403 from the same browser
• Affects ALL Railway-hosted domains from the same network, confirming it's infrastructure-level
• Railway HTTP logs show the apps are online and responding normally — the 403 is generated at the Fastly edge before reaching origin
• Changing Railway deployment region from Singapore to Netherlands did not resolve the issue

Network Details

• Location: Bangladesh
• Affected: Multiple broadband ISPs (WiFi)
• Not affected: Mobile carrier networks (likely route through a different Fastly POP)
• VPN workaround: Confirmed working (bypasses the SIN POP)

Timestamps (GMT+6)

• First observed: Feb 21, 2026 ~2:30 PM
• Still ongoing as of ticket submission

Steps to Reproduce

1. From a Bangladesh broadband IP, visit any Railway-hosted domain (e.g., archiom.io)
2. Some requests return 403 from Varnish SIN POP, others pass through normally
3. Same browser, same URL — results vary per request due to Fastly load balancing across SIN nodes

Expected Resolution: This appears to be an issue with specific nodes in Fastly's Singapore POP incorrectly blocking legitimate traffic. Requesting escalation to Fastly to investigate the SIN POP nodes serving 403 responses.