Hello, I am experiencing an increase in my usual ping of roughly 50 to a ping of 90 now. This has been occuring for a few weeks now and has happened before in the past. Unfortunetly, as with the pervious occurance, there is nothing that can be done on my end to resolve this issue as it is NOT a local connection issue.
ISP: Shaw
I will post the tracert here to show the origin of the increased ping. Hopefully there is something that can be done on your end to address this issue.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 9 ms 8 ms 8 ms 96.52.64.1
3 9 ms 10 ms 12 ms rc2we-be105-1.ed.shawcable.net [64.59.186.61]
4 9 ms 9 ms 9 ms rc2ar-be7.ed.shawcable.net [66.163.70.130]
5 26 ms 24 ms 29 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
6 39 ms 43 ms 39 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
7 38 ms 39 ms 39 ms chi-b21-link.telia.net [213.248.84.97]
8 40 ms 39 ms 38 ms ae-25.r08.chcgil09.us.bb.gin.ntt.net [129.250.8.61]
9 55 ms 41 ms 42 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
10 92 ms 93 ms 94 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 99 ms 95 ms 96 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 97 ms 96 ms 96 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 96 ms 96 ms 96 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 96 ms 100 ms 95 ms 204.2.229.234
15 95 ms 96 ms 99 ms 204.2.229.10
Trace complete.
The issue seems to be steaming from ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17].
Thanks
Continue reading...
ISP: Shaw
I will post the tracert here to show the origin of the increased ping. Hopefully there is something that can be done on your end to address this issue.
Tracing route to 204.2.229.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 9 ms 8 ms 8 ms 96.52.64.1
3 9 ms 10 ms 12 ms rc2we-be105-1.ed.shawcable.net [64.59.186.61]
4 9 ms 9 ms 9 ms rc2ar-be7.ed.shawcable.net [66.163.70.130]
5 26 ms 24 ms 29 ms rc3sc-be1.wp.shawcable.net [66.163.70.77]
6 39 ms 43 ms 39 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
7 38 ms 39 ms 39 ms chi-b21-link.telia.net [213.248.84.97]
8 40 ms 39 ms 38 ms ae-25.r08.chcgil09.us.bb.gin.ntt.net [129.250.8.61]
9 55 ms 41 ms 42 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
10 92 ms 93 ms 94 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 99 ms 95 ms 96 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 97 ms 96 ms 96 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 96 ms 96 ms 96 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 96 ms 100 ms 95 ms 204.2.229.234
15 95 ms 96 ms 99 ms 204.2.229.10
Trace complete.
The issue seems to be steaming from ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17].
Thanks
Continue reading...