|
| Author | Message / Information |
|
Snow_White
Quote | Reply | |
West Coast/Comcast
replied on: 12/7/2007 1:35:37 PM yeah, last night while playing I noticed my ping was higher then a player from Boston.... |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 12/8/2007 11:11:33 AM Should be fixed again. Kyrpt saids that one of their ISP keeps making changes without notifying them. They will talk with the ISP to try to avoid this in the future. we'll see... -d |
|
fuze
Quote | Reply | |
West Coast/Comcast
replied on: 12/8/2007 3:22:51 PM my ping is back to normal again. whew..now i can get back to playing. |
|
Snow_White
Quote | Reply | This message was updated on 1/15/2008 9:10:13 PM by Snow_White |
West Coast/Comcast
replied on: 1/15/2008 9:03:19 PM Tonight my ping is at 180... People from the East Coast have better pings then I do, and I live in the same State as the Server. I don't think this has ever been fixed for me.... How about you Dor? EDIT: Look at my Traceroute... they are sending me all over the place. Tracing route to CUSTOMER.VPLS.NET [209.11.247.42] over a maximum of 30 hops: 1 * <1 ms <1 ms 10.0.1.1 2 * * * Request timed out. 3 8 ms * * ge-1-2-ur01.sfpine.ca.sfba.comcast.net [68.87.19 7.209] 4 * 11 ms 11 ms te-9-3-ur02.sfpine.ca.sfba.comcast.net [68.87.19 2.241] 5 * 13 ms 12 ms pos-0-7-0-0-ar01.oakland.ca.sfba.comcast.net [68 .86.90.138] 6 13 ms 12 ms 11 ms pos-0-8-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.85] 7 21 ms 22 ms 21 ms te-0-2-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.84.49] 8 42 ms 40 ms 40 ms te-0-0-0-7-cr01.mclean.va.ibone.comcast.net [68. 86.84.70] 9 58 ms 54 ms 55 ms te-7-4-ar02.bearcreek.tx.houston.comcast.net [68 .86.91.78] 10 59 ms 55 ms 55 ms pos-0-9-0-0-cr01.denver.co.ibone.comcast.net [68 .86.85.118] 11 78 ms 81 ms 81 ms pos-0-14-0-0-cr01.chicago.il.ibone.comcast.net [ 68.86.85.106] 12 115 ms 122 ms * 204.70.144.2 13 200 ms 130 ms 99 ms 204.70.144.1 14 * 98 ms 409 ms 204.70.197.10 15 * 117 ms 116 ms cr1-tengig-0-7-3-0.losangeles.savvis.net [204.70 .193.105] 16 106 ms 102 ms 120 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193 .106] 17 123 ms 110 ms 109 ms s218058-1.savvis-internet.uslsan3-bsn.savvis.net [64.240.66.114] 18 108 ms 116 ms 125 ms VLAN3001.BR5.SNA1.VPLS.NET [66.186.32.238] 19 130 ms 121 ms 122 ms gig10-2.cr2.sna1.vpls.net [209.11.241.186] 20 108 ms 108 ms 124 ms CUSTOMER.VPLS.NET [209.11.247.42] Trace complete. |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 1/17/2008 9:40:37 AM Sorry princess, didn't see it.. still off? If so, then I will email this to krypt... Its a shame as my ping was down to 60 since xmas... which what it was on cod2 and uo. I had been runnng at 70-80 with cod4... I was hoping that our routing finally got resolved... -d |
|
SS1936
Quote | Reply | |
West Coast/Comcast
replied on: 1/17/2008 9:44:49 AM Can someone tell me again how to run tracert please... |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 1/17/2008 10:29:18 AM On WinXP: Click Start Select Run In the field type: cmd This brings up a black command console Type in on the command line > tracert 209.11.247.42 It'll spew the lines like above. Next right-click on the top part of the window the black command console. Choose Edit->Select All Repeat, but choose Edit->Copy Go to email, webpost, notepad and "paste" your results -d |
|
Wally_Aussie
Code 720 Quote | Reply | This message was updated on 1/18/2008 2:58:01 AM by Wally_Aussie |
West Coast/Comcast
replied on: 1/18/2008 2:57:14 AM Just as a point of comparision: >tracert 209.11.247.42 Tracing route to CUSTOMER.VPLS.NET [209.11.247.42] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms bendigo.gateway [192.168.0.1] 2 35 ms 34 ms 31 ms dsl-lns1.vic.chariot.net.au [203.87.84.48] 3 36 ms 33 ms 32 ms ge0-1-101.mel-pow-rt1.vic.chariot.net.au [203.87 .83.33] 4 37 ms 35 ms 37 ms nme-pow-ibo-zeu-1-ge-5-0.tpgi.com.au [220.244.22 9.189] 5 35 ms 33 ms 32 ms nme-nxg-ibo-zeu-1-pos-2-2.tpgi.com.au [202.7.162 .154] 6 50 ms 46 ms 45 ms syd-nxg-ibo-zeu-1-pos-8-3.tpgi.com.au [202.7.162 .13] 7 195 ms 198 ms 198 ms 207.114.154.9 8 198 ms 198 ms * peer-02-so-0-0-0-0.palo.twtelecom.net [64.129.24 8.19] 9 207 ms 212 ms 212 ms 10gigabitethernet1-1.core1.lax1.he.net [72.52.92 .22] 10 217 ms 205 ms 211 ms 10gigabitethernet1-1.core1.lax2.he.net [72.52.92 .122] 11 211 ms 215 ms 208 ms 216.218.135.147 12 219 ms 212 ms 212 ms VLAN3001.BR5.SNA1.VPLS.NET [66.186.32.238] 13 212 ms 211 ms 212 ms gig10-2.cr2.SNA1.VPLS.NET [209.11.241.186] 14 212 ms 211 ms 212 ms CUSTOMER.VPLS.NET [209.11.247.42] Trace complete. |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 1/18/2008 11:56:45 AM quote: So, to explain this for you all. Wally basically chews up about "45" ping to get to this hub in Sydney (syd-nxg-ibo-zeu-1-pos-8-3.tpgi.com.au ). He then loses another 150 crossing the water...(hop 7 = 198) to LA. From LA, he loses another 15-20 to SD. Wally's route is direct, but the ocean is what kills his ping. If the pacific cable is clogged, then it is worse for him. If you look at Snow White, the problem is that he originates in SF. Then his connection goes to LA, then off to the east coast and back to LA, then to SD. The whole east coast adds unnecessary ping. For some reason, just us SF guys on comcast keep getting this re-route. It makes no sense to us because we get to LA.. Then why not strait to SD. Prior to this I had a 60 ping which 45 of it was my house to LA. 15 or so to SD... So, if ping is an issue... look at your trace route. You can see where the block is. If it is the LA to SD connection, then our machine provider can probably influence it. If it is between your home and LA, then is is probably under the control of your ISP or someone in the route (like the ocean). -d |
|
Snow_White
Quote | Reply | |
West Coast/Comcast
replied on: 1/18/2008 12:35:44 PM Well, last night my Ping was back down to 60-70... which is normal for me... I used to run anywhere from 20-50 in UO & CoD2..... The high ping of 180-200 lasted a couple of nights.... I'll keep an eye on it again over the weekend and see how it is...... |
|
KaneNZ
The General Quote | Reply | |
West Coast/Comcast
replied on: 1/18/2008 1:53:01 PM Heres mine.. Just because i can... C:\Documents and Settings\Kane>tracert 209.11.247.42 Tracing route to CUSTOMER.VPLS.NET [209.11.247.42] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.1.1.1 2 66 ms 61 ms 59 ms 125-239-64-1.jetstream.xtra.co.nz [125.239.64.1] 3 * 91 ms 135 ms mdr-ip03e-3-1-0.akbr4.global-gateway.net.nz [202 .50.236.114] 4 69 ms 69 ms 67 ms ge6-3-1-42.akbr4.global-gateway.net.nz [202.50.2 36.113] 5 70 ms 69 ms 70 ms 202.50.232.166 6 223 ms 193 ms 194 ms so0-1-0.labr5.global-gateway.net.nz [202.50.232. 26] 7 225 ms 224 ms 193 ms so-1-0-0.lebr6.global-gateway.net.nz [202.50.232 .237] 8 193 ms 194 ms 195 ms gi1-13.mpd01.lax05.atlas.cogentco.com [154.54.12 .141] 9 225 ms 225 ms 225 ms vl3490.ccr02.lax01.atlas.cogentco.com [154.54.6. 189] 10 193 ms 194 ms * te3-4.ccr01.lax04.atlas.cogentco.com [154.54.2.2 38] 11 193 ms 193 ms 225 ms 38.101.117.219 12 226 ms 197 ms 199 ms VLAN3001.BR5.SNA1.VPLS.NET [66.186.32.238] 13 195 ms 194 ms 195 ms GIG10-2-1000M.CR2.SNA1.VPLS.NET [209.11.241.186] 14 195 ms 226 ms 225 ms CUSTOMER.VPLS.NET [209.11.247.42] Trace complete. C:\Documents and Settings\Kane> |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 1/19/2008 8:43:37 PM run that again Kane... Yours said that your problem is actually in NZ and not the ocean crossing... -d |
|
KaneNZ
The General Quote | Reply | |
West Coast/Comcast
replied on: 1/20/2008 12:16:20 AM Tried to run it again, But at the present point of time as it does quite often my ping is in the high 500's - 600's on our Servers. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Kane>tracert 209.11.247.42 Tracing route to CUSTOMER.VPLS.NET [209.11.247.42] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.1.1.1 2 60 ms 58 ms 59 ms 125-239-64-1.jetstream.xtra.co.nz [125.239.64.1] 3 * * 71 ms mdr-ip03e-3-1-0.akbr4.global-gateway.net.nz [202 .50.236.114] 4 676 ms 364 ms 363 ms ge6-3-1-42.akbr4.global-gateway.net.nz [202.50.2 36.113] 5 370 ms 366 ms 362 ms 202.50.232.166 6 495 ms * * so0-1-1.labr5.global-gateway.net.nz [203.96.120. 78] 7 480 ms 480 ms 520 ms so-1-0-0.lebr6.global-gateway.net.nz [202.50.232 .237] 8 514 ms 498 ms 497 ms gi1-3.mpd01.lax05.atlas.cogentco.com [154.54.13. 121] 9 515 ms 526 ms 529 ms vl3490.ccr02.lax01.atlas.cogentco.com [154.54.6. 189] 10 487 ms * 491 ms te3-4.ccr01.lax04.atlas.cogentco.com [154.54.2.2 38] 11 532 ms 524 ms 487 ms 38.101.117.219 12 525 ms 515 ms 522 ms VLAN3002.BR6.SNA1.VPLS.NET [66.186.32.118] 13 488 ms 488 ms 528 ms GIG14-7-1000M.CR2.SNA1.VPLS.NET [66.186.32.22] 14 516 ms 518 ms 533 ms CUSTOMER.VPLS.NET [209.11.247.42] Trace complete. C:\Documents and Settings\Kane> Ill do another when it settles down. |
|
dorian_rast
CoD:4/Server Administrator Quote | Reply | |
West Coast/Comcast
replied on: 1/20/2008 6:26:30 PM Aside from the huge ping... Your tracepath is strange... You hub where all the ping is still in NZ... An earlier hub "4 676 ms 364 ms 363 ms ge6-3-1-42.akbr4.global-gateway.net.nz" is causing tonights issue. However, look at the NZ and US hubs line 7 and line 8. There is only like 30 ping difference... I am wondering if you guys That makes no sense... Like Wally's, you should have most of your ping between the two. I am wondering if you guys are really on satelite or something... |
|
John Kerry
Quote | Reply | |
West Coast/Comcast
replied on: 5/19/2008 10:25:31 PM Im getting rerouted again... Stupid comcast. Tracing route to CUSTOMER.VPLS.NET [209.11.247.42] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 * * * Request timed out. 3 6 ms 7 ms * ge-9-2-ur01.maplegrove.mn.minn.comcast.net [68.8 5.166.57] 4 15 ms * 7 ms te-8-3-ur02.maplegrove.mn.minn.comcast.net [68.8 7.174.50] 5 8 ms 7 ms * te-2-1-ur01.anoka.mn.minn.comcast.net [68.87.174 .54] 6 7 ms 9 ms * te-8-3-ur02.anoka.mn.minn.comcast.net [68.87.174 .58] 7 6 ms * 8 ms te-2-1-ur01.hamlake.mn.minn.comcast.net [68.87.1 74.62] 8 6 ms * 7 ms te-8-3-ur02.hamlake.mn.minn.comcast.net [68.87.1 74.66] 9 8 ms * 8 ms te-2-2-ar02.roseville.mn.minn.comcast.net [68.87 .174.69] 10 26 ms 25 ms 28 ms te-0-0-0-4-cr01.omaha.ne.ibone.comcast.net [68.8 6.91.149] 11 36 ms 34 ms 35 ms pos-0-9-0-0-cr01.chicago.il.ibone.comcast.net [6 8.86.85.117] 12 71 ms 69 ms 70 ms pos-0-15-0-0-cr01.newyork.ny.ibone.comcast.net [ 68.86.85.101] 13 75 ms 76 ms 76 ms pos-0-15-0-0-cr01.mclean.va.ibone.comcast.net [6 8.86.85.89] 14 76 ms 75 ms 76 ms xe-3-1-0.was11.ip.tiscali.net [213.200.84.117] 15 134 ms 134 ms 135 ms so-0-0-0.lax22.ip.tiscali.net [213.200.80.93] 16 113 ms 114 ms 113 ms vpls-gw3.ip.tiscali.net [213.200.73.92] 17 114 ms 113 ms 116 ms VLAN2093.BR1.LAX1.VPLS.NET [74.222.141.21] 18 115 ms 124 ms 124 ms VLAN3002.BR6.SNA1.VPLS.NET [66.186.32.118] 19 116 ms 120 ms 119 ms GIG14-7-1000M.CR2.SNA1.VPLS.NET [66.186.32.22] 20 115 ms 119 ms 118 ms CUSTOMER.VPLS.NET [209.11.247.42] Trace complete. |
|
LinkBot
|
Gamers Wanted is looking for people to write game reviews and post news, |
|
|
| Tired of seeing ads? Click here to upgrade to Elite Membership! |
ChatArea.com Help & News Forums | Terms of Use | Contact ChatArea.com | Advertising
Powered By ChatArea.com - Get your free Society today! © Copyright 2003 Wewp!