Outbound TCP port 443 blocked from container - all external API calls timing out
rileycrane
HOBBYOP

2 months ago

All outbound HTTPS connections from my container have been failing since ~06:40 UTC on 2026-03-15. DNS resolution works fine (1ms), but TCP connections to port 443 time out for every external host -- Google APIs, httpbin.org, Backblaze S3, PyPI.

This also breaks builds (uv sync can't reach pypi.org to resolve hatchling).

Region: US (Fastly edge in San Francisco)

Diagnostic evidence (from an endpoint I added to test this):

{

"dns": {

"places.googleapis.com": "192.178.156.95",

"time_ms": 1

},

"tcp_connect": {

"error": "",

"type": "TimeoutError"

},

"google_places": {

"error": "",

"type": "ConnectTimeout"

},

"httpbin": {

"error": "",

"type": "ConnectTimeout"

}

}

DNS resolves instantly, but raw TCP open_connection to port 443 times out. This affects every external service (Google Places, Anthropic, Twilio, Stripe, Backblaze).

The app was working fine at 23:20 UTC on 2026-03-14 (successful outbound Vapi calls logged). The issue started during a deploy cycle around 06:40 UTC on 2026-03-15. I've tried multiple redeploys and fresh containers -- same result every time.

Inbound traffic works fine (the app serves HTTP requests). Only outbound is broken.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


2 months ago

Heya, apologies for the delay, we've called an incident here: https://status.railway.com/cmmrjwx4x0ltkf6zwi526b038 and a fix is rolling out


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...