WebRTC works as fallback. WebRTC is encrypted and cant be used for much else.

STUN in the otherhand is unencrypted and the protocol itself can be used for DDoS reflection/amplification. I would not be surprised if this is somehow weaponized and/or blocked/analyzed in real time that then breaks the connectivity.

It's just something so heartwarming of multiple people coming together to describe their symptoms, workarounds and theories of what could be causing it.

We have kids complaining online about 40ms ping on their video games, and right down the kids are online complaining about how they're being hunted for sport.

Maybe they need a few average devs there to spend time sweeping up behind the paragons that are pushing the envelope into these features existing at all.

Looks like they tracked it to a steam update in March, and there's a workaround for at lest 3 games that involves all players copying steamwebrtc.dll to the game's ./binaries folder.

It's been kept around because they treat their customers ok, but they absolutely exsanguinate their developers.

And their engineering culture is... odd. They hire senior people and then let them all fuck sound aimlessly. Their APIs are terrible, their infrastructure is all over the place, they still have patch Tuesdays. But because they are the landlord that owns every house in town, what are you going to do, not pay rent?

Gabe is out there cruising the world in a billion dollar yacht, eating thousand dollar meals. All that came off the backs of developers who actually make the games.