3 months ago
Issue:
Application logs show "[Errno -3] Temporary failure in name resolution" at:
- 08:36:36–08:37:00 UTC
- 08:58:30–08:58:37 UTC
During these windows, every outbound HTTPS call failed (getaddrinfo could not
resolve ANY hostname), and Railway's edge proxy returned HTTP 502 "upstream error"
for inbound requests to BOTH our frontend and backend services at the same time.
Ruling out our app:
- No restart: no SIGTERM / startup / "Started server process" in logs.
- CPU normal, memory flat (~156 MB) — no OOM.
- Both independent external APIs failed in the same 2 seconds → not the APIs.
This points to a host/container-level networking/DNS interruption on Railway's side.
Details:
- Project ID: a84bad25-9964-4329-b141-5a056c8c0423
- Backend service ID: e6b58a01-95b3-4406-8f18-f8bc74f658a6
- Deployment ID: 5549317d-58c6-4998-9fda-406696170e4b
- Replica ID: 459ad00c-e007-4bd8-9b78-dca468fe1771
- Edge region: zrh1 (Zurich)
- Impact: ~7-second full outage of a live production site.
Question:
Was there a networking/DNS incident affecting this host/region at these times?
What mitigation prevents recurrence?
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
There was a major edge network incident on July 2 from 07:44 to 12:01 UTC involving elevated latency and packet loss, tracked at this status page entry. Your DNS resolution failures at 08:36 UTC and 08:58 UTC fall within that window, and the symptoms you describe (502s on inbound traffic, failed outbound DNS for both services simultaneously) are consistent with the impact. A post-mortem covering root cause and preventive measures will be published once ready.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago