Incident with Wowza Streaming Engine - StreamLock Certificate Issue.

Update timeline

1. resolved Nov 19, 2025, 06:10 AM UTC

   Type: Incident Duration: 15 hours and 16 minutes Nov 19, 06:38:25 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 19, 06:46:03 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 19, 08:50:01 GMT+0 - Identified - We are aware of an issue affecting the availability of StreamLock-secured connections and are actively working with our external service provider to restore full functionality. The matter is being treated with the highest priority. In the meantime, customers who need an urgent workaround can install a self-managed SSL certificate or any other SSL certificate on their Wowza server. Support is available to assist with this process. We will provide the next update as soon as we have more information or a confirmed timeline for recovery. Thank you for your patience while we work to resolve this. Nov 19, 18:58:54 GMT+0 - Monitoring - We have identified the root cause of the service disruption and deployed a fix. The solution is currently propagating across our infrastructure. During this propagation window, some customers may continue to experience intermittent or delayed restoration of service. Performance and availability may fluctuate as the update completes. We will continue to actively monitor the environment and provide another update as soon as full service stability is confirmed. Thank you for your patience. Nov 19, 21:26:56 GMT+0 - Resolved - > The issue affecting StreamLock-secured connections has now been resolved, and services should be functioning normally again. This interruption was linked to an unexpected problem with one of our external service providers. As soon as it was detected, our teams worked closely with them to restore full functionality. We'll continue to monitor the environment to ensure stability moving forward. > > We sincerely apologize for the inconvenience this caused. If you experience anything unusual or need further assistance, please let us know. We're here to support you. Nov 19, 10:16:57 GMT+0 - Identified - We are continuing to monitor and investigate the issue affecting StreamLock-secured connections. Our teams remain actively engaged with the external service provider, and this matter is being treated with the highest priority. At this time, there is no change to the status, but we will provide the next update as soon as we have additional information or a confirmed timeline for recovery. Thank you for your patience while we work to resolve this. Nov 19, 12:23:45 GMT+0 - Identified - Our teams are continuing to work closely with the external service provider to restore full stability for StreamLock-secured connections. The issue remains a top priority, and we are actively monitoring all related systems. We will provide the next update as soon as new information becomes available. Nov 19, 16:26:07 GMT+0 - Identified - Our teams, in coordination with the external service provider, continue to work on restoring full functionality for StreamLock-secured connections. The issue remains a top priority, and progress is being made toward resolution. We will provide the next update as soon as the issue is fully resolved or additional information becomes available. Thank you for being so patient. Nov 19, 06:10:43 GMT+0 - Investigating - **We are actively investigating this issue.** _Known Impact_: Customers may be experiencing **DNS resolution failures** (specifically the `DNS_PROBE_FINISHED_NXDOMAIN` error) when attempting to connect to secure streaming endpoints (`*.streamlock.net`). We apologize for any inconvenience this may be causing; we will provide updates here as they become available.