Description of the issue you're facing:

We're trying to use DataBento's live streaming API for real-time financial data in our trading application. DataBento uses port 13000 for live streaming connections, but Railway appears to be blocking outbound TCP connections to this port.

Error messages and descriptions:

TypeError: Connection does not support read-write operations

Authentication with equs-mini.lsg.databento.com:13000 timed out after 30.0 second(s)

Key Technical Details:

• Service: DataBento live streaming API
• Port: 13000 (TCP)
• Connection Method: DataBento Raw API (we don't specify host/port - DataBento handles internally)
• Works: Locally on our development machines
• Fails: On Railway cloud deployment
• DataBento Support Confirmed: "You do not need to specify the host/port when running the example" - they handle connection details internally

Logs:

INFO:databento.live.client:adding user callback handle_live_data

TypeError: Connection does not support read-write operations

Authentication with equs-mini.lsg.databento.com:13000 timed out after 30.0 second(s)

Code example:

# This is our exact implementation following DataBento's documentation

import databento as db

client = db.Live(api_key) # No host/port specified

for record in client: # DataBento internally connects to port 13000

process_data(record)

Questions:

1. Does Railway block outbound TCP connections to non-standard ports like 13000?
2. Is there a way to whitelist specific ports for outbound connections?
3. Are there any network policies that restrict live streaming data services?
4. Would upgrading to a higher Railway plan resolve this issue? Workaround Implemented: We've implemented a polling strategy using DataBento's historical API (port 443) as a workaround, but this reduces our data freshness from real-time to ~30 seconds.