Regarding any Server Lag issues

**Yamagata 1st MRB** · March 10, 2011

We're working on it, Maj. Parker stayed up all last night reinstalling the server. We'll let you know if there are any new developments.

**Stab N' Grab** · March 10, 2011

played for several hours today, not one bit of chop or lag whatever Parker did helped immensely

I have no arms BAR · March 10, 2011

YAY! :lol:

**Cozad** · March 11, 2011

i played for an hour or so this evening and it seemed just like any other night the last few nights. choppy and lots of rubber banding.

**Magoo** · March 12, 2011

I have been playing for a few hours since Major reinstalled everything and I haven't noticed the lag problems from before. Boutton has also confirmed that he hasn't seen the lag either. I will keep watching for any problems and report if I find anything but for now all seems well.

Edited March 12, 2011 by Magoo 1st MRB

I have no arms BAR · March 14, 2011

I have also noticed a marked improvement! Thanks for all your hard work command staff! Looks like I'm back to positive scores. :lol:

**Goodwin 1st MRB** · March 15, 2011

I just figured I would let you all know that today our pub has died a couple times.

I know, I know, you hear about it enough, but I figured I should alert you guys just in case.

I played for a bit in the early AM (around 8:30-9:30), and there were a few big burps of lag felt server wide (everyone would freeze in place for around 2-3 seconds) then be fine (not rubber-banding, but stopping in place). We had around 8-9 people at that point and the pub was gaining some steam, then I got the 'connection interrupted' error and was frozen and I figured it was the server restarting or something - there had been some pretty bad hiccups of lag prior to that, so I didn't think much of it. I left for around 3 minutes, came back and all was good once more, but the pub was empty for a considerable time.

Then Elf and I played for a bit, and a couple more joined in, so I took off (there were random burps of lag here and there, but fairly rare, and not consistent).

I just joined up around 11:35 or so (CST), and there were around 4-6 people in the pub (St.Denis included) - we were goofing on Donner, then there were some burps of lag again - one that lasted upwards of 8-10 seconds (showing the 'connection interrupted' error). That burp caused St.Denis' game to crash as well as another person to get booted due to timeout.

The game resumed normal play for about another 3-5 minutes, then the server went down entirely again.

*EDIT: Went back in the servers around 12pm - there were a few big spikes of lag again with the 'connection interrupted' error and the countdown timer - everyone was affected.

Edited March 15, 2011 by Goodwin 1st MRB

**Magoo** · March 15, 2011

The server keeps crashing. It crashed again at 2:20 PM EST.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 7 ms 7 ms 7 ms 10.240.184.117

3 8 ms 7 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 12 ms 13 ms 14 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 12 ms 12 ms 11 ms tge1-2-cr2.ewr2.choopa.net [66.55.128.34]

9 13 ms 13 ms 11 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

**Misenhimer** · March 15, 2011

ive been having issues aswell.

**Goodwin 1st MRB** · March 15, 2011

It's a steam update issue.

Other servers have been having the same issue because Steam had to update some shiz.

Should be fixed soon.

**Boutton 1st MRB** · March 22, 2011

Microsoft Windows [Version 6.1.7600]

C:\Users\David Boutton Jr> tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 8 ms 6 ms 11 ms dynamic-acs-24-101-205-1.zoominternet.net [24.10

1.205.1]

3 13 ms 21 ms 9 ms static-acs-72-23-3-177.zoominternet.net [72.23.3

.177]

4 13 ms 15 ms 17 ms static-acs-72-23-3-158.zoominternet.net [72.23.3

.158]

5 15 ms 14 ms 16 ms dynamic-acs-72-23-2-49.zoominternet.net [72.23.2

.49]

6 13 ms 15 ms 15 ms static-acs-24-154-0-185.zoominternet.net [24.154

.0.185]

7 15 ms 27 ms 24 ms te3-4.ccr01.pit02.atlas.cogentco.com [38.104.120

.145]

8 24 ms 25 ms 25 ms te0-0-0-5.ccr22.dca01.atlas.cogentco.com [154.54

.30.230]

9 27 ms 27 ms 27 ms te0-0-0-1.ccr22.iad02.atlas.cogentco.com [154.54

.26.134]

10 25 ms 25 ms 28 ms verio.iad01.atlas.cogentco.com [154.54.12.238]

11 26 ms 25 ms 27 ms ae-6.r20.asbnva02.us.bb.gin.ntt.net [129.250.3.1

09]

12 37 ms 37 ms 36 ms ae-6.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.8

]

13 35 ms 35 ms 35 ms ae-1.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.6

9]

14 35 ms 35 ms 39 ms xe-4-0-7.ar2.nyc3.us.nlayer.net [69.31.34.206]

15 56 ms 55 ms 33 ms ae1-70g.cr1.nyc3.us.nlayer.net [69.31.95.153]

16 35 ms 35 ms 35 ms ae2-110g.cr1.ewr1.us.nlayer.net [69.31.95.145]

17 36 ms 37 ms 47 ms as20473.xe-3-3-0.cr1.ewr1.us.nlayer.net [69.31.9

4.138]

18 34 ms 36 ms 34 ms tge1-2-cr2.ewr2.choopa.net [66.55.128.34]

19 35 ms 35 ms 35 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\David Boutton Jr>

I did this when I was at 400 ms in the server and I had the best ping of anyone on the server.

**Magoo** · March 22, 2011

Everyone seems to have a ping in the 500-800 range in the pub right now. Help us Obi-Wan Kenobi you're our only hope.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 11 ms 8 ms 7 ms 10.240.184.117

3 9 ms 9 ms 9 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 15 ms 13 ms 14 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 13 ms 13 ms 12 ms tge1-2-cr2.ewr2.choopa.net [66.55.128.34]

9 12 ms 11 ms 14 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

**M. Kim** · May 1, 2011

Server crashed today at around 10:40pm est. This is the second one I witnessed with the first around a week ago.

**Cozad** · May 1, 2011

it did the same thing around 11am EST as well.

**Kabasares** · July 14, 2011

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 3 ms 2 ms 1 ms 192.168.0.1

2 71 ms 44 ms 102 ms c-76-103-8-1.hsd1.ca.comcast.net [76.103.8.1]

3 18 ms 54 ms 27 ms te-7-3-ur02.sfmission.ca.sfba.comcast.net [68.87

.197.101]

4 48 ms 38 ms 62 ms te-1-10-0-3-ar01.oakland.ca.sfba.comcast.net [68

.85.154.50]

5 36 ms 106 ms 98 ms pos-2-2-0-0-cr01.sacramento.ca.ibone.comcast.net

[68.86.90.137]

6 15 ms 40 ms 52 ms pos-0-7-0-0-cr01.sanjose.ca.ibone.comcast.net [6

8.86.85.46]

7 24 ms 54 ms 58 ms pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.ne

t [68.86.87.162]

8 62 ms 39 ms 58 ms 208.178.58.13

9 68 ms 64 ms 30 ms ae9-40G.scr4.SNV2.gblx.net [67.17.72.13]

10 136 ms 98 ms 106 ms te2-1-10G.asr1.EWR2.gblx.net [67.16.136.230]

11 102 ms 101 ms 118 ms xe-1-0-4.ar2.ewr1.us.nlayer.net [69.31.94.137]

12 100 ms 100 ms 98 ms as20473.ae3.ar2.ewr1.us.nlayer.net [69.31.34.214

]

13 124 ms 101 ms 161 ms tge2-4-cr2.ewr2.choopa.net [66.55.128.162]

14 * * * Request timed out.

15 * * * Request timed out.

16 120 ms * * 208.167.243.207.choopa.net [208.167.243.207]

17 * * 129 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

Griswold · August 7, 2011

This is my Tracert of the Public at 8:00 P.M. CST/ 9:00 EST P.M. on 8/6/11

I did this multiple times to get a result that i am sure wasn't being hindered by thunderstorms outside.

All are listed below:

Microsoft Windows [Version 6.1.7601]

C:\Users\Joshua Griswold>tracrt 208.167.243.207:27015

'tracrt' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\Joshua Griswold>tracert 208.167.243.207:27015

Unable to resolve target system name 208.167.243.207:27015.

C:\Users\Joshua Griswold>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 7 ms 11 ms 11 ms ip174-71-32-1.om.om.cox.net [174.71.32.1]

3 7 ms 7 ms 7 ms 68.13.8.133

4 8 ms 9 ms 10 ms 68.13.8.237

5 10 ms 11 ms 8 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]

6 54 ms 51 ms 51 ms nyrkbprj02-ae0.0.rd.ny.cox.net [68.1.0.253]

7 60 ms 54 ms 60 ms ve27-br1.ewr3.choopa.net [66.55.135.233]

8 53 ms 51 ms 52 ms tge1-2-cr2.ewr2.choopa.net [66.55.128.34]

9 52 ms 51 ms 51 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Joshua Griswold>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 7 ms 7 ms ip174-71-32-1.om.om.cox.net [174.71.32.1]

3 8 ms 7 ms 7 ms 68.13.8.133

4 9 ms 10 ms 10 ms 68.13.8.237

5 11 ms 7 ms 23 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]

6 54 ms 54 ms 52 ms nyrkbprj02-ae0.0.rd.ny.cox.net [68.1.0.253]

7 53 ms 61 ms 53 ms ve27-br1.ewr3.choopa.net [66.55.135.233]

8 87 ms 52 ms 51 ms tge2-4-cr2.ewr2.choopa.net [66.55.128.162]

9 54 ms 51 ms 54 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Joshua Griswold>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 11 ms 7 ms ip174-71-32-1.om.om.cox.net [174.71.32.1]

3 11 ms 10 ms 8 ms 68.13.8.133

4 8 ms 11 ms 11 ms 68.13.8.237

5 9 ms 11 ms 17 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]

6 51 ms 51 ms 50 ms nyrkbprj02-ae0.0.rd.ny.cox.net [68.1.0.253]

7 53 ms 50 ms 51 ms ve27-br1.ewr3.choopa.net [66.55.135.233]

8 53 ms 51 ms 51 ms tge2-4-cr2.ewr2.choopa.net [66.55.128.162]

9 54 ms 51 ms 51 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Joshua Griswold>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 10 ms 11 ms 11 ms ip174-71-32-1.om.om.cox.net [174.71.32.1]

3 11 ms 10 ms 10 ms 68.13.8.133

4 11 ms 10 ms 12 ms 68.13.8.237

5 31 ms 20 ms 9 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]

6 50 ms 51 ms 51 ms nyrkbprj02-ae0.0.rd.ny.cox.net [68.1.0.253]

7 54 ms 51 ms 50 ms ve21-br2.ewr3.choopa.net [66.55.135.225]

8 54 ms 54 ms 52 ms tge1-4-cr2.ewr2.choopa.net [66.55.128.134]

9 53 ms 51 ms 50 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Joshua Griswold>

Edited August 7, 2011 by Griswold 1st MRB

**Cast 1st MRB** · November 22, 2012

Microsoft Windows [Version 6.1.7601]

C:\Users\Laura>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 27 ms 23 ms 9 ms cpc1-nrte21-2-0-gw.8-4.cable.virginmedia.com [81

.111.76.1]

2 10 ms 26 ms 18 ms nrth-core-2b-ae2-2553.network.virginmedia.net [2

13.106.255.201]

3 7 ms 6 ms 7 ms nrth-bb-1b-ae8-0.network.virginmedia.net [213.10

5.159.209]

4 12 ms 27 ms 10 ms popl-bb-1a-as3-0.network.virginmedia.net [213.10

5.172.14]

5 10 ms 52 ms 12 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.10

5.159.2]

6 30 ms 20 ms 26 ms amst-ic-1-as0-0.network.virginmedia.net [213.105

.175.6]

7 23 ms 39 ms 30 ms ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.21

9]

8 20 ms 29 ms 25 ms ae3-50g.cr1.ams2.nl.nlayer.net [69.22.139.238]

9 25 ms 23 ms 25 ms xe-4-3-1.cr1.lhr1.uk.nlayer.net [69.22.142.15]

10 99 ms 108 ms 105 ms xe-11-3-1.cr1.nyc3.us.nlayer.net [69.22.142.132]

11 101 ms 100 ms 103 ms ae1-50g.ar2.nyc3.us.nlayer.net [69.31.95.154]

12 102 ms 102 ms 103 ms as20473.ae7.ar2.nyc3.us.nlayer.net [69.31.34.78]

13 102 ms 102 ms 103 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

14 111 ms 104 ms 106 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Laura>

Server been lagging all day from what I heard talking to people. You get shot and you don't even hear the bullet sometimes even if the person who shooting you is right in front of you.

**Gardner2** · November 22, 2012

Server was actually quite good this morning when I was on for about 3 hours, when I came back on this afternoon the lag was bad. Notcied pings of most players who are normally in the 50 to 80 range including myself, would periodically jump to 200+ sometimes 800+ for a few seconds then jump back down to normal.

Thought it might have been something running on my computer, checked and nothing else was running.

**Cast 1st MRB** · November 22, 2012

Seems to be mainly the euros getting this delay

**Gearhart 1st MRB** · January 8, 2013

Microsoft Windows [Version 6.0.6002]

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 <1 ms <1 ms <1 ms 192.168.254.254

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 43 ms 42 ms 42 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

**T. Brown 1st MRB** · January 9, 2013

Crashed going to jagd; 5:05pm EST

c:\>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 8 ms 8 ms 6 ms 24.25.32.28

4 14 ms 17 ms 11 ms 24.93.64.112

5 32 ms 30 ms 23 ms 107.14.19.20

6 19 ms 22 ms 20 ms 107.14.19.133

7 23 ms 24 ms 21 ms xe-2-0-5.ar1.iad1.us.nlayer.net [69.31.30.65]

8 21 ms 25 ms 20 ms ae3-40g.cr1.iad1.us.nlayer.net [69.31.31.129]

9 25 ms 25 ms 24 ms xe-10-3-1.cr1.nyc3.us.nlayer.net [69.22.142.93]

10 27 ms 35 ms 28 ms ae1-50g.ar2.nyc3.us.nlayer.net [69.31.95.154]

11 24 ms 37 ms 27 ms as20473.ae7.ar2.nyc3.us.nlayer.net [69.31.34.78]

12 25 ms 29 ms 26 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

13 26 ms 25 ms 27 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

c:\>

**Gardner2** · February 13, 2013

Microsoft Windows [Version 6.1.7601]

C:\Users\OWNER>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]

2 10 ms 22 ms 39 ms 70.64.208.1

3 33 ms 23 ms 23 ms rc1nr-tge0-8-2-0-1.wp.shawcable.net [64.59.182.1

46]

4 26 ms 35 ms 27 ms rc2sc-tge0-2-5-0.wp.shawcable.net [66.163.73.194

]

5 47 ms 47 ms 47 ms rc1sh-pos15-0.mt.shawcable.net [66.163.76.221]

6 62 ms 62 ms 61 ms rd1kt-fe5-0-0.ek.shawcable.net [66.163.76.14]

7 61 ms 73 ms 72 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

8 62 ms 61 ms 132 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

9 60 ms 62 ms 71 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\OWNER>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]

2 23 ms 11 ms 11 ms 70.64.208.1

3 21 ms 23 ms 23 ms rc1nr-tge0-8-2-0-1.wp.shawcable.net [64.59.182.1

46]

4 24 ms 23 ms 31 ms rc2sc-tge0-2-5-0.wp.shawcable.net [66.163.73.194

]

5 57 ms 49 ms 48 ms rc1sh-pos15-0.mt.shawcable.net [66.163.76.221]

6 78 ms 64 ms 64 ms rd1kt-fe5-0-0.ek.shawcable.net [66.163.76.14]

7 59 ms 59 ms 72 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

8 112 ms 63 ms 62 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

9 59 ms 58 ms 61 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\OWNER>

Edited February 13, 2013 by Gardner 1st MRB

**Gardner2** · February 28, 2013

Server just lagged out and crashed.

C:\Users\OWNER>cmd

Microsoft Windows [Version 6.1.7601]

C:\Users\OWNER>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms my.router [192.168.1.1]

2 11 ms 13 ms 8 ms 70.64.208.1

3 33 ms 32 ms 30 ms rc2nr-ge5-0-0-1.wp.shawcable.net [64.59.182.146]

4 21 ms 27 ms 23 ms rc2sc-tge0-2-5-0.wp.shawcable.net [66.163.73.194

]

5 48 ms 48 ms 49 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]

6 63 ms 58 ms 60 ms rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]

7 70 ms 69 ms 61 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

8 61 ms 63 ms 64 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

9 64 ms 59 ms 60 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\OWNER>

**Gardner2** · February 28, 2013

Just crashed/lagged again giving everyone disconnect count downs

Microsoft Windows [Version 6.1.7601]

C:\Users\OWNER>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]

2 11 ms 11 ms 24 ms 70.64.208.1

3 25 ms 22 ms 24 ms rc2nr-ge5-0-0-1.wp.shawcable.net [64.59.182.146]

4 25 ms 27 ms 39 ms rc2sc-tge0-2-5-0.wp.shawcable.net [66.163.73.194

]

5 45 ms 75 ms 47 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]

6 62 ms 63 ms 61 ms rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]

7 68 ms 63 ms 72 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

8 77 ms 74 ms 61 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

9 62 ms 83 ms 59 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\OWNER>

**Gardner2** · February 28, 2013

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms my.router [192.168.1.1]

2 12 ms 9 ms 20 ms 70.64.208.1

3 36 ms 21 ms 23 ms rc2nr-ge5-0-0-1.wp.shawcable.net [64.59.182.146]

4 29 ms 26 ms 22 ms rc2sc-tge0-2-5-0.wp.shawcable.net [66.163.73.194

]

5 47 ms 53 ms 70 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]

6 67 ms 64 ms 61 ms rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]

7 65 ms 61 ms 63 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

8 62 ms 59 ms 59 ms ve105-as1.pnj1.choopa.net [108.61.79.86]

9 62 ms 58 ms 60 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

Sign In

Regarding any Server Lag issues

Recommended Posts

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Join the conversation

Recently Browsing 0 members

Recent Posts