sMURF
join:2007-02-27
Toronto, ON | reply to zinc
Re: Packet loss rates up to 2% on TekSavvy DSL said by zinc:The real question is: are you seeing actual effects of packet loss or just seeing what you think is loss on pings/traceroutes? I'm seeing actual effects of packet loss. In fact, I'd bet that anyone on TekSavvy premium who goes through a similar route as me has packet loss, it all depends on if they notice it or not. One possible way to notice it is with websites. Anyone ever start to load a website, when it seems to just stall halfway through, even though your browser still shows it as loading, and the only way to get it to load fully is to hit F5 to refresh?
If you read my other thread ( »Peer1 is junk ), you'll see that I was testing a UT2004 gaming server. If I tested it anytime after around 6pm on a weekday, I'd get a steady 3% loss to it, with spikes up to 10-13%. It seems to be the worst at around 9pm and continues into the night. |
|
|
|
zincPremium
join:2004-02-17
Kitchener, ON | That question was intended @hiremichael
From your thread it's obvious that you are experiencing problems. I'm just personally not seeing it, but I also don't have UT2004 so I can't try with your server. I've never had the needing-to-F5 problem you've described either (well, except with Rogers' website, but that's broken half the time anyways).
FYI, I'm on Premium as well. |
|
sMURF
join:2007-02-27
Toronto, ON | said by zinc:From your thread it's obvious that you are experiencing problems. I'm just personally not seeing it, but I also don't have UT2004 so I can't try with your server. If you're online now, try a simple ping test. I'm showing about 4% loss to 72.51.60.248. But it's not just that server, it's everything that routes through the IPs I posted earlier, but I'm still betting that it's either 65.39.134.1 or 65.39.198.250 that's causing all the problems.
If you're not online now, try pinging that IP tomorrow. Do a test around noon, again at 5pm, and again at 10pm. You shouldn't see any packet loss at noon (other than the inaccurate numbers 65.39.134.1 spits out), you may see a bit of packet loss at 5pm, and at 10pm you should see a steady 3-5% loss. |
|
 TSI GabePremium,VIP
join:2007-01-03
Chatham, ON
kudos:2 | --- 72.51.60.248 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 14027ms
rtt min/avg/max/mdev = 25.854/28.504/38.116/2.449 ms, pipe 4
--- 65.39.134.1 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 13643ms
rtt min/avg/max/mdev = 13.886/15.276/61.957/4.137 ms, pipe 5
--- 65.39.198.250 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 14716ms
rtt min/avg/max/mdev = 14.663/17.252/31.470/2.119 ms, pipe 3 |
|
sMURF
join:2007-02-27
Toronto, ON | said by TSI Gabe:--- 72.51.60.248 ping statistics --- 1000 packets transmitted, 1000 received, 0% packet loss, time 14027ms rtt min/avg/max/mdev = 25.854/28.504/38.116/2.449 ms, pipe 4 Can you post a trace route? I'd like to know how you're not seeing any packet loss.
1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 14 ms 13 ms 206.248.154.102
3 13 ms 10 ms 11 ms 65.39.134.1
4 12 ms 13 ms 11 ms 65.39.198.250
5 13 ms 13 ms 13 ms oc48-po7-0.tor-1yg-cor-1.peer1.net [216.187.114.161]
6 23 ms 23 ms 23 ms 216.187.114.141
7 25 ms 26 ms 28 ms 72.51.60.248 |
|
TSI GabePremium,VIP
join:2007-01-03
Chatham, ON
kudos:2 | traceroute to 72.51.60.248 (72.51.60.248), 30 hops max, 38 byte packets
1 206.248.154.120 (206.248.154.120) 17.378 ms 13.681 ms 14.053 ms
2 206.248.155.233 (206.248.155.233) 13.568 ms 13.439 ms 13.063 ms
3 65.39.198.250 (65.39.198.250) 15.725 ms 15.992 ms 16.957 ms
4 oc48-po7-0.tor-1yg-cor-1.peer1.net (216.187.114.161) 15.890 ms 14.573 ms 14.994 ms
5 216.187.114.141 (216.187.114.141) 26.159 ms 25.307 ms 25.601 ms
6 * * *
The end IP is not responding to me for some reason.
I do note that my first hop is different than yours. We have 2 different routers facing the customers and our next upgrade this Tuesday night will most probably help with the problem you are having. |
|
zincPremium
join:2004-02-17
Kitchener, ON
1 edit | I'm on a different router (same as sMURF), so maybe these problems *are* being caused by the router we're on. I guess we'll see after the upgrade Tuesday.
I guess I've also just been lucky that I haven't been having any the problems you guys've been having...
Tracing route to 72.51.60.248 over a maximum of 30 hops
1 1 ms 1 ms <1 ms linksys-gw1 [192.168.10.1]
2 12 ms 13 ms 13 ms 206.248.154.102
3 12 ms 13 ms 13 ms 65.39.134.1
4 15 ms 15 ms 15 ms 65.39.198.250
5 14 ms 15 ms 15 ms oc48-po7-0.tor-1yg-cor-1.peer1.net [216.187.114.
161]
6 24 ms 25 ms 27 ms 216.187.114.141
7 24 ms 25 ms 27 ms 72.51.60.248
--
Ping statistics for 72.51.60.248:
Packets: Sent = 69, Received = 65, Lost = 4 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 46ms, Average = 25ms
--
Ping simultaneously from a host not on Teksavvy's network:
--- 72.51.60.248 ping statistics ---
66 packets transmitted, 66 received, 0% packet loss, time 65026ms
rtt min/avg/max/mdev = 0.817/1.276/2.560/0.336 ms, pipe 2
|
|
sMURF
join:2007-02-27
Toronto, ON | reply to TSI Gabe
said by TSI Gabe:traceroute to 72.51.60.248 (72.51.60.248), 30 hops max, 38 byte packets 1 206.248.154.120 (206.248.154.120) 17.378 ms 13.681 ms 14.053 ms 2 206.248.155.233 (206.248.155.233) 13.568 ms 13.439 ms 13.063 ms 3 65.39.198.250 (65.39.198.250) 15.725 ms 15.992 ms 16.957 ms 4 oc48-po7-0.tor-1yg-cor-1.peer1.net (216.187.114.161) 15.890 ms 14.573 ms 14.994 ms 5 216.187.114.141 (216.187.114.141) 26.159 ms 25.307 ms 25.601 ms 6 * * * The end IP is not responding to me for some reason. I do note that my first hop is different than yours. We have 2 different routers facing the customers and our next upgrade this Tuesday night will most probably help with the problem you are having. That makes it clear now. I'm not showing packet loss on 206.248.154.102. However, I am seeing packet loss on 65.39.134.1 and beyond.
Looks to me like 65.39.134.1 is the problem, but due to the fact that it sets ping packets to low priority, I couldn't get any accurate numbers from it.
Ping statistics for 72.51.60.248:
Packets: Sent = 225, Received = 218, Lost = 7 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 32ms, Average = 24ms
 |
|
| reply to TSI Gabe
said by TSI Gabe: We have 2 different routers facing the customers and our next upgrade this Tuesday night will most probably help with the problem you are having. This is a bit off topic, but any chance that you guys will do that change for bonding with MLPPP during this upgrade, as discussed in another topic, which I can't find now? |
|
