| Significant latency and degraded bandwidth for 173.187.47.23 Hello, please look into the issues relating to the high latency and saturation of your network upstream of the Moody AL Access Concentrator. This issue is not related to CPE, this is upstream in your network.
There is measurable and significant latency and bandwidth reduction on all layer 3 traffic and is not layer 7 specific.
It seems that 173.187.47.237 is significantly degraded/saturated. Please escalate this upstream to Tier II/Escalation Team. I attempted to report this issue to Tier 1 and was unable to successfully convey the issue to the CSR who was engaged in a "chat" with Tier II because they "can't conference them in" or "transfer me". The issue isn't CPE or the Springville, AL CO, it's upstream.
I am disappointed as I used to be able to communicate with meaningful staff via phone; being stuck with Tier I could be because this is Sunday and hopefully not a procedural change for all support requests. It's very frustrating to have to explain upstream network issues to "did you reboot" and "tell me again what you're saying" staff.
# traceroute www.google.com -n
traceroute to www.google.com (74.125.113.103), 30 hops max, 38 byte packets
1 173.186.112.146 31.369 ms 32.352 ms 32.375 ms
2 173.187.47.61 32.213 ms 32.568 ms 32.318 ms
3 173.187.47.237 125.021 ms 123.880 ms 125.024 ms
4 166.102.72.88 124.497 ms 122.422 ms 119.827 ms
5 166.102.72.13 113.637 ms 166.102.72.13 118.236 ms 120.987 ms
6 72.14.239.100 122.850 ms 64.233.174.2 176.429 ms 166.313 ms
7 209.85.249.45 130.887 ms 209.85.249.238 153.791 ms 130.542 ms
8 64.233.174.87 134.529 ms 209.85.251.228 134.481 ms 64.233.174.87 162.388 ms
9 216.239.47.242 138.697 ms 209.85.243.1 134.779 ms 143.606 ms
10 74.125.113.103 138.531 ms 146.055 ms 143.225 ms
# traceroute speedtest.windstream.net -nn
traceroute to speedtest.windstream.net (162.39.145.20), 30 hops max, 38 byte packets
1 173.186.112.146 32.380 ms 32.257 ms 32.340 ms
2 173.187.47.49 32.503 ms 32.290 ms 32.366 ms
3 173.187.47.237 126.021 ms 122.917 ms 125.230 ms
4 166.102.72.94 122.110 ms 126.055 ms 126.200 ms
5 151.213.254.101 124.974 ms 149.574 ms 140.236 ms
6 66.109.236.18 161.700 ms 158.613 ms 152.865 ms
7 *
# traceroute www.windstream.net -nn
traceroute to www.windstream.net (64.8.70.11), 30 hops max, 38 byte packets
1 173.186.112.146 31.246 ms 32.335 ms 32.330 ms
2 173.187.47.61 32.553 ms 31.738 ms 32.648 ms
3 173.187.47.237 117.667 ms 118.647 ms 117.073 ms
4 166.102.72.90 115.921 ms 119.688 ms 114.411 ms
5 209.130.172.53 114.892 ms 118.439 ms 120.597 ms
6 207.218.80.218 118.644 ms 128.009 ms 127.473 ms
7 64.94.0.23 126.449 ms 133.753 ms 133.857 ms
8 216.52.194.210 130.880 ms 131.311 ms 130.647 ms
# traceroute www.windstream.com -nn
traceroute to www.windstream.com (173.203.26.198), 30 hops max, 38 byte packets
1 173.186.112.146 31.598 ms 32.315 ms 32.098 ms
2 173.187.47.49 32.522 ms 31.995 ms 32.615 ms
3 173.187.47.237 143.699 ms 119.498 ms 123.515 ms
4 166.102.72.90 120.784 ms 117.780 ms 115.601 ms
5 4.59.12.41 111.977 ms 107.570 ms 108.050 ms
6 4.69.150.126 104.497 ms 108.138 ms 110.189 ms
7 4.69.132.73 125.290 ms 130.725 ms 127.962 ms
8 4.69.140.194 123.869 ms 129.259 ms 140.118 ms
9 4.69.138.162 134.769 ms 134.211 ms 131.429 ms
10 4.71.248.54 134.178 ms 134.986 ms 131.917 ms
11 184.106.126.134 140.115 ms 184.106.126.132 144.810 ms 184.106.126.134
145.801 ms
12 184.106.126.125 147.369 ms 184.106.126.129 147.577 ms 184.106.126.125
149.750 ms
13 173.203.0.153 59.394 ms 59.560 ms 59.734 ms
Sincerely,
Business Class DSL Customer
Springville, AL |
|
 WindstreamPremium,VIP
join:2009-03-31
Twinsburg, OH
kudos:28 | I will get in contact with our Data Engineers and see if there is a known issue with that particular server. It may be a utilization, provisioning, routing, or programming issue. I will let you know if I find anything.
Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com |
|
| Thank you Aaron for your time, I am curious to see what the findings are if they are communicated back to you. I also sent a variant of this post via E-Mail to the wci.broadbandhelp E-mail address yesterday with my telephone number.
During the high latency "outage" there was also noticeable bandwidth degradation affecting the downstream. Upstream was fine, at the time of testing using various protocols and timing (ICMP echo request, TCP SYN timing for SYN-ACK, etc) RTT latency was ~200 to ~300ms and downstream bandwidth was 0.5 Mbit. The line was almost symmetric in nature with ~600K being seen in both directions. It seems that the router at 173.187.47.23 was starved for bandwidth.
Additionally, a residential customer adjacent to me was unaffected. Any recent EIGRP routing changes for Static IP DSL customers?
Thanks,
Springville, AL |
|
| reply to ALDSL
Aaron thanks for escalating this, this was resolved fully by Tue when I checked. Moderators would you mind locking this thread to indicate this is not an outstanding issue?
Thanks again Aaron and Windstream staff. |
|
WindstreamPremium,VIP
join:2009-03-31
Twinsburg, OH
kudos:28 | Glad it was fixed. I just received confirmation it was a simple coding issues in that servers.
Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com |
|
