Digital Paint Discussion Board
Digital Paint Community => Clans, Matches, and Tournaments => PBCup => Topic started by: 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.
-
Post removed
-
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)
-
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.
-
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? ::)
-
80.139.*(provider Deutsche Telekom AG Germany)
got a high ping and many laags ch1ll server since a few days
-
i've been getting fairly regular black lines recently too.
-
That's what my net graph looks like...
note: The big black block is because of the "screenshot lag"
-
yeah, mines almost exactly hte same as bitmates. (including screenshot lag :/ )
-
Post removed
-
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!
-
I ping 30 yet...
http://tinypic.com/view/?pic=10rsk5f
----
http://tinypic.com/view/?pic=10rskcl
Yea.
-
Instead of getting better, the server packet losses are getting worse and worse for me.
Server: -ch1ll- US-East Match 2 - www.ch1ll.com
-
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 :-(
-
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.
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.
-
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.
-
pings are not the problem termi, its the packetloss that causes the lag.
-
From my parent's computer in SC:
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
-
ok Jesse, I've send you an e-mail with all the details given.
-
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.
-
Okay Hobo,
I submitted a ticket for your problem, however I think it's a problem with your isp.
Here's the traceroute from the server to you:
traceroute to 163-120-178-69.gci.net (69.178.120.163), 30 hops max, 38 byte packets
1 69.72.221.161 (69.72.221.161) 0.499 ms 0.402 ms 0.345 ms
2 69.57.170.1 (69.57.170.1) 100.039 ms 206.417 ms 6.721 ms
3 nyk-b1-link.telia.net (213.248.83.105) 0.868 ms 0.998 ms 0.595 ms
4 nyk-bb1-link.telia.net (213.248.82.205) 2.826 ms 1.136 ms 1.033 ms
5 nyk-b1-link.telia.net (213.248.82.14) 1.063 ms 1.126 ms 1.244 ms
6 sl-gw40-nyc-1-0.sprintlink.net (160.81.238.109) 0.991 ms 1.143 ms 1.113 ms
7 sl-bb26-nyc-9-0.sprintlink.net (144.232.13.49) 1.722 ms 1.461 ms 1.263 ms 8 sl-bb22-nyc-6-0.sprintlink.net (144.232.7.42) 1.325 ms 1.124 ms 1.021 ms
9 sl-bb21-chi-9-0.sprintlink.net (144.232.9.149) 24.765 ms 32.558 ms 184.670 ms
10 sl-bb25-chi-13-0.sprintlink.net (144.232.26.90) 32.632 ms 23.609 ms 23.796 ms
11 sl-bb21-sea-1-0.sprintlink.net (144.232.20.156) 79.754 ms 156.318 ms 70.389 ms
12 sl-gw14-sea-9-0.sprintlink.net (144.232.6.134) 70.211 ms 69.566 ms 69.485 ms
13 sl-gencomm-2-0.sprintlink.net (144.232.192.6) 69.679 ms 69.712 ms 69.508 ms
14 214-129-165-209.gci.net (209.165.129.214) 69.815 ms 69.572 ms 70.124 ms
15 69-129-165-209.gci.net (209.165.129.69) 102.465 ms 101.633 ms 102.660 ms
16 1-128-165-209.gci.net (209.165.128.1) 100.739 ms 101.240 ms 100.248 ms
17 34-128-165-209.gci.net (209.165.128.34) 101.942 ms 101.418 ms 101.892 ms
18 * * *