dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
604
share rss forum feed


stickperson2

@teksavvy.com

Ping spikes/packet loss

Hi everyone,
recently my internet has been running slowly and the online games I've been running have experienced extremely high pings and delays. I did a traceroute
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Arthur>tracert google.com

Tracing route to google.com [74.125.226.66]
over a maximum of 30 hops:

1 5 ms 1 ms 5 ms 192.168.1.1
2 1162 ms 1306 ms 1178 ms 10.126.245.129
3 1314 ms 1196 ms 1491 ms 69.63.242.173
4 1746 ms 1713 ms 1886 ms richmondhill-newkirk4.cable.teksavvy.com [24.52.
255.94]
5 1743 ms 1427 ms 1387 ms richmondhill-newkirk4.cable.teksavvy.com [24.52.
255.93]
6 1550 ms 1563 ms 1572 ms gw-google.torontointernetxchange.net [206.108.34
.6]
7 1606 ms 1581 ms 1851 ms 216.239.47.114
8 1551 ms 1696 ms 1616 ms 64.233.175.98
9 1365 ms 1381 ms 1616 ms yyz06s07-in-f2.1e100.net [74.125.226.66]

Trace complete.

So what does this mean?



JonF
Premium
join:2012-11-22
Chatham, ON

Hi there,

Could we try the trace without the router?


stickdude2

join:2008-12-22
reply to stickperson2

sry how would I do that?



stickperson2

@teksavvy.com
reply to stickperson2

hmm and how would I do that?



d4m1r

join:2011-08-25
reply to stickperson2

Plug your PC directly into the modem....Or just "edit" your traceroute to save yourself the trouble


videonerd

join:2007-01-21
reply to stickperson2

I went through this last week. Rogers came back and said the connection to my modem as fine (well DUH yes it is) and closed the ticket. Throughout Christmas Day and today the ping remained ~1000ms... I took my modem to my parent's house just to see if it was the modem. Nope. Now that I'm back home, I plugged in the modem and everything is fine. Maybe you took my unlucky port? :)


traceroute: Warning: www.google.com has multiple addresses; using 74.125.226.16
traceroute to www.google.com (74.125.226.16), 64 hops max, 52 byte packets
1 10.126.7.129 (10.126.7.129) 773.125 ms 829.053 ms 879.254 ms
2 69.63.243.229 (69.63.243.229) 833.885 ms 890.163 ms 947.187 ms
3 yorkmills7 (24.52.255.38) 939.332 ms
yorkmills2 (24.52.255.10) 1011.793 ms
yorkmills7 (24.52.255.38) 1065.489 ms
4 yorkmills5 (24.52.255.133) 1102.736 ms 1156.063 ms 1161.222 ms
5 gw-google.torontointernetxchange.net (206.108.34.6) 1139.930 ms 1443.087 ms 578.945 ms
6 216.239.47.114 (216.239.47.114) 627.215 ms 708.320 ms 680.074 ms
7 72.14.233.142 (72.14.233.142) 667.806 ms 897.389 ms 810.334 ms
8 yyz06s05-in-f16.1e100.net (74.125.226.16) 896.409 ms 835.416 ms 873.989 ms


Here's what Teksavvy tech support will ask you anyway, this was my template that I sent to Teksavvy in the Direct forum. I give them as much info as necessary, so Rogers can't kick the ticket back and ask for more info and drag their heels.

*** MODEM STATS ***
Manufacturer & Model:
Serial:
MAC:
Software version:
Software Model:
Bootloader:

// Paste info from the modem stats (Power/SNR/etc) below:




*** PING TO EXTERNAL IP ***
// Mac: ping -c 50 -s 1000 xxx.xxx.xxx.xxx
// PC: ping -n 100 -l 1000 xxx.xxx.xxx.xxx




*** PING TO GATEWAY ***
// Mac: ping -c 50 -s 1000 xxx.xxx.xxx.xxx
// PC: ping -n 100 -l 1000 xxx.xxx.xxx.xxx




*** PING TO GOOGLE.COM ***
// Mac: ping -c 50 -s 1000 www.google.com
// PC: ping -n 100 -l 1000 www.google.com




*** PING TO ROGERS.COM ***
// Mac: ping -c 50 -s 1000 www.rogers.com
// PC: ping -n 100 -l 1000 www.rogers.com




*** TRACEROUTE TO GOOGLE.COM ***
// Mac: traceroute www.google.com
// PC: tracert www.google.com




*** TRACEROUTE TO ROGERS.COM ***
// Mac: traceroute www.rogers.com
// PC: tracert www.rogers.com



videonerd

join:2007-01-21

spoke too soon... was wondering why it took so long to post .... ø©ƒ IT'S HAPPENING AGAIN!!!!!


traceroute to www.google.com (74.125.226.49), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.755 ms 0.566 ms 0.548 ms
2 10.126.7.129 (10.126.7.129) 989.916 ms 1015.427 ms 1045.312 ms
3 69.63.243.229 (69.63.243.229) 1058.360 ms 1083.732 ms 1131.910 ms
4 yorkmills7.cable.teksavvy.com (24.52.255.38) 1129.183 ms
yorkmills1.cable.teksavvy.com (69.165.168.14) 1185.620 ms
yorkmills5.cable.teksavvy.com (24.52.255.134) 1213.214 ms
5 yorkmills2.cable.teksavvy.com (24.52.255.9) 1214.074 ms 1239.719 ms 1284.335 ms
6 72.14.212.134 (72.14.212.134) 1308.188 ms 1325.174 ms 1351.949 ms
7 216.239.47.114 (216.239.47.114) 1364.668 ms 1434.127 ms 1443.634 ms
8 64.233.175.132 (64.233.175.132) 1433.465 ms 525.291 ms 687.529 ms
9 yyz06s06-in-f17.1e100.net (74.125.226.49) 684.699 ms 727.971 ms 733.541 ms


stickdude2

join:2008-12-22
reply to stickperson2

redid a tracert directly connected to the modem

C:\Windows\system32>tracert google.com

Tracing route to google.com [74.125.226.4]
over a maximum of 30 hops:

1 484 ms 600 ms 623 ms 10.126.245.129
2 1010 ms 900 ms 598 ms 69.63.242.173
3 1054 ms 915 ms 686 ms richmondhill-newkirk1.cable.teksavvy.com [69.165
.168.242]
4 1022 ms 1093 ms 1094 ms richmondhill-newkirk4.cable.teksavvy.com [24.52.
255.93]
5 950 ms 854 ms 976 ms gw-google.torontointernetxchange.net [206.108.34
.6]
6 1170 ms 1127 ms 1204 ms 216.239.47.114
7 815 ms 705 ms 913 ms 72.14.233.142
8 1150 ms 1137 ms 976 ms yyz06s05-in-f4.1e100.net [74.125.226.4]

Trace complete.


stickdude2

join:2008-12-22
reply to stickperson2

pinged google while connected directly to modem
C:\Windows\system32>ping google.com

Pinging google.com [74.125.225.35] with 32 bytes of data:
Reply from 74.125.225.35: bytes=32 time=1415ms TTL=54
Reply from 74.125.225.35: bytes=32 time=1346ms TTL=54
Reply from 74.125.225.35: bytes=32 time=1276ms TTL=54
Reply from 74.125.225.35: bytes=32 time=1132ms TTL=54

Ping statistics for 74.125.225.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1132ms, Maximum = 1415ms, Average = 1292ms



TSI Keith
Premium
join:2012-07-09
kudos:5

Hello,

Can you please post your account information in the direct forum here: »TekSavvy Direct and we can look into getting a ticket submitted for you here.

Thank you,
Keith
--
TSI Keith (E-Services) - TekSavvy Solutions Inc.
Authorized TSI employee ( »TekSavvy FAQ »Official support in the forum )