NEWS CS:GO and Insurgency Are Closed, or Not.
- Thread starter Shotgun Jesus
- Start date
Server is on server list on front page. If you hover cursor over name, it shows IP and you can copy/paste.
OG buckshot jr
TD Admin
Thank you:
Code:
Run one
1 ***
2 8 ms 6 ms 7 ms lo0-0-lns02-tor2.teksavvy.com [***]
3 7 ms 6 ms 7 ms ae2-2150-bdr01-tor2.teksavvy.com [***]
4 7 ms 7 ms 7 ms te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.122.69.201]
5 16 ms 16 ms 16 ms be2436.ccr21.alb02.atlas.cogentco.com [66.28.4.29]
6 19 ms 19 ms 19 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
7 20 ms 19 ms 20 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
8 20 ms 19 ms 19 ms 38.88.194.86
9 37 ms 18 ms 25 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
10 18 ms 18 ms 18 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
11 19 ms 19 ms 19 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Run Two
1 ***
2 29 ms 6 ms 6 ms lo0-0-lns02-tor2.teksavvy.com [***]
3 7 ms 7 ms 7 ms ae2-2150-bdr01-tor2.teksavvy.com [***]
4 7 ms 7 ms 7 ms te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.122.69.201]
5 16 ms 16 ms 16 ms be2436.ccr21.alb02.atlas.cogentco.com [66.28.4.29]
6 19 ms 19 ms 19 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
7 20 ms 19 ms 19 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
8 20 ms 19 ms 21 ms 38.88.194.86
9 19 ms 18 ms 19 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
10 18 ms 18 ms 18 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
11 19 ms 19 ms 18 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Run Three
1 ***
2 7 ms 8 ms 7 ms lo0-0-lns02-tor2.teksavvy.com [***]
3 7 ms 6 ms 7 ms ae2-2150-bdr01-tor2.teksavvy.com [***]
4 7 ms 7 ms 7 ms te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.122.69.201]
5 16 ms 16 ms 16 ms be2436.ccr21.alb02.atlas.cogentco.com [66.28.4.29]
6 19 ms 19 ms 19 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
7 20 ms 19 ms 19 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
8 21 ms 20 ms 20 ms 38.88.194.86
9 18 ms 19 ms 19 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
10 19 ms 18 ms 18 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
11 18 ms 18 ms 18 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]Whatever Hop #8 is, it's the worst one (38.88.194.86). Might be a firewall or something.. All in all, good from where I'm sitting.
EDIT: Apparently it's a Network Services hop located in Milford, just north of NY.. https://www.db-ip.com/38.88.194.86
Code:
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
2 5 ms 4 ms 4 ms 104.255.14.138
3 8 ms 5 ms 4 ms 208.68.89.245
4 5 ms 4 ms 4 ms toro-b1-link.telia.net [213.248.98.241]
5 95 ms 15 ms 15 ms nyk-bb1-link.telia.net [62.115.141.192]
6 16 ms 16 ms 16 ms nyk-b5-link.telia.net [213.155.135.19]
7 21 ms 21 ms 24 ms internap-ic-305784-nyk-b5.c.telia.net [213.248.66.102]
8 18 ms 17 ms 16 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
9 17 ms 16 ms 16 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
10 16 ms 17 ms 16 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
no cogentco
Rogers sending me to Pakistan first.
Saturday, March 12 2016... the day @Low Budget finally paid off his car.
I wish...four more years to go
Sushicutter
TD Admin
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
2 6 ms 7 ms 7 ms 10.208.2.1
3 * * * Request timed out.
4 42 ms 42 ms 41 ms 96.127.251.141
5 45 ms 46 ms 55 ms te0-7-0-27.ccr21.ymq02.atlas.cogentco.com [38.104.154.13]
6 48 ms 47 ms 47 ms be2088.ccr21.alb02.atlas.cogentco.com [154.54.43.18]
7 85 ms 51 ms 51 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
8 50 ms 51 ms 51 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
9 53 ms 53 ms 56 ms 38.88.194.86
10 126 ms 222 ms 220 ms border2.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.79]
11 50 ms 50 ms 52 ms inap-b2.e3.router.nyc.nfoservers.com [70.42.74.254]
12 49 ms 50 ms 50 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
2 8 ms 7 ms 7 ms 10.208.2.1
3 * * * Request timed out.
4 41 ms 42 ms 42 ms 96.127.251.141
5 47 ms 47 ms 42 ms te0-7-0-27.ccr21.ymq02.atlas.cogentco.com [38.104.154.13]
6 47 ms 51 ms 48 ms be2088.ccr21.alb02.atlas.cogentco.com [154.54.43.18]
7 50 ms 50 ms 52 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
8 52 ms 51 ms 50 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
9 53 ms 55 ms 52 ms 38.88.194.86
10 50 ms 51 ms 51 ms border2.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.79]
11 49 ms 50 ms 49 ms inap-b2.e3.router.nyc.nfoservers.com [70.42.74.254]
12 49 ms 51 ms 51 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
step 3 and 10.....
over a maximum of 30 hops:
2 6 ms 7 ms 7 ms 10.208.2.1
3 * * * Request timed out.
4 42 ms 42 ms 41 ms 96.127.251.141
5 45 ms 46 ms 55 ms te0-7-0-27.ccr21.ymq02.atlas.cogentco.com [38.104.154.13]
6 48 ms 47 ms 47 ms be2088.ccr21.alb02.atlas.cogentco.com [154.54.43.18]
7 85 ms 51 ms 51 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
8 50 ms 51 ms 51 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
9 53 ms 53 ms 56 ms 38.88.194.86
10 126 ms 222 ms 220 ms border2.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.79]
11 50 ms 50 ms 52 ms inap-b2.e3.router.nyc.nfoservers.com [70.42.74.254]
12 49 ms 50 ms 50 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
2 8 ms 7 ms 7 ms 10.208.2.1
3 * * * Request timed out.
4 41 ms 42 ms 42 ms 96.127.251.141
5 47 ms 47 ms 42 ms te0-7-0-27.ccr21.ymq02.atlas.cogentco.com [38.104.154.13]
6 47 ms 51 ms 48 ms be2088.ccr21.alb02.atlas.cogentco.com [154.54.43.18]
7 50 ms 50 ms 52 ms be2106.ccr41.jfk02.atlas.cogentco.com [154.54.3.49]
8 52 ms 51 ms 50 ms be2324.ccr21.jfk04.atlas.cogentco.com [154.54.47.18]
9 53 ms 55 ms 52 ms 38.88.194.86
10 50 ms 51 ms 51 ms border2.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.79]
11 49 ms 50 ms 49 ms inap-b2.e3.router.nyc.nfoservers.com [70.42.74.254]
12 49 ms 51 ms 51 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
step 3 and 10.....
everyth1ng
DARKLY Regular
Server works really well, although I was getting massive FPS drops on Dust 2 today. I think it was on my end, but I haven't seen FPS drops like that for a long time. Not sure what's going on. It went away when I restarted, though.
Noob.
TD Member
Run 1
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
2 * * * Request timed out.
3 13 ms 14 ms 12 ms tl6rh.rd.shawcable.net [64.59.133.149]
4 30 ms 30 ms 28 ms rc3sc-be10.wp.shawcable.net [66.163.78.2]
5 85 ms 73 ms 73 ms rc4as-tge0-2-0-0.vx.shawcable.net [66.163.77.50]
6 77 ms 73 ms 72 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
7 75 ms 74 ms 74 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
8 77 ms 77 ms 77 ms ae27.cs1.dca2.us.eth.zayo.com [64.125.30.246]
9 79 ms 77 ms 107 ms ae4.cs1.lga5.us.eth.zayo.com [64.125.29.202]
10 78 ms 77 ms 77 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
11 77 ms 77 ms 87 ms ae11.mpr3.lga7.us.zip.zayo.com [64.125.20.14]
12 75 ms 67 ms 69 ms 128.177.168.190.IPYX-072053-ZYO.zip.zayo.com [128.177.168.190]
13 70 ms 67 ms 67 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
14 66 ms 68 ms 67 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
15 67 ms 67 ms 65 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Run 2
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
2 * * * Request timed out.
3 12 ms 13 ms 13 ms tl6rh.rd.shawcable.net [64.59.133.149]
4 27 ms 35 ms 28 ms rc3sc-be10.wp.shawcable.net [66.163.78.2]
5 74 ms 74 ms 73 ms rc4as-tge0-2-0-0.vx.shawcable.net [66.163.77.50]
6 71 ms 71 ms 72 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
7 72 ms 74 ms 72 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
8 76 ms 77 ms 80 ms ae27.cs1.dca2.us.eth.zayo.com [64.125.30.246]
9 78 ms 79 ms 79 ms ae4.cs1.lga5.us.eth.zayo.com [64.125.29.202]
10 78 ms 79 ms 77 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
11 81 ms 77 ms 103 ms ae11.mpr3.lga7.us.zip.zayo.com [64.125.20.14]
12 67 ms 66 ms 68 ms 128.177.168.190.IPYX-072053-ZYO.zip.zayo.com [128.177.168.190]
13 66 ms 64 ms 66 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
14 66 ms 68 ms 67 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
15 67 ms 67 ms 76 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
Now I don't quite know what this means, but I'm assuming step 2 timing out isn't ideal, as well as the random steps greater than 100ms.
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
2 * * * Request timed out.
3 13 ms 14 ms 12 ms tl6rh.rd.shawcable.net [64.59.133.149]
4 30 ms 30 ms 28 ms rc3sc-be10.wp.shawcable.net [66.163.78.2]
5 85 ms 73 ms 73 ms rc4as-tge0-2-0-0.vx.shawcable.net [66.163.77.50]
6 77 ms 73 ms 72 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
7 75 ms 74 ms 74 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
8 77 ms 77 ms 77 ms ae27.cs1.dca2.us.eth.zayo.com [64.125.30.246]
9 79 ms 77 ms 107 ms ae4.cs1.lga5.us.eth.zayo.com [64.125.29.202]
10 78 ms 77 ms 77 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
11 77 ms 77 ms 87 ms ae11.mpr3.lga7.us.zip.zayo.com [64.125.20.14]
12 75 ms 67 ms 69 ms 128.177.168.190.IPYX-072053-ZYO.zip.zayo.com [128.177.168.190]
13 70 ms 67 ms 67 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
14 66 ms 68 ms 67 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
15 67 ms 67 ms 65 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Run 2
Tracing route to c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
2 * * * Request timed out.
3 12 ms 13 ms 13 ms tl6rh.rd.shawcable.net [64.59.133.149]
4 27 ms 35 ms 28 ms rc3sc-be10.wp.shawcable.net [66.163.78.2]
5 74 ms 74 ms 73 ms rc4as-tge0-2-0-0.vx.shawcable.net [66.163.77.50]
6 71 ms 71 ms 72 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
7 72 ms 74 ms 72 ms ae6.cr1.dca2.us.zip.zayo.com [64.125.20.117]
8 76 ms 77 ms 80 ms ae27.cs1.dca2.us.eth.zayo.com [64.125.30.246]
9 78 ms 79 ms 79 ms ae4.cs1.lga5.us.eth.zayo.com [64.125.29.202]
10 78 ms 79 ms 77 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
11 81 ms 77 ms 103 ms ae11.mpr3.lga7.us.zip.zayo.com [64.125.20.14]
12 67 ms 66 ms 68 ms 128.177.168.190.IPYX-072053-ZYO.zip.zayo.com [128.177.168.190]
13 66 ms 64 ms 66 ms border1.pc2-bbnet2.ext1.nym.pnap.net [216.52.95.78]
14 66 ms 68 ms 67 ms inap-b1.e2.router.nyc.nfoservers.com [63.251.20.254]
15 67 ms 67 ms 76 ms c-74-91-123-216.managed-ded.internap-nyc.nfoservers.com [74.91.123.216]
Trace complete.
Now I don't quite know what this means, but I'm assuming step 2 timing out isn't ideal, as well as the random steps greater than 100ms.
We have a new server.
.44 caliber
TD Admin
I get gradual fps drops when I join off steam server window from desktop. When I join server after game launch tho it works just fine. Been like that since 2014, no idea why. Sniffing markers as a child has never helped my cause in these situations.
everyth1ng
DARKLY Regular
Actually, now that you mention it, I did join the server through the join button on the front page with the game closed. Good shit.
Last edited:
amanshotme
TD Member
CS:go killed it......
I haven't played since we abandoned the cs:s server
Is it time to have a CSS night???
.44 caliber
TD Admin
Good shit guys, was fun! Lets get this slut rollin' more often. This was the best turnout since more than a year ago.
