Overclock.net › Forums › Software, Programming and Coding › Networking & Security › why is my ping acting like that?
New Posts  All Forums:Forum Nav:

why is my ping acting like that?

post #1 of 7
Thread Starter 
i have a problem where my ping keeps rising from ~60 in the morning on a uk server to 200+ in the evening.. thats the same for all servers (200 goes to 350, 150 goes to 250-300 and 40 goes up to 100 etc)

7:58am
tracert 85.234.148.66

Tracing route to 85-234-148-66.static.as29550.net [85.234.148.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 12 ms 14 ms 172.19.1.25
4 43 ms 42 ms 43 ms so-4-1-1.edge1.Marseille1.Level3.net [212.73.206
.49]
5 43 ms 43 ms 42 ms ae-3-4.bar1.Marseille1.Level3.net [4.69.148.9]
6 55 ms 54 ms 57 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
7 54 ms 56 ms 57 ms ae-11-51.car1.Paris1.Level3.net [4.69.139.194]
8 53 ms 54 ms 56 ms tiscali-level3-te.Paris1.Level3.net [4.68.110.12
2]
9 63 ms 82 ms 61 ms xe-1-3-0.lon21.ip4.tinet.net [89.149.183.145]
10 61 ms 62 ms 61 ms blueconnex-gw.ip4.tinet.net [77.67.67.138]
11 63 ms 64 ms 65 ms 92-48-121-214.static.as29550.net [92.48.121.214]

12 63 ms 63 ms 62 ms 85-234-148-66.static.as29550.net [85.234.148.66]

11:00am

tracert 85.234.148.66

Tracing route to 85-234-148-66.static.as29550.net [85.234.148.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 50 ms 26 ms 25 ms 172.19.1.25
4 59 ms 62 ms 56 ms so-4-1-1.edge1.Marseille1.Level3.net [212.73.206
.49]
5 91 ms 73 ms 64 ms ae-3-4.bar1.Marseille1.Level3.net [4.69.148.9]
6 71 ms 69 ms 79 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
7 73 ms 83 ms 85 ms ae-11-51.car1.Paris1.Level3.net [4.69.139.194]
8 89 ms 78 ms 72 ms tiscali-level3-te.Paris1.Level3.net [4.68.110.12
2]
9 74 ms 90 ms 82 ms xe-1-3-0.lon21.ip4.tinet.net [89.149.183.145]
10 76 ms 91 ms 81 ms blueconnex-gw.ip4.tinet.net [77.67.67.138]
11 87 ms 116 ms 89 ms 92-48-121-214.static.as29550.net [92.48.121.214]

12 75 ms 89 ms 84 ms 85-234-148-66.static.as29550.net [85.234.148.66]

3:48pm
tracert 85.234.148.66

Tracing route to 85-234-148-66.static.as29550.net [85.234.148.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 33 ms 44 ms 49 ms 172.19.1.25
4 82 ms 84 ms 95 ms so-4-1-1.edge1.Marseille1.Level3.net [212.73.206
.49]
5 114 ms 84 ms 82 ms ae-3-4.bar1.Marseille1.Level3.net [4.69.148.9]
6 104 ms 90 ms 84 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
7 96 ms 106 ms 90 ms ae-11-51.car1.Paris1.Level3.net [4.69.139.194]
8 105 ms 87 ms 82 ms tiscali-level3-te.Paris1.Level3.net [4.68.110.12
2]
9 108 ms 97 ms 110 ms xe-1-3-0.lon21.ip4.tinet.net [89.149.183.145]
10 120 ms 111 ms 109 ms blueconnex-gw.ip4.tinet.net [77.67.67.138]
11 109 ms 103 ms 91 ms 92-48-121-214.static.as29550.net [92.48.121.214]

12 88 ms 78 ms 103 ms 85-234-148-66.static.as29550.net [85.234.148.66]

5:58pm
tracert 85.234.148.66

Tracing route to 85-234-148-66.static.as29550.net [85.234.148.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 41 ms 44 ms 48 ms 172.19.1.25
4 148 ms 140 ms 161 ms so-4-1-1.edge1.Marseille1.Level3.net [212.73.206
.49]
5 154 ms 125 ms 157 ms ae-3-4.bar1.Marseille1.Level3.net [4.69.148.9]
6 159 ms 226 ms 168 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
7 89 ms 87 ms 85 ms ae-11-51.car1.Paris1.Level3.net [4.69.139.194]
8 197 ms 168 ms 164 ms tiscali-level3-te.Paris1.Level3.net [4.68.110.12
2]
9 163 ms 152 ms 210 ms xe-1-3-0.lon21.ip4.tinet.net [89.149.183.145]
10 149 ms 143 ms 192 ms blueconnex-gw.ip4.tinet.net [77.67.67.138]
11 185 ms 194 ms 216 ms 92-48-121-214.static.as29550.net [92.48.121.214]

12 159 ms 155 ms 162 ms 85-234-148-66.static.as29550.net [85.234.148.66]

8:27pm

tracert 85.234.148.66

Tracing route to 85-234-148-66.static.as29550.net [85.234.148.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 87 ms 119 ms * 172.19.1.25
4 173 ms 245 ms 249 ms so-4-1-1.edge1.Marseille1.Level3.net [212.73.206
.49]
5 209 ms 158 ms 167 ms ae-3-4.bar1.Marseille1.Level3.net [4.69.148.9]
6 219 ms 195 ms 232 ms ae-7-7.ebr1.Paris1.Level3.net [4.69.143.238]
7 164 ms 177 ms 197 ms ae-11-51.car1.Paris1.Level3.net [4.69.139.194]
8 196 ms 224 ms 331 ms tiscali-level3-te.Paris1.Level3.net [4.68.110.12
2]
9 249 ms 125 ms 182 ms xe-1-3-0.lon21.ip4.tinet.net [89.149.183.145]
10 150 ms 155 ms 165 ms blueconnex-gw.ip4.tinet.net [77.67.67.138]
11 221 ms 200 ms 237 ms 92-48-121-214.static.as29550.net [92.48.121.214]

12 170 ms 120 ms 189 ms 85-234-148-66.static.as29550.net [85.234.148.66]


that, ofc, makes tf2 unplayable, could anybody tell the problem or how to solve it?
oh and, i dont make any downloads or have any other one on the network, its a wired router with 1 port to my pc
Edited by WildEast - 1/16/11 at 4:56am
Budget Gaming Rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II x4 955 @ 3.4GHz MSI 870A-G54 Sapphire HD 4830 1GB @ 740/1080Mhz Kingston HyperX 2x2048 MB 1600MHz 
Hard DriveOSMonitorPower
Samsung F3 1.5TB Windows 7 Ultimate x64 Samsung 2233rz 120Hz 22" LCD HEC-600TE-2WX 
MouseMouse PadAudioOther
Logitech G400 Steelseries Qck+ Asus Xonar DG 5.1 JVC HA-RX700 Headphone 
  hide details  
Reply
Budget Gaming Rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II x4 955 @ 3.4GHz MSI 870A-G54 Sapphire HD 4830 1GB @ 740/1080Mhz Kingston HyperX 2x2048 MB 1600MHz 
Hard DriveOSMonitorPower
Samsung F3 1.5TB Windows 7 Ultimate x64 Samsung 2233rz 120Hz 22" LCD HEC-600TE-2WX 
MouseMouse PadAudioOther
Logitech G400 Steelseries Qck+ Asus Xonar DG 5.1 JVC HA-RX700 Headphone 
  hide details  
Reply
post #2 of 7
Your ping times get worse as the day goes on. My first guess is you are on cable, and more people are getting on line. Higher ping times can be caused by errors on the cirucit, and maxing out the bandwidth on a circuit or node.

If your ping times are good early tomorrow morning or in the middle of the night, I would rule out errors on the circuit.
1090T
(13 items)
 
  
CPUMotherboardGraphicsRAM
1090T GA-890FXA-UD5 HIS 4670 G.SKILL ECO Series 4GB (1600) 
Hard DriveOSPowerCase
WD Black (Raid 0) Win 7 Home Premium x64 CORSAIR 850W COOLER MASTER Storm Sniper 
  hide details  
Reply
1090T
(13 items)
 
  
CPUMotherboardGraphicsRAM
1090T GA-890FXA-UD5 HIS 4670 G.SKILL ECO Series 4GB (1600) 
Hard DriveOSPowerCase
WD Black (Raid 0) Win 7 Home Premium x64 CORSAIR 850W COOLER MASTER Storm Sniper 
  hide details  
Reply
post #3 of 7
Quote:
Originally Posted by Thorn-Blade;12029880 
Your ping times get worse as the day goes on. My first guess is you are on cable, and more people are getting on line. Higher ping times can be caused by errors on the cirucit, and maxing out the bandwidth on a circuit or node.

If your ping times are good early tomorrow morning or in the middle of the night, I would rule out errors on the circuit.

This, as more people logon, your shared speed begins getting split up and the allocation of bandwidth gets more difficult and complex. This computational time can actually increase your lag.


If you're not on college or school net then i would consult your ISP because they are allocating bandwidth elsewhere when they should not be.
Bernard
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 @ 3.71 Ghz | 1.17v Rampage III Extreme EVGA GTX 580 Corsair Dominators GTX 6gb 1925MHz 7-7-7-20 
Hard DriveOptical DriveOSMonitor
64Gb C300 SATA 6 Gb/s, 2 x 320 Gb F4's RAID 0 ASUS 24x -_- Windows 7 Home(Who needs ultimate?!) ASUS VH226H 21.5 Inch 1080p 
PowerCaseMouseMouse Pad
Corsair HX1000 + Custom Sleeving NZXT Tempest Evo Razer Naga NONE 
  hide details  
Reply
Bernard
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 950 @ 3.71 Ghz | 1.17v Rampage III Extreme EVGA GTX 580 Corsair Dominators GTX 6gb 1925MHz 7-7-7-20 
Hard DriveOptical DriveOSMonitor
64Gb C300 SATA 6 Gb/s, 2 x 320 Gb F4's RAID 0 ASUS 24x -_- Windows 7 Home(Who needs ultimate?!) ASUS VH226H 21.5 Inch 1080p 
PowerCaseMouseMouse Pad
Corsair HX1000 + Custom Sleeving NZXT Tempest Evo Razer Naga NONE 
  hide details  
Reply
post #4 of 7
That's not really a direct ping, that's a Route Tracing. You'll get time-outs and high responses. Some systems are designed to ignore a ping request, hench the time-out. Others have high traffice, hench the large latency.

It's all normal.
    
CPUMotherboardGraphicsRAM
Intel Overdrive 486DX4 100Mhz Digital Venturis 466 S3 Trio 32 1MB 68MB 72 Pin SIMMs 
Hard DriveOptical DriveOSMonitor
1.2Gb & 270Mb 32X CD-ROM Windows 98 SE LG 23" Flatron 
KeyboardPowerCaseMouse
Microsoft PS/2 Lite-On Digital Venturis 466 Logitech PS/2 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel Overdrive 486DX4 100Mhz Digital Venturis 466 S3 Trio 32 1MB 68MB 72 Pin SIMMs 
Hard DriveOptical DriveOSMonitor
1.2Gb & 270Mb 32X CD-ROM Windows 98 SE LG 23" Flatron 
KeyboardPowerCaseMouse
Microsoft PS/2 Lite-On Digital Venturis 466 Logitech PS/2 
  hide details  
Reply
post #5 of 7
Thread Starter 
Quote:
Originally Posted by killabytes;12030132 
That's not really a direct ping, that's a Route Tracing. You'll get time-outs and high responses. Some systems are designed to ignore a ping request, hench the time-out. Others have high traffice, hench the large latency.

It's all normal.

it actually does ping same as the trace routes
today morning
ping 85.234.148.66

Pinging 85.234.148.66 with 32 bytes of data:
Reply from 85.234.148.66: bytes=32 time=62ms TTL=51
Reply from 85.234.148.66: bytes=32 time=62ms TTL=51
Reply from 85.234.148.66: bytes=32 time=63ms TTL=51
Reply from 85.234.148.66: bytes=32 time=63ms TTL=51

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

right now
ping 85.234.148.66

Pinging 85.234.148.66 with 32 bytes of data:
Reply from 85.234.148.66: bytes=32 time=229ms TTL=51
Reply from 85.234.148.66: bytes=32 time=195ms TTL=51
Reply from 85.234.148.66: bytes=32 time=207ms TTL=51
Reply from 85.234.148.66: bytes=32 time=217ms TTL=51

Ping statistics for 85.234.148.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 229ms, Average = 212ms

so, what should i tell my isp? to allocate bandwidth more on my line instead of other lines :|?
Budget Gaming Rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II x4 955 @ 3.4GHz MSI 870A-G54 Sapphire HD 4830 1GB @ 740/1080Mhz Kingston HyperX 2x2048 MB 1600MHz 
Hard DriveOSMonitorPower
Samsung F3 1.5TB Windows 7 Ultimate x64 Samsung 2233rz 120Hz 22" LCD HEC-600TE-2WX 
MouseMouse PadAudioOther
Logitech G400 Steelseries Qck+ Asus Xonar DG 5.1 JVC HA-RX700 Headphone 
  hide details  
Reply
Budget Gaming Rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II x4 955 @ 3.4GHz MSI 870A-G54 Sapphire HD 4830 1GB @ 740/1080Mhz Kingston HyperX 2x2048 MB 1600MHz 
Hard DriveOSMonitorPower
Samsung F3 1.5TB Windows 7 Ultimate x64 Samsung 2233rz 120Hz 22" LCD HEC-600TE-2WX 
MouseMouse PadAudioOther
Logitech G400 Steelseries Qck+ Asus Xonar DG 5.1 JVC HA-RX700 Headphone 
  hide details  
Reply
post #6 of 7
No it doesn't.

A ping request goes from your PC to a Server. A trace route goes from Your PC to a single server, then nothing more than server tracing.
    
CPUMotherboardGraphicsRAM
Intel Overdrive 486DX4 100Mhz Digital Venturis 466 S3 Trio 32 1MB 68MB 72 Pin SIMMs 
Hard DriveOptical DriveOSMonitor
1.2Gb & 270Mb 32X CD-ROM Windows 98 SE LG 23" Flatron 
KeyboardPowerCaseMouse
Microsoft PS/2 Lite-On Digital Venturis 466 Logitech PS/2 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel Overdrive 486DX4 100Mhz Digital Venturis 466 S3 Trio 32 1MB 68MB 72 Pin SIMMs 
Hard DriveOptical DriveOSMonitor
1.2Gb & 270Mb 32X CD-ROM Windows 98 SE LG 23" Flatron 
KeyboardPowerCaseMouse
Microsoft PS/2 Lite-On Digital Venturis 466 Logitech PS/2 
  hide details  
Reply
post #7 of 7
Depending on what he pings along the trace route; yes it will be the same to that end device.

"A ping request goes from your PC to a Server. A trace route goes from Your PC to a single server, then nothing more than server tracing."

Looks like you said the same thing twice. Yes a ping goes from your PC to a server, and no a traceroute doesn't just go from your PC to a single server. A trace route does a new ping to each device along the way to the end destination. As each new hop is added, the round trip time should increment.

http://www.tek-tips.com/faqs.cfm?fid=381

Tracing route to www.l.google.com [74.125.45.105]
over a maximum of 30 hops:

1 9 ms 8 ms 10 ms 10.185.0.1
2 19 ms 13 ms 10 ms 96-34-65-38.static.unas.sc.charter.com [96.34.65.38]
3 11 ms 10 ms 11 ms 96-34-64-92.static.spbg.sc.charter.com [96.34.64.92]
4 10 ms 12 ms 13 ms dtr01spbgsc-gbe-8-1.spbg.sc.charter.com [96.34.64.32]
5 12 ms 11 ms 13 ms 96-34-64-65.static.spbg.sc.charter.com [96.34.64.65]
6 29 ms 11 ms 15 ms dtr01spbgsc-tge-4-2.spbg.sc.charter.com [96.34.64.20]
7 12 ms 15 ms 13 ms 96-34-64-47.static.spbg.sc.charter.com [96.34.64.47]
8 31 ms 18 ms 17 ms 96-34-78-22.static.kgpt.tn.charter.com [96.34.78.22]
9 * * * Request timed out.
10 22 ms 30 ms 18 ms prr01atlnga-2-4.atln.ga.charter.com [96.34.3.81]
11 23 ms 19 ms 20 ms 96-34-150-30.static.unas.mo.charter.com [96.34.150.30]
12 18 ms 19 ms 19 ms 72.14.233.56
13 19 ms 20 ms 20 ms 209.85.254.243
14 24 ms 20 ms 33 ms 209.85.253.145
15 24 ms 23 ms 21 ms yx-in-f105.1e100.net [74.125.45.105]

Trace complete.

Pinging www.l.google.com [74.125.45.105] with 32 bytes of data:
Reply from 74.125.45.105: bytes=32 time=23ms TTL=50
Reply from 74.125.45.105: bytes=32 time=20ms TTL=50
Reply from 74.125.45.105: bytes=32 time=33ms TTL=50
Reply from 74.125.45.105: bytes=32 time=20ms TTL=50

Ping statistics for 74.125.45.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 33ms, Average = 24ms

If you look at the average ping, it is equal to the first round of ICMP packts in the trace and very close to the other two.
1090T
(13 items)
 
  
CPUMotherboardGraphicsRAM
1090T GA-890FXA-UD5 HIS 4670 G.SKILL ECO Series 4GB (1600) 
Hard DriveOSPowerCase
WD Black (Raid 0) Win 7 Home Premium x64 CORSAIR 850W COOLER MASTER Storm Sniper 
  hide details  
Reply
1090T
(13 items)
 
  
CPUMotherboardGraphicsRAM
1090T GA-890FXA-UD5 HIS 4670 G.SKILL ECO Series 4GB (1600) 
Hard DriveOSPowerCase
WD Black (Raid 0) Win 7 Home Premium x64 CORSAIR 850W COOLER MASTER Storm Sniper 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security
Overclock.net › Forums › Software, Programming and Coding › Networking & Security › why is my ping acting like that?