thank you for responding!
if you mean from end user side, then yep - could be reprod both from one device (where we put several streams running when trying to debug this - after adding more than 5, some of the streams started to get stuck) as well as from around 20-30 end-users who were in different networks (and ISPs) in the same country - who were all running just a single instance of the stream to their own device
near as i can tell from documentation and publicly available info, it shouldnt be a p2p sharing issue as well even though webrtc is generally meant to be that sort of thing, but it looks like for cloudflare stream product, cf network and servers do the heavy lifting, so to speak, and given the beefy hardware and network (and extremely small amount of people being streamed to) involved, this shouldnt be a product limitation - especially since we even tried pulling the resolution down to 720p, but that didnt make much of.a difference either
though since everyone is in the same country, most probably everyone is using the cf datacentre in tallinn, estonia, both for ingress and egress - but id like to imagine that shouldnt make much of a difference
so im trying to understand what might be happening, and if we can get around this issue - is there any way to enable metrics and logging? by default theyre disabled and couldnt find a way to enable them - figured its because its technically in beta as a product, but perhaps theres away regardless
in browser inspector we occasionally get 404 for get request to stream url/key, but that happens even when stream is running fine, so it probably handles occasional cuts just fine, but at some point it gets stuck and page needs to be reloaded
