Downstream QoS Prioritization Issue
Incident Report for Bigleaf Networks
Resolved
We have identified that our most recent software update, during our maintenance window on 9/10/2018, caused our QoS prioritization in the downstream direction to become ineffective. The root cause of this issue was an error in a configuration file that was unfortunately not caught during pre-rollout testing due to some specific timing in how the testing was performed. We identified the problem this morning and almost immediately resolved the issue. All QoS prioritization is now working correctly. We apologize for this issue and any application performance problems that it might have caused. We will be updating our testing procedures to ensure a situation like this is caught before rollout in the future. Please contact us at support@bigleaf.net if you have any questions or concerns
Posted about 1 year ago. Sep 18, 2018 - 11:34 PDT
This incident affected: Gateway Cluster: Atlanta, GA, Gateway Cluster: Chicago, IL, Gateway Cluster: Dallas, TX, Gateway Cluster: Los Angeles, CA, Gateway Cluster: New York, NY, and Gateway Cluster: Seattle, WA.