| ID | Description | Impact | |----|-------------|--------| | WZ-24567 | WebRTC playback stalls on Safari after 2 minutes | Fixed via SDP renegotiation | | WZ-24891 | HLS AES-128 key rotation fails on edge servers | Resolved by synchronizing token TTL | | WZ-25012 | REST API /v2/streams returns 500 on high load | Memory leak in JSON serializer patched | | WZ-25103 | MPEG-TS input with PCR jitter causes disconnect | Improved PCR tolerance window |
| Feature | Deprecated in | Removal in | |---------|---------------|-------------| | RTMP port 1935 (plain) | 4.9.0 | 5.0 (use port 1935 with TLS) | | Legacy VOD file scanning (XML-based) | 4.8.0 | 5.0 (use REST API) | | Windows 2012 R2 support | 4.10.0 | 4.11.0 | | JMX-based monitoring (non-Prometheus) | 4.9.2 | 5.0 | wowza streaming engine release notes
This article breaks down the anatomy of a typical Wowza Streaming Engine release note, highlights what to look for in recent updates, and provides best practices for upgrading. Every official release note from Wowza (accessible at www.wowza.com/docs ) follows a consistent structure: | ID | Description | Impact | |----|-------------|--------|
Set a recurring monthly reminder to check for new patch releases. Most production issues are fixed within 30 days of being reported — and those fixes are always detailed in the release notes first. Have a specific version’s release notes in mind? Visit the official Wowza documentation portal and search for your exact build number. Have a specific version’s release notes in mind