Author Topic: High Pingers to PBCup and -ch1ll- Servers Speak Up! (Read 7106 times)

XtremeBain · « **on:** May 18, 2006, 11:27:02 PM »

If you've been experiencing very high pings (I know a lot of mid-west players have reported this) please send me a PM on IRC or the forums with your IP address.

I'm going to present some of the peering issues to my service provider so we can hopefully get certain connections re-routed from the datacenter.

Dirty_Taco · « **Reply #1 on:** May 19, 2006, 10:13:48 AM »

Post removed

bitmate · « **Reply #2 on:** May 19, 2006, 10:21:33 AM »

I'm also experiencing those thin black lines on my netgraph.
My ping is nearly the same as few weeks ago, but I've the feeling that everything's getting choppy.
I don't know if it's the same on Insane or PBCup servers, but it's happening on the ch1ll servers.

IP: 217.225.* (Provider: Deutsche Telekom AG Germany)

Smokey · « **Reply #3 on:** May 20, 2006, 01:29:13 AM »

Yes.. i really want to speak to them about it to. After you say something if they dont get right on it ill complain about it also.

Playah · « **Reply #4 on:** May 20, 2006, 01:36:11 PM »

I also got this packetloss on the ch1ll match/ pub servers. Ping hasnt changed. On the insane servers i dont get packetloss as i tested today.

So what are you going to do for the pbcup finals tomorrow?

[b]east · « **Reply #5 on:** May 21, 2006, 04:31:57 AM »

80.139.*(provider Deutsche Telekom AG Germany)
got a high ping and many laags ch1ll server since a few days

lekky · « **Reply #6 on:** May 21, 2006, 04:40:52 AM »

i've been getting fairly regular black lines recently too.

bitmate · « **Reply #7 on:** May 21, 2006, 04:51:00 AM »

That's what my net graph looks like...

note: The big black block is because of the "screenshot lag"

lekky · « **Reply #8 on:** May 21, 2006, 04:53:18 AM »

yeah, mines almost exactly hte same as bitmates. (including screenshot lag :/ )

Dirty_Taco · « **Reply #9 on:** May 21, 2006, 12:34:20 PM »

Post removed

Gibb · « **Reply #10 on:** May 24, 2006, 12:58:53 PM »

ME ME ME ME ME.

67.190.5.92

I ping from 140-170, I live in Colorado, my provider is Comcast. If I go down to Colorado Springs (100 miles south of where I live in Boulder) my parents connection through Adelphia yields a 70 ping. It's messed up. Fix this crap or I WALK!

SkateR · « **Reply #11 on:** May 26, 2006, 10:18:55 PM »

I ping 30 yet...

http://tinypic.com/view/?pic=10rsk5f

----
http://tinypic.com/view/?pic=10rskcl

Yea.

bitmate · « **Reply #12 on:** May 27, 2006, 08:00:03 AM »

Instead of getting better, the server packet losses are getting worse and worse for me.

Server: -ch1ll- US-East Match 2 - www.ch1ll.com

AgentSmith · « **Reply #13 on:** May 27, 2006, 09:53:34 AM »

My Problem withthe server is NOT the ping (It's around 150, what is normal for me on American Servers), but:

We were in Clanmatch with [CC] and we had to play 1 map on the ch1ll server, and you didnt see ppl movin in 1 motion, you saw like 1 frame per second of where the opponent actually is, what made it really hard to hit him with a paintball, that situation made us lose the map really high :-(

XtremeBain · « **Reply #14 on:** May 27, 2006, 12:24:02 PM »

bitmate: If I could get you to run a few commands on your end to help identify the problem.
First off, we'll need to grab a decent size sample of pings to the server. 100 is a good start, the more the better.
At a DOS prompt: (Start->Run; Open: cmd; OK)
ping -n 100 castle1.pbcup.com

This will spam a lot, but I only need the last four lines.

Code: [Select]

Ping statistics for castle1.pbcup.com:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 50ms, Average = 35ms

Next I need the entire traceroute from your point of view:
tracert castle1.pbcup.com

Finally I need your IP so that I can run a traceroute from the server's point of view.

Once you've got all that information, send me a PM on the forum, or an e-mail at XtremeBain@ch1ll.com

I'll raise the issue with my network support group.
I've already got a packetloss ticket created that will be looked into Monday, your's is much much worse.

AgentSmith and others: if you'd like to do the same go ahead. The more data I collect, the better case I can prevent.

Termin8oR · « **Reply #15 on:** May 27, 2006, 02:32:23 PM »

I havent had bad ping on PBCup/ch1ll servers because I cant play on them yet!
But with All Seeing Eye I see that my ping would be 75-90.

lekky · « **Reply #16 on:** May 27, 2006, 05:16:11 PM »

pings are not the problem termi, its the packetloss that causes the lag.

jitspoe · « **Reply #17 on:** May 27, 2006, 08:13:21 PM »

From my parent's computer in SC:

Quote

Ping statistics for 69.72.221.162:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 55ms, Average = 33ms

bitmate · « **Reply #18 on:** May 28, 2006, 04:46:28 AM »

ok Jesse, I've send you an e-mail with all the details given.

Hobo · « **Reply #19 on:** June 05, 2006, 05:23:23 PM »

Since I'm probably one of the farest from most servers... everything goes through Seattle for me.

Ping statistics for 69.72.221.162:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 177ms, Average = 162ms

from: 69.178.120.163

For comparison to EV1 server: 216.127.68.86
Ping statistics for 216.127.68.86:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 104ms, Average = 84ms

Tracing route to castle1.pbcup.com [69.72.221.162]
over a maximum of 30 hops:

1 * * * Request timed out.
2 5 ms 7 ms 7 ms 225-188-165-209.gci.net [209.165.188.225]
3 23 ms 6 ms 7 ms 161-128-165-209.gci.net [209.165.128.161]
4 9 ms 7 ms 5 ms 136-128-165-209.gci.net [209.165.128.136]
5 34 ms 34 ms 67 ms 170-129-165-209.gci.net [209.165.129.170]
6 35 ms 34 ms 35 ms 221-129-165-209.gci.net [209.165.129.221]
7 36 ms 33 ms 35 ms acr2-so-1-2-0.Seattle.savvis.net [208.172.81.153]
8 61 ms 59 ms 63 ms dcr2-so-1-0-0.Denver.savvis.net [204.70.193.58]

9 141 ms 145 ms 145 ms dcr1-so-7-0-0.Chicago.savvis.net [204.70.192.134]
10 164 ms 143 ms 143 ms dcr2-so-5-0-0.Chicago.savvis.net [204.70.192.46]

11 164 ms 163 ms 165 ms aer1-ge-5-16.newyork.savvis.net [204.70.193.82]

12 160 ms 163 ms 161 ms fortressitx.NewYork.savvis.net [206.24.195.134]

13 161 ms 161 ms 161 ms 65.98.0.227
14 160 ms 163 ms 162 ms castle1.pbcup.com [69.72.221.162]

Trace complete.