A bug report filed against Valve's networking library says peer-to-peer connectivity has been broken for more than two months — and counting.
The issue was opened on Valve's GameNetworkingSockets repository on GitHub, where it documented an ongoing failure in the library's P2P networking layer. GameNetworkingSockets is Valve's open-source networking stack, used to handle Steam connections and made available to developers building multiplayer games on top of it. The report surfaced on Hacker News in early June, where it attracted modest attention — a sign the problem has been quietly affecting developers without generating much public pressure on Valve itself.
For multiplayer games that rely on P2P connections rather than dedicated servers, a broken networking layer isn't a minor inconvenience: it is the difference between a game that works and one that doesn't. Smaller studios often choose P2P architectures specifically to avoid the cost of running servers, which makes them more exposed to upstream breakage like this. A two-month window without a visible fix or official acknowledgment is a long time in software terms.
Valve publishes developer-facing infrastructure but doesn't always maintain a support posture to match. When a bug sits open for weeks in a critical library, the question isn't just whether a fix is coming — it's whether anyone with commit access is watching.