Wowza Outage History

Started Jul 07, 2026, 01:36 PM UTC· resolved Jul 07, 2026, 02:40 PM UTC

1. investigating Jul 07, 2026, 01:36 PM UTC

   Some users may experience being redirected back to the login page when attempting to sign in. Our team is actively investigating the issue. We will provide an update as soon as more information becomes available.

2. resolved Jul 07, 2026, 02:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 01:36 PM UTC· resolved Jul 07, 2026, 02:40 PM UTC

1. investigating Jul 07, 2026, 01:36 PM UTC

   Some users may experience being redirected back to the login page when attempting to sign in. Our team is actively investigating the issue. We will provide an update as soon as more information becomes available..

2. resolved Jul 07, 2026, 02:40 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jun 29, 2026, 03:49 PM UTC· resolved Jun 29, 2026, 06:22 PM UTC

1. investigating Jun 29, 2026, 03:49 PM UTC

   AI transcriptions for Wowza Video and Flowplayer OVP are currently not progressing. We are currently investigating this incident. All submitted transcriptions are queued and will be processed once the issue is resolved.

2. resolved Jun 29, 2026, 06:22 PM UTC

   This incident has been resolved, and the remaining transcriptions in the backlog are being processes.

Read the full incident report →

Started Jun 16, 2026, 07:26 PM UTC· resolved Jun 16, 2026, 08:50 PM UTC

1. investigating Jun 16, 2026, 07:26 PM UTC

   We are currently investigating this incident. Although it appears user are still able to login to their FLowplayer accounts using app.flowplayer.com

2. identified Jun 16, 2026, 07:46 PM UTC

   We are continuing to work on a fix for this incident. Access to the OVP Platform via [app.flowplayer.com](http://app.flowplayer.com) is not impacted; if you have any issues please contact Wowza Technical Support

3. monitoring Jun 16, 2026, 08:10 PM UTC

   We implemented a fix and are currently monitoring the result.

4. resolved Jun 16, 2026, 08:50 PM UTC

   **We’re happy to report a fix was deployed and was successful.** This incident has been closed. Our apologies for any inconvenience this may have caused. If you experience any issues going forward, please [contact Wowza Support](https://www.wowza.com/portal/help/video).

Read the full incident report →

Started Jun 16, 2026, 07:26 PM UTC· resolved Jun 16, 2026, 08:50 PM UTC

1. investigating Jun 16, 2026, 07:26 PM UTC

   We are currently investigating this incident. Although it appears user are still able to login to their FLowplayer accounts using app.flowplayer.com.

2. identified Jun 16, 2026, 07:46 PM UTC

   We are continuing to work on a fix for this incident. Access to the OVP Platform via [app.flowplayer.com](http://app.flowplayer.com) is not impacted; if you have any issues please contact Wowza Technical Support.

3. monitoring Jun 16, 2026, 08:10 PM UTC

   We implemented a fix and are currently monitoring the result..

4. resolved Jun 16, 2026, 08:50 PM UTC

   **We’re happy to report a fix was deployed and was successful.** This incident has been closed. Our apologies for any inconvenience this may have caused. If you experience any issues going forward, please [contact Wowza Support](https://www.wowza.com/portal/help/video)..

Read the full incident report →

Started Mar 23, 2026, 11:38 PM UTC· resolved Mar 24, 2026, 03:00 PM UTC

1. investigating Mar 23, 2026, 11:38 PM UTC

   We are seeing delays in processing new, renewal, and replacement Streamlock certificates. Existing certificates and active streams are not affected. We are working with our provider and will share updates shortly..

2. monitoring Mar 24, 2026, 02:35 PM UTC

   The delay affecting new, renewal, and replacement Streamlock SSL certificate issuance has been resolved. Existing certificates and active streams were not impacted..

3. resolved Mar 24, 2026, 03:00 PM UTC

   This issue has been fully resolved, and certificate issuance is operating normally. Thank you for your patience..

Read the full incident report →

Started Feb 17, 2026, 01:26 PM UTC· resolved Mar 24, 2026, 08:18 PM UTC

1. identified Feb 17, 2026, 01:26 PM UTC

   Due to work on the backend, the realtime analytics view in Flowplayer OVP is currently unavailable. We continue to work on the system and will restore the realtime analytics soon..

2. resolved Mar 24, 2026, 08:18 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Feb 15, 2026, 03:27 AM UTC· resolved Feb 16, 2026, 02:22 AM UTC

1. investigating Feb 15, 2026, 03:27 AM UTC

   We are investigating reports of slower video segment downloads for some users in the United States. This may cause the video quality to temporarily switch to a lower renditions during playback. Our team is actively working to resolve the issue..

2. investigating Feb 15, 2026, 05:51 AM UTC

   We are continuing to investigate increased HLS segment download times impacting some users in the United States. Further updates will be provided as soon as more information is available..

3. investigating Feb 15, 2026, 10:10 AM UTC

   We are continuing to investigate increased HLS segment download times affecting some live streams in the United States region. Users may experience temporary quality reductions during playback while this is being addressed. Further updates will be provided as more information becomes available..

4. identified Feb 15, 2026, 03:38 PM UTC

   We have identified the cause of the intermittent video playback quality reductions affecting some live streams in the United States. Our engineering teams are actively working on mitigation and are monitoring the situation closely. We will continue to provide updates as progress is made..

5. monitoring Feb 15, 2026, 05:49 PM UTC

   A fix has been implemented to address the intermittent video playback quality reductions affecting some live streams in the United States. We are no longer observing the issue and are actively monitoring to ensure continued stability. We will provide a final update once monitoring is complete..

6. resolved Feb 16, 2026, 02:22 AM UTC

   The issue affecting intermittent video playback quality for some live streams in the United States has been resolved. Thank you for your patience..

Read the full incident report →

Started Jan 20, 2026, 07:18 PM UTC· resolved Jan 20, 2026, 08:38 PM UTC

1. investigating Jan 20, 2026, 07:18 PM UTC

   We are currently investigating as to why we are seeing this behavior during this time..

2. monitoring Jan 20, 2026, 07:36 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Jan 20, 2026, 08:38 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Dec 05, 2025, 09:14 AM UTC· resolved Dec 05, 2025, 11:45 AM UTC

1. investigating Dec 05, 2025, 09:14 AM UTC

   Support ticketing system along with Live Chat is currently offline due to an outage. We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. monitoring Dec 05, 2025, 09:26 AM UTC

   The Support ticketing system, along with the Live Chat, is currently available. We are currently monitoring the incident for stability..

3. resolved Dec 05, 2025, 11:45 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Nov 19, 2025, 06:10 AM UTC· resolved Nov 19, 2025, 09:26 PM UTC

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

   **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..

2. identified Nov 19, 2025, 06:38 AM UTC

   We are continuing to work on a fix for this incident..

3. identified Nov 19, 2025, 06:46 AM UTC

   We are continuing to work on a fix for this incident..

4. identified Nov 19, 2025, 08:50 AM UTC

   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..

5. identified Nov 19, 2025, 10:16 AM UTC

   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..

6. identified Nov 19, 2025, 12:23 PM UTC

   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..

7. identified Nov 19, 2025, 04:26 PM UTC

   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..

8. monitoring Nov 19, 2025, 06:58 PM UTC

   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..

9. resolved Nov 19, 2025, 09:26 PM UTC

   > 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..

Read the full incident report →

Started Oct 20, 2025, 01:00 PM UTC· resolved Oct 20, 2025, 02:57 PM UTC

1. investigating Oct 20, 2025, 01:00 PM UTC

   We're currently investigating reports of transcoder startup failures affecting the US East region. Other regions continue to operate normally. Our engineering team is actively working on a resolution.

2. identified Oct 20, 2025, 02:48 PM UTC

   We are continuing to work on a fix for this incident..

3. monitoring Oct 20, 2025, 02:51 PM UTC

   We implemented a fix and are currently monitoring the result..

4. resolved Oct 20, 2025, 02:57 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 07, 2025, 08:31 AM UTC· resolved Oct 07, 2025, 10:01 AM UTC

1. investigating Oct 07, 2025, 08:31 AM UTC

   **We are actively investigating this issue.** _Known Impact_: Unable to start New and existing Transcoders in Wowza Video! _Workaround_: None, We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. identified Oct 07, 2025, 09:40 AM UTC

   We are continuing to work on a fix for this incident..

3. monitoring Oct 07, 2025, 09:45 AM UTC

   We’ve implemented a fix and are currently monitoring its impact. We believe this issue is resolved and will monitor for another 10 minutes to ensure transcoder startup success..

4. resolved Oct 07, 2025, 10:01 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Sep 30, 2025, 03:47 PM UTC· resolved Oct 01, 2025, 08:40 AM UTC

1. investigating Sep 30, 2025, 03:47 PM UTC

   **We are actively investigating this issue.** _Known Impact_: Wowza Video and Flowplayer OVP using clipping does not allow users to additional clips to the clip reel. _Workaround_: There is currently no know work around at this time. We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. identified Sep 30, 2025, 06:46 PM UTC

   We are continuing to work on a fix for this incident..

3. resolved Oct 01, 2025, 08:40 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Sep 18, 2025, 10:04 AM UTC· resolved Sep 18, 2025, 10:32 AM UTC

1. investigating Sep 18, 2025, 10:04 AM UTC

   There is an issue affecting the [wowza.com](http://wowza.com) homepage, which may not load as expected. All other subpages (including documentation) and streaming services remain fully operational. Our team is investigating and will provide updates as they become available..

2. resolved Sep 18, 2025, 10:32 AM UTC

   The issue affecting the [wowza.com](http://wowza.com) homepage has been resolved. The site is now loading normally. Subpages and streaming services were unaffected throughout..

Read the full incident report →

Started Jun 27, 2025, 03:28 PM UTC· resolved Jun 27, 2025, 05:03 PM UTC

1. investigating Jun 27, 2025, 03:28 PM UTC

   **We are actively investigating this issue.** _Known Impact_: This will prevent starting Live stream by publishing from the encoder. We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. monitoring Jun 27, 2025, 04:09 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Jun 27, 2025, 05:03 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jun 27, 2025, 02:06 PM UTC· resolved Jun 27, 2025, 02:45 PM UTC

1. investigating Jun 27, 2025, 02:06 PM UTC

   **We are actively investigating this issue.** _Known Impact_: This is preventing users from starting new live streams. We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. investigating Jun 27, 2025, 02:11 PM UTC

   We continue to investigate this issue with transcoders not starting. Note: all existing transcoders are unaffected at this time. Updates to follow. .

3. identified Jun 27, 2025, 02:17 PM UTC

   We have identified the issue and have deployed a fix. We will begin monitoring and will provide an update very soon. .

4. monitoring Jun 27, 2025, 02:24 PM UTC

   We implemented a fix and are currently monitoring the result. We see some regions starting up successfully. Not all are operational at this time. We are continuing to resolve this issue as quickly as possible. Thank you for your patience. .

5. monitoring Jun 27, 2025, 02:36 PM UTC

   WWe’ve implemented a fix and are currently monitoring its impact. Since 14:29 UTC, we’ve stopped seeing startup errors. We believe this issue is resolved and will monitor for another 10 minutes to ensure transcoder startup success. .

6. resolved Jun 27, 2025, 02:45 PM UTC

   This incident has been resolved. All transcoders are starting successfully in all regions. .

Read the full incident report →

Started Jun 12, 2025, 07:32 PM UTC· resolved Jun 12, 2025, 09:39 PM UTC

1. investigating Jun 12, 2025, 07:32 PM UTC

   We are currently investigating an issue where HLS streams will show connected, but no connection is established and the stream does not display a preview..

2. identified Jun 12, 2025, 07:45 PM UTC

   We are continuing to work on a fix for this incident..

3. identified Jun 12, 2025, 07:45 PM UTC

   We are continuing to work on a fix for this incident..

4. identified Jun 12, 2025, 07:46 PM UTC

   We are continuing to work on a fix for this incident where CDN playback is getting 500 errors. More updates to follow..

5. identified Jun 12, 2025, 07:47 PM UTC

   We are continuing to work on a fix for this incident where CDN playback is getting 500 errors. More updates to follow..

6. identified Jun 12, 2025, 08:24 PM UTC

   Thank you for your patience! We identified the issue and are seeing HLS playback starting to return. We are continuing to monitor and more updates to follow..

7. monitoring Jun 12, 2025, 08:45 PM UTC

   Thank you for your patience. We implemented a fix and are currently monitoring the result..

8. resolved Jun 12, 2025, 09:39 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jun 04, 2025, 07:27 AM UTC· resolved Jun 05, 2025, 06:50 AM UTC

1. investigating Jun 04, 2025, 07:27 AM UTC

   We are currently investigating an intermittent issue where some existing transcoders may fail to start, displaying the error: **"Unable to start the transcoder at this time. Please try again."** This issue does not affect all transcoders, and newly created transcoders or other existing transcoders may continue to work as expected. If you encounter this issue, please try using a different transcoder or creating a new one..

2. identified Jun 04, 2025, 09:51 AM UTC

   We have identified the issue affecting the ability to start certain transcoders. The issue is limited to specific transcoder instances and does not impact all transcoders/customers. We are working on implementing a fix. In the meantime, as a workaround, affected users may be able to start a new transcoder instead of reusing the impacted one. We will provide an update as soon as the fix is in place..

3. monitoring Jun 04, 2025, 02:51 PM UTC

   We have implemented a fix and are currently monitoring the result..

4. resolved Jun 05, 2025, 06:50 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Apr 14, 2025, 04:53 PM UTC· resolved Apr 14, 2025, 05:20 PM UTC

1. investigating Apr 14, 2025, 04:53 PM UTC

   **We are actively investigating this issue.** _Known Impact_: _This morning we received several reports about Wowza Streaming Engine containers no longer showing up on Google Marketplace. We’re actively working to correct this at the highest priority. Initial testing shows this is only impacting new container implementations from the marketplace, existing containers in GCP running Wowza Streaming Engine are working as expected._ _Workaround_: NA We apologize for any inconvenience this may be causing; we will provide updates here as they become available..

2. resolved Apr 14, 2025, 05:20 PM UTC

   **We’re happy to report a fix was deployed and was successful.** This incident has been closed. Our apologies for any inconvenience this may have caused. If you experience any issues going forward, please [contact Wowza Support](https://www.wowza.com/portal/help/video)..

Read the full incident report →

Started Mar 07, 2025, 03:50 PM UTC· resolved Mar 07, 2025, 05:27 PM UTC

1. investigating Mar 07, 2025, 03:50 PM UTC

   We are currently investigating errors affecting the creation of new Live Streams and Transcoders for Wowza Video users. Existing running streams and transcoders are unaffected. Login to the interface is also experiencing inconsistent loading issues. .

2. monitoring Mar 07, 2025, 04:57 PM UTC

   Thank you for your patience. We implemented a fix and are currently monitoring the result..

3. resolved Mar 07, 2025, 05:27 PM UTC

   **We’re happy to report a fix was deployed and was successful.** This incident has been closed. Our apologies for any inconvenience this may have caused. If you experience any issues going forward, please [contact Wowza Support](https://www.wowza.com/portal/help/video)..

Read the full incident report →

Started Nov 27, 2024, 03:48 PM UTC· resolved Nov 27, 2024, 05:28 PM UTC

1. investigating Nov 27, 2024, 03:48 PM UTC

   We are currently investigating this incident..

2. monitoring Nov 27, 2024, 04:14 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Nov 27, 2024, 05:28 PM UTC

   This incident has been resolved..

Read the full incident report →