Critical Incident Report

[brixxnatt]

Critical Incident Report

We have identified a serious issue affecting the stability streaming server . When two clients attempt to publish a live stream using the same stream key simultaneously—either by accident or due to an operational overlap—the server becomes completely unresponsive.

Specifically, if a stream is already live under a given key and another source tries to push to that same key (for example, two encoders using identical stream names), the system experiences a total crash. This failure affects not only the conflicting stream but also impacts the entire Ant Media service instance, requiring a manual restart to recover.

This behavior represents a critical vulnerability in stream session handling. Ideally, the platform should detect such a conflict gracefully and reject the second incoming stream with an appropriate error message, rather than allowing the collision to cause a full server crash.

We request that this issue be investigated and patched as a priority, as it poses a severe risk to live production environments where multiple operators may inadvertently use the same stream key. A robust mechanism to handle duplicate stream key attempts or concurrent publishing attempts is urgently needed to ensure system stability and reliability during live operations.

Please confirm receipt of this incident report and advise on any immediate mitigations or configuration workarounds until a permanent fix is available.

[burak-58]

AMS does not let using same key as stream ID. It returns streamIdInUse error.
Circle generates stream ID by itself. How can you add 2 participants with the same key? Please create a full scenario here.