Hello,

We do support outbound UDP traffic, and any other kind of traffic for that matter, there are no limits on the protocol for outbound connections.

Perhaps you meant inbound? since we do not support inbound UDP traffic.

Best,

Brody

Yea, sorry! I mixed that up. Inbound UDP traffic

Feel free to update your title and message to correctly reflect your ask.

This would be great not only for WebRTC services but also for SRT streams. :)

I also want this feature.

Many hardware devices and sensors still don't support MQTT, so I want to receive them via UDP in the backend deployed on Railway because they can't go through IoT Core.

@brody are there any plans for this?

+1 - this would be awesome.

+1 for inbound UDP please!

I need this for my livekit self-hosting video calls, don't want to host another vps for this 😭

Yep, would love this. I was trying to stream SRT out to Mux, but I wasn't very familiar with the protocol and realized it won't work since we need to receive UDP acks from the server we're connecting to.

This would be nice for hosting Epic's new version control, Lore. https://epicgames.github.io/lore/how-to/deploy-local-lore-server/?h=udp#prerequisites

+1. This is extremely important especially for situations when you're designing software where TCP just can't be used and HTTP is not an option either.

+1, I want to host a TURN server and I need UDP so :3

if you want to host something like a livekit server I have been having some success building ephemeral compute boxes over api/sdk for digital ocean and Vultr. If you have rooms that are scheduled ahead of time, I just provision the compute at the scheduled time and tear them down after. The cost to run video chat is pretty minimal as long as you can keep the compute wall clock time down to just when the rooms are live. It would be nice to have all the infra in railway, but going ephemeral has made the cost of solutions like Vultr/DigitalOcean/Hertzer a viable option.