Flowplayer.com - Operational
Flowplayer.com
Notice history
Aug 2024
- ResolvedResolved
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.
- MonitoringMonitoring
Thank you for your patience as we have identified the issue, added a fix and monitoring the results.
More updates to follow...
- InvestigatingInvestigating
We are actively investigating this issue.
Known Impact: Wowza.com login can potentially get an intermittent 504 errors. This effects Wowza Video, and account login, which could effect accessing/viewing support tickets.Workaround: Refresh page and attempt logging in again. If you need to reach out to support, the email address is: support@wowza.com
Also, Wowza REST API calls can potentially get intermittent 503 service unavailable responses.
Workaround: For failed REST API calls that get a 503 service unavailable response, please re-attempt the REST API call.
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
- ResolvedResolved
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.
- IdentifiedIdentified
We have identified the issue. We are currently working to fix to address this issue.
We apologize for any inconvenience. We will provide updates here as they become available. - InvestigatingInvestigating
We are actively investigating this issue.
Known Impact: A small portion of Wowza Video v2 and OVP users are reporting getting a blank page when logging into the UI
Workaround: go to video.wowza.com to use the Legacy UI
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
- ResolvedResolved
We’re happy to report a StreamLock renewal 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.
- InvestigatingInvestigating
We are actively investigating this issue.
Known Impact: Unable to renew Streamlock certificates
Workaround: Create a temp certificate
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
- ResolvedResolved
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.
- MonitoringMonitoring
We have identified and implemented a fix. We are monitoring the results.
- UpdateUpdate
Wowza Account and Wowza Video Login and could potentially get 504 bad gateway errors.
As a workaround, if you need to reach out to Wowza Support, please email at the below address:'
- InvestigatingInvestigating
We are actively investigating this issue where wowza.
Known Impact: Wowza account and Wowza Video login pages are down
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
Jul 2024
- ResolvedResolved
We’re happy to report a fix was deployed and was successful for all Wowza WebRTC example pages. 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.
- UpdateUpdate
We have the fix added to our public Github pages:
https://github.com/WowzaMediaSystems/webrtc-examples
More updates to follow on when the Wowza Video WebRTC examples have a fix implemented.
Thank you for your patience!
- IdentifiedIdentified
Wowza Streaming Engine WebRTC publish and play pages have been fixed. You'll need to clear Javascript cache for the changes to take effect.
We are currently working on a resolution for Wowza Video and the Github WebRTC page examples.
More updates to follow...
- InvestigatingInvestigating
We are actively investigating this issue.
Known Impact:
Wowza WebRTC Publish Page impacted if using the recently updated Chrome browser (Version 127.0.6533.73)
Workflows affected:
Deliver WebRTC streams to viewers using Wowza Video
WebRTC Hosted Publish PageA hosted page for testing WebRTC Publish with Wowza Video.
Workaround:
Prior versions of Chrome work as expected along with other browsers.
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
- ResolvedResolved
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.
- IdentifiedIdentified
We have identified the issue. We are currently working to fix to address this issue.
We apologize for any inconvenience. We will provide updates here as they become available. - InvestigatingInvestigating
We are actively investigating this issue.
Known Impact: Encoders are unable to connect to Stream Sources
Workaround: Create new live stream without using Stream Source option
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
- ResolvedResolved
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.
- IdentifiedIdentified
We have identified the issue. We are currently working on a fix to address this issue.
We apologize for any inconvenience. We will provide updates here as they become available. - InvestigatingInvestigating
We are actively investigating this issue.
Known Impact: "Create a ticket" and "View your tickets" are not accessible. (500 Server Error)
Workaround: Send an email directly to support@wowza.com
We apologize for any inconvenience this may be causing; we will provide updates here as they become available.
Jun 2024
- UpdateJuly 12, 2024 at 9:33 PMCompletedJuly 12, 2024 at 9:33 PM
Update as the old IP's should be kept till further notice:
Who does this affect?
If you are using a Wowza Streaming Engine pull to Wowza CDN workflow and you whitelist Wowza CDN IP addresses in your firewall, you will need to take action to prevent disruption of your streams.What do I need to do?
Please add the new IP addresses into your workflow before July 11th, 2024:
Oregon (us-west-2):
44.232.207.68,
54.245.251.133,
35.161.232.146Seoul (ap-northeast-2):
13.124.180.184,
3.39.128.171,
3.39.185.132Frankfurt (eu-central-1):
3.65.160.245,
3.76.110.124,
18.195.249.55
After July 11, 2024, please keep the legacy IP's in place till further notice. We'll share an update on when they can be removed from your firewall rules:129.153.100.158
129.153.114.13
129.154.207.194
132.145.253.238
138.3.255.30
141.147.1.186
146.56.156.1
158.101.43.210
193.123.241.42
Further details can be found in the below article in step 9:
Pull streams from Wowza Streaming Engine to Wowza CDNIf you use the REST API, refer to this article:
Send a stream from Wowza Streaming Engine to a Wowza CDN HLS target using Wowza REST APIs
If there are any questions please, contact Wowza Support.
Thank you again for being a valued Wowza customer. We appreciate your business!
Best,
The Wowza Support Team - CompletedJuly 11, 2024 at 7:00 PMCompletedJuly 11, 2024 at 7:00 PMMaintenance has completed successfully
- In progressJune 27, 2024 at 3:00 PMIn progressJune 27, 2024 at 3:00 PMMaintenance is now in progress
- PlannedJune 27, 2024 at 3:00 PMPlannedJune 27, 2024 at 3:00 PM
Who does this affect?
If you are using a Wowza Streaming Engine pull to Wowza CDN workflow and you whitelist Wowza CDN IP addresses in your firewall, you will need to take action to prevent disruption of your streams.What do I need to do?
Please add the new IP addresses into your workflow before July 11th, 2024:
Oregon (us-west-2):
44.232.207.68,
54.245.251.133,
35.161.232.146Seoul (ap-northeast-2):
13.124.180.184,
3.39.128.171,
3.39.185.132Frankfurt (eu-central-1):
3.65.160.245,
3.76.110.124,
18.195.249.55
After July 11, 2024, please remove the legacy IPs from your workflow as they will no longer be valid:129.153.100.158
129.153.114.13
129.154.207.194
132.145.253.238
138.3.255.30
141.147.1.186
146.56.156.1
158.101.43.210
193.123.241.42
Further details can be found in the below article in step 9:
Pull streams from Wowza Streaming Engine to Wowza CDNIf you use the REST API, refer to this article:
Send a stream from Wowza Streaming Engine to a Wowza CDN HLS target using Wowza REST APIs
If there are any questions please, contact Wowza Support.
Thank you again for being a valued Wowza customer. We appreciate your business!
Best,
The Wowza Support Team