[Matt]

Like always, just saying "MY PING HAS RISEN HALP!!!" is very unhelpful. Tracert Tracert Tracert.

Double post

I decided to do some traceroutes from the server.

DK yours seems fine.

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.270 ms 0.335 ms 0.390 ms 2 100-42-223-193.static.webnx.com (100.42.223.193) 0.498 ms 0.604 ms 0.760 ms 3 100-42-223-141.static.webnx.com (100.42.223.141) 0.532 ms 0.692 ms 0.789 ms 4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.779 ms 0.938 ms 1.007 ms 5 te0-4-0-7.mpd21.lax01.atlas.cogentco.com (154.54.84.109) 0.771 ms te0-2-0-7.mpd21.lax01.atlas.cogentco.com (154.54.24.61) 0.836 ms te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.733 ms 6 te8-2.ccr01.lax05.atlas.cogentco.com (154.54.0.218) 0.734 ms te7-8.ccr01.lax05.atlas.cogentco.com (154.54.30.190) 0.555 ms te9-1.ccr01.lax05.atlas.cogentco.com (154.54.44.138) 0.677 ms 7 te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.471 ms te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 18.451 ms te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.474 ms 8 pos-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.57) 3.963 ms 19.377 ms 3.955 ms 9 68.86.86.118 (68.86.86.118) 34.795 ms 58.905 ms 34.681 ms 10 pos-1-6-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.85.154) 54.464 ms 70.459 ms 70.447 ms 11 he-0-2-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.89.145) 87.229 ms 87.272 ms 86.576 ms 12 so-1-1-0-0-ar03.audubon.nj.panjde.comcast.net (68.86.92.162) 72.144 ms 87.750 ms 87.606 ms 13 xe-0-1-2-0-ar03.absecon.nj.panjde.comcast.net (68.86.152.114) 74.183 ms ae-1-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.63.178) 74.183 ms so-3-0-0-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.62.214) 73.904 ms 14 xe-11-0-0-0-sur01.eatontown.nj.panjde.comcast.net (68.85.62.78) 77.961 ms 77.525 ms 94.490 ms 15 te-17-10-cdn07.eatontown.nj.panjde.comcast.net (68.87.214.130) 82.989 ms 85.277 ms 90.150 ms

Raptor yours is outside of our providers network and seems like an ISP problem. Complain to them.

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.301 ms 0.334 ms 0.433 ms 2 100-42-223-193.static.webnx.com (100.42.223.193) 0.520 ms 0.678 ms 0.785 ms 3 100-42-223-141.static.webnx.com (100.42.223.141) 0.512 ms 0.711 ms 0.823 ms 4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.765 ms 1.014 ms 1.059 ms 5 te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113) 0.747 ms te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 0.687 ms te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113) 0.794 ms 6 38.104.210.162 (38.104.210.162) 182.020 ms 182.018 ms 182.027 ms 7 * * * 8 58.27.14.158 (58.27.14.158) 418.627 ms 418.686 ms 418.744 ms 9 tengig4-4-ph.telecomplus.net (196.20.254.170) 308.801 ms 308.873 ms 308.022 ms

Oh and here's James

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.289 ms 0.379 ms 0.424 ms 2 100-42-223-177.static.webnx.com (100.42.223.177) 0.468 ms 0.656 ms 0.740 ms 3 100-42-223-145.static.webnx.com (100.42.223.145) 0.549 ms 0.735 ms 0.799 ms 4 10gigabitethernet1-1.core1.lax2.he.net (216.218.196.189) 0.337 ms 0.428 ms 0.475 ms 5 10gigabitethernet2-1.core1.lax1.he.net (72.52.92.121) 0.371 ms 6.414 ms 0.420 ms 6 LANGBBPC01GEX0200A001.R2.LA.COX.NET (206.223.123.42) 1.179 ms 0.758 ms 1.205 ms 7 kscydsrj02-ge610.rd.ks.cox.net (68.1.1.197) 45.203 ms 46.019 ms 45.836 ms 8 70.183.71.66 (70.183.71.66) 50.894 ms 70.183.71.62 (70.183.71.62) 45.220 ms 70.183.71.66 (70.183.71.66) 51.167 ms 9 70.183.66.6 (70.183.66.6) 58.095 ms ip70-183-65-102.ks.ks.cox.net (70.183.65.102) 54.299 ms 54.241 ms 10 70.183.71.126 (70.183.71.126) 53.213 ms 70.183.71.122 (70.183.71.122) 53.772 ms 70.183.71.126 (70.183.71.126) 52.815 ms

So what's that mean? lol...

Well, now my ping is increased by 20-40. So I would say something wrong still?

[Matt]

DK the ping increase is way outside of WebNX's network. WebNX's transit provider CogentCO hits Comcast at 3ms (I assume your ISP). Looks like an ISP problem to me.

Like always, just saying "MY PING HAS RISEN HALP!!!" is very unhelpful. Tracert Tracert Tracert.

Double post

I decided to do some traceroutes from the server.

DK yours seems fine.

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.270 ms 0.335 ms 0.390 ms 2 100-42-223-193.static.webnx.com (100.42.223.193) 0.498 ms 0.604 ms 0.760 ms 3 100-42-223-141.static.webnx.com (100.42.223.141) 0.532 ms 0.692 ms 0.789 ms 4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.779 ms 0.938 ms 1.007 ms 5 te0-4-0-7.mpd21.lax01.atlas.cogentco.com (154.54.84.109) 0.771 ms te0-2-0-7.mpd21.lax01.atlas.cogentco.com (154.54.24.61) 0.836 ms te0-3-0-7.mpd21.lax01.atlas.cogentco.com (154.54.43.253) 0.733 ms 6 te8-2.ccr01.lax05.atlas.cogentco.com (154.54.0.218) 0.734 ms te7-8.ccr01.lax05.atlas.cogentco.com (154.54.30.190) 0.555 ms te9-1.ccr01.lax05.atlas.cogentco.com (154.54.44.138) 0.677 ms 7 te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.471 ms te-0-9-0-4-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.113) 18.451 ms te-0-9-0-5-pe01.600wseventh.ca.ibone.comcast.net (66.208.229.117) 3.474 ms 8 pos-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.57) 3.963 ms 19.377 ms 3.955 ms 9 68.86.86.118 (68.86.86.118) 34.795 ms 58.905 ms 34.681 ms 10 pos-1-6-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.85.154) 54.464 ms 70.459 ms 70.447 ms 11 he-0-2-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.89.145) 87.229 ms 87.272 ms 86.576 ms 12 so-1-1-0-0-ar03.audubon.nj.panjde.comcast.net (68.86.92.162) 72.144 ms 87.750 ms 87.606 ms 13 xe-0-1-2-0-ar03.absecon.nj.panjde.comcast.net (68.86.152.114) 74.183 ms ae-1-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.63.178) 74.183 ms so-3-0-0-0-ar03.eastwindsor.nj.panjde.comcast.net (68.85.62.214) 73.904 ms 14 xe-11-0-0-0-sur01.eatontown.nj.panjde.comcast.net (68.85.62.78) 77.961 ms 77.525 ms 94.490 ms 15 te-17-10-cdn07.eatontown.nj.panjde.comcast.net (68.87.214.130) 82.989 ms 85.277 ms 90.150 ms

Raptor yours is outside of our providers network and seems like an ISP problem. Complain to them.

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.301 ms 0.334 ms 0.433 ms 2 100-42-223-193.static.webnx.com (100.42.223.193) 0.520 ms 0.678 ms 0.785 ms 3 100-42-223-141.static.webnx.com (100.42.223.141) 0.512 ms 0.711 ms 0.823 ms 4 te0-0-0-14.209.ccr21.lax04.atlas.cogentco.com (38.122.146.25) 0.765 ms 1.014 ms 1.059 ms 5 te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113) 0.747 ms te0-2-0-7.mpd22.lax01.atlas.cogentco.com (154.54.2.237) 0.687 ms te0-4-0-7.mpd22.lax01.atlas.cogentco.com (154.54.84.113) 0.794 ms 6 38.104.210.162 (38.104.210.162) 182.020 ms 182.018 ms 182.027 ms 7 * * * 8 58.27.14.158 (58.27.14.158) 418.627 ms 418.686 ms 418.744 ms 9 tengig4-4-ph.telecomplus.net (196.20.254.170) 308.801 ms 308.873 ms 308.022 ms

Oh and here's James

Code:

1 142-4-63-225.static.webnx.com (142.4.63.225) 0.289 ms 0.379 ms 0.424 ms 2 100-42-223-177.static.webnx.com (100.42.223.177) 0.468 ms 0.656 ms 0.740 ms 3 100-42-223-145.static.webnx.com (100.42.223.145) 0.549 ms 0.735 ms 0.799 ms 4 10gigabitethernet1-1.core1.lax2.he.net (216.218.196.189) 0.337 ms 0.428 ms 0.475 ms 5 10gigabitethernet2-1.core1.lax1.he.net (72.52.92.121) 0.371 ms 6.414 ms 0.420 ms 6 LANGBBPC01GEX0200A001.R2.LA.COX.NET (206.223.123.42) 1.179 ms 0.758 ms 1.205 ms 7 kscydsrj02-ge610.rd.ks.cox.net (68.1.1.197) 45.203 ms 46.019 ms 45.836 ms 8 70.183.71.66 (70.183.71.66) 50.894 ms 70.183.71.62 (70.183.71.62) 45.220 ms 70.183.71.66 (70.183.71.66) 51.167 ms 9 70.183.66.6 (70.183.66.6) 58.095 ms ip70-183-65-102.ks.ks.cox.net (70.183.65.102) 54.299 ms 54.241 ms 10 70.183.71.126 (70.183.71.126) 53.213 ms 70.183.71.122 (70.183.71.122) 53.772 ms 70.183.71.126 (70.183.71.126) 52.815 ms

can u explain to me in simpler terms what these numbers say to me...:oops:

[Matt]

Sure thing .

1-5 is our providers network (less than 1ms), 5 being the end of it
6 is Telekom Malaysia's network (182ms), which is pretty normal ping for that distance.
7 Can't be pinged, most likey an overloaded/congested router trying to do more important things than respond to our servers ping request.
8 TMNet Telekom Malaya (418ms), most likely high from hop 7 being congested.

As you can see our providers network is fine, the ping doesn't start to dramatically increase until well into Telekom Malaysia's network.

Double post

DK I'm going to monitor your ping for a bit longer, I noticed something that I might take to our provider if it turn's out to be anything.

DK I'm going to monitor your ping for a bit longer, I noticed something that I might take to our provider if it turn's out to be anything.

Alright, let me know if you get something. Thanks.

Hi Guys/Girls,

Box 2 will be going down to transfer the IP range to our new server. Expect some down time on the 24/7 servers, hopefully everything goes smoothly.

Edit: The IP range transfer is complete, the servers should be starting to come back online now.

Edit2: The servers should all be back up, let Bison or Me know if there is any problems.

Sniper server is still down. Is it gone permanently?

Sniper server is still down. Is it gone permanently?

This was from 4 months ago and no it is not gone permanently just wait for it to be up again.