My ping is so bad...

Randy · Post by **Randy** » Mon Oct 11, 2004 2:13 pm

that it really affects my game play my average ping in sg is 139.. which IMO is too high to keep playing.

My ping in dc days used to be between 70- 90 and on local sevrers 40-60

for the past year it has been 110 - 150 and on local servers 60 - 90

even though i dont think my isp will do anything I am going to call my isp one last time and try and resolve this

Post by **YeOldeStonecat** » Mon Oct 11, 2004 2:15 pm

You using the same ISP that Immy does? I remember last winter, for about a month or more, his pings were all over the place...before they seemed to fix whatever his issue was.

Randy · Post by **Randy** » Mon Oct 11, 2004 2:20 pm

shaw ... im not sure about immy.

for some reason they gave me a new ip and ever since it has been

Randy · Post by **Randy** » Mon Oct 11, 2004 2:22 pm

funnay tech is checking connection says sumthin dropped off

Randy · Post by **Randy** » Mon Oct 11, 2004 2:47 pm

sweet this time the tech agreed that my pings suck!

we believe that its

a) modem
b) crappy ethernet cable
c) increase signal from the pole
d) neighbours live porno web cam

Going to get this fixed!

funny thing is this is similar to the problems that i had in jan 2000 which brought me to speedguide.

Chris · Post by **Chris** » Mon Oct 11, 2004 3:40 pm

Randy wrote:sweet this time the tech agreed that my pings suck!

funny thing is this is similar to the problems that i had in jan 2000 which brought me to speedguide.

Does this mean your gonna leave now?

jk

Immortal · Post by **Immortal** » Mon Oct 11, 2004 3:45 pm

I use rogers, he uses shaw! That and he is around 6 hrs flight time away from me! Damn those west coasters!

Randy · Post by **Randy** » Tue Oct 12, 2004 4:26 pm

Chris wrote:Does this mean your gonna leave now?

jk

in a sense yeah if i dont get this resolved there really is not much point in playing on sg server

UPDATE:
swapped out modem today and unfortunately i got this
Pinging 69.24.42.69 with 32 bytes of data:

Reply from 69.24.42.69: bytes=32 time=109ms TTL=117
Reply from 69.24.42.69: bytes=32 time=108ms TTL=117
Reply from 69.24.42.69: bytes=32 time=108ms TTL=117
Reply from 69.24.42.69: bytes=32 time=108ms TTL=117
Reply from 69.24.42.69: bytes=32 time=111ms TTL=117
Reply from 69.24.42.69: bytes=32 time=110ms TTL=117
Reply from 69.24.42.69: bytes=32 time=109ms TTL=117
Reply from 69.24.42.69: bytes=32 time=146ms TTL=117
Reply from 69.24.42.69: bytes=32 time=169ms TTL=117
Reply from 69.24.42.69: bytes=32 time=146ms TTL=117
Reply from 69.24.42.69: bytes=32 time=123ms TTL=117
Reply from 69.24.42.69: bytes=32 time=112ms TTL=117
Reply from 69.24.42.69: bytes=32 time=112ms TTL=117
Reply from 69.24.42.69: bytes=32 time=121ms TTL=117
Reply from 69.24.42.69: bytes=32 time=108ms TTL=117
Reply from 69.24.42.69: bytes=32 time=108ms TTL=117
Reply from 69.24.42.69: bytes=32 time=193ms TTL=117
Reply from 69.24.42.69: bytes=32 time=116ms TTL=117
Reply from 69.24.42.69: bytes=32 time=109ms TTL=117
Reply from 69.24.42.69: bytes=32 time=109ms TTL=117

Ping statistics for 69.24.42.69:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 193ms, Average = 121ms

Evilone · Post by **Evilone** » Tue Oct 12, 2004 5:09 pm

one time with my cable internet it started getting real bad pings, I kept calling cox

telling them its ****ty and to fix it. They sent some guy over but he didnt' fix it. They finially firgured it out, Everyone was getting routed to one point somewhere down there line and slowing everyone up. might be what is happening to yours?

Chris · Post by **Chris** » Tue Oct 12, 2004 6:33 pm

Randy wrote:in a sense yeah if i dont get this resolved there really is not much point in playing on sg server

Bummer, my pings are not much better, I used to be around 75, and since the speed increases my ping to the game server are averaging 96.

Tracing route to 69.24.42.69 over a maximum of 30 hops

1 56 ms 55 ms 56 ms os-dsl-0256.bmts.com [216.183.153.1]
2 57 ms 57 ms 56 ms 216.183.131.13
3 64 ms 72 ms 67 ms bardisr01-atm6-1-0-49.in.bellnexxia.net [206.108
.111.81]
4 71 ms 67 ms 66 ms barcorr01-fe5-0-0.in.bellnexxia.net [64.230.229.
133]
5 65 ms 66 ms 68 ms 64.230.234.85
6 65 ms 64 ms 65 ms 64.230.242.194
7 63 ms 63 ms 63 ms bx3-toronto12-pos4-0.in.bellnexxia.net [206.108.
107.230]
8 64 ms 67 ms 69 ms if-7-0.core1.Scarborough.teleglobe.net [209.58.2
5.69]
9 86 ms 88 ms 82 ms if-8-0.core2.NewYork.Teleglobe.net [64.86.80.221
]
10 84 ms 90 ms 82 ms if-4-0.bb8.NewYork.Teleglobe.net [66.110.8.130]

11 89 ms 86 ms 85 ms ix-9-0.bb8.NewYork.Teleglobe.net [207.45.198.74]

12 85 ms 94 ms 107 ms 0.so-6-0-0.XL1.NYC9.ALTER.NET [152.63.18.226]
13 89 ms 95 ms 94 ms 0.so-6-0-0.CL1.BOS1.ALTER.NET [152.63.17.145]
14 98 ms 98 ms 93 ms 306.ATM7-0.GW7.BOS1.ALTER.NET [152.63.21.177]
15 103 ms 93 ms 93 ms pt2pt-gw.customer.ALTER.NET [65.217.198.246]
16 99 ms 100 ms 96 ms 66-159-131-106.ptr.p2pa.com [66.159.131.106]
17 94 ms 101 ms 94 ms 69.24.42.69

Trace complete.
Routing around New York and Boston seam to be the problem for me, most likely where yours is hanging also.
Whats your traceroute look like?

Randy · Post by **Randy** » Tue Oct 12, 2004 6:39 pm

Evilone wrote:one time with my cable internet it started getting real bad pings, I kept calling cox telling them its ****ty and to fix it. They sent some guy over but he didnt' fix it. They finially firgured it out, Everyone was getting routed to one point somewhere down there line and slowing everyone up. might be what is happening to yours?

no doubt!

I got a new ip ( bumped to 2nd class)
monthly isp charge dropped 20$ a month < wots up wit dat?

new super high speed comes out and costs what reg hs used to cost ..hmmmm

OH YAH > check this shizzle > I go to get replacement modem and they give me this modem thats all beat and scratched I look at the power cord and i see chew marks and about 2 inches of exposed sheilding. I walk back to isp service desk:
I say: "HEY whats with this old ass modem?

Receptionist lady says:"oh yeah we just replace used with used, but dont worry its all tested and works fine

".

I said: " oh yah well look at this cord!. I want a new modem".

new modem does nuthin

ahwell I kinda knew that it wouldnt.

Randy · Post by **Randy** » Tue Oct 12, 2004 6:43 pm

tracert 69.24.42.69

Tracing route to 69-24-42-69.ptr.p2pa.com [69.24.42.69]
over a maximum of 30 hops:

1 59 ms 24 ms 24 ms 24.69.212.1
2 27 ms 29 ms 29 ms rd2cv-ge4-2.gv.shawcable.net [64.59.161.3]
3 51 ms 30 ms 29 ms rc1wh-atm0-0-1.vc.shawcable.net [66.163.76.101]

4 31 ms 28 ms 30 ms POS5-0.GW3.VAN1.ALTER.NET [205.150.222.125]
5 56 ms 29 ms 29 ms 0.so-1-0-0.XL2.VAN1.ALTER.NET [152.63.137.134]
6 31 ms 29 ms 30 ms 0.so-7-0-0.TL2.VAN1.ALTER.NET [152.63.138.90]
7 107 ms 107 ms 107 ms 0.so-2-2-0.TL2.NYC9 PREYS ASS JAMM.ALTER.NET [152.63.0.178]
8 133 ms 113 ms 114 ms 0.so-6-1-0.CL2.BOS1.ALTER.NET [152.63.17.118]
9 117 ms 113 ms 113 ms 307.ATM6-0.GW7.BOS1.ALTER.NET [152.63.21.181]
10 116 ms 113 ms 113 ms pt2pt-gw.customer.ALTER.NET [65.217.198.246]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 *

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\ass gravey\Rodentia dimentia> tracert 69.24.42.69

Tracing route to 69-24-42-69.ptr.p2pa.com [69.24.42.69]
over a maximum of 30 hops:

1 44 ms 23 ms 24 ms 24.69.212.
2 28 ms 30 ms 29 ms rd2cv-ge4-2.gv.shawcable.net [64.59.161.3]
3 53 ms 29 ms 29 ms rc1wh-atm0-0-1.vc.shawcable.net [66.163.76.101]

4 32 ms 28 ms 29 ms POS5-0.GW3.VAN1.ALTER.NET [205.150.222.125]
5 30 ms 30 ms 29 ms 0.so-1-0-0.XL2.VAN1.ALTER.NET [152.63.137.134]
6 54 ms 29 ms 30 ms 0.so-7-0-0.TL2.VAN1.ALTER.NET [152.63.138.90]
7 107 ms 107 ms 107 ms 0.so-2-2-0.TL2.NYC9 PREYS ASS JAMMER.ALTER.NET [152.63.0.178]
8 137 ms 114 ms 113 ms 0.so-6-1-0.CL2.BOS1.ALTER.NET [152.63.17.118]
9 116 ms 114 ms 113 ms 307.ATM6-0.GW7.BOS1.ALTER.NET [152.63.21.181]
10 140 ms 118 ms 117 ms pt2pt-gw.customer.ALTER.NET [65.217.198.246]
11 * * *

I THINK ME SEES THE PRB

*edit more bad ping

ping 69.24.42.69 -n 20

Pinging 69.24.42.69 with 32 bytes of data:

Reply from 69.24.42.69: bytes=32 time=111ms TTL=117
Reply from 69.24.42.69: bytes=32 time=112ms TTL=117
Reply from 69.24.42.69: bytes=32 time=804ms TTL=117
Reply from 69.24.42.69: bytes=32 time=187ms TTL=117
Reply from 69.24.42.69: bytes=32 time=112ms TTL=117
Reply from 69.24.42.69: bytes=32 time=684ms TTL=117
Reply from 69.24.42.69: bytes=32 time=116ms TTL=117
Reply from 69.24.42.69: bytes=32 time=135ms TTL=117
Reply from 69.24.42.69: bytes=32 time=129ms TTL=117
Reply from 69.24.42.69: bytes=32 time=137ms TTL=117
Reply from 69.24.42.69: bytes=32 time=138ms TTL=117
Reply from 69.24.42.69: bytes=32 time=114ms TTL=117
Reply from 69.24.42.69: bytes=32 time=157ms TTL=117
Reply from 69.24.42.69: bytes=32 time=115ms TTL=117
Reply from 69.24.42.69: bytes=32 time=128ms TTL=117
Reply from 69.24.42.69: bytes=32 time=140ms TTL=117
Reply from 69.24.42.69: bytes=32 time=130ms TTL=117
Reply from 69.24.42.69: bytes=32 time=130ms TTL=117
Reply from 69.24.42.69: bytes=32 time=148ms TTL=117
Reply from 69.24.42.69: bytes=32 time=142ms TTL=117

Ping statistics for 69.24.42.69:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 804ms, Average = 193ms

Chris · Post by **Chris** » Tue Oct 12, 2004 6:56 pm

Randy wrote:tracert 69.24.42.69

11 * * *

I THINK ME SEES THE PRB

Alternet....