Server issues

PBRMEASAP

PBRMEASAP

A Little Darkly
Man, it is very frustrating. We haven't changed ISP or anything affiliated with our internet, but somewhere along the lines it got fucked up and now I can't play on TD with less than a 90 ping....maaaaaaaaan
 
Wake

Wake

I'm New Here
I get up to 40% choke and sometimes the server just sits at 10% for an entire round.

Living in Toronto and using TekSavvy (Bell?):


Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
tracert 208.68.90.170
 
Tracing route to 208.68.90.170 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  GATEWAY [192.168.2.1]
  2    6 ms    6 ms    5 ms  lo-100.lns02.tor.packetflow.ca [206.248.154.122]
 
  3    7 ms    5 ms    5 ms  2150.ae1.bdr04.tor.man.teksavvy.com.packetflow.c
a [69.196.136.164]
  4    5 ms    5 ms    5 ms  69.196.136.41
  5    5 ms    5 ms    5 ms  gw-spdnetwork.torontointernetxchange.net [206.10
8.34.81]
  6    5 ms    5 ms    5 ms  208.68.90.170
 
Trace complete.
 
ranger24

ranger24

A Little Darkly
ever since the new year this server has had a choke problem. Its just getting worse and worse.. When the map was on dust 2 early the choke peaked at 99% and never got below 50% till everyone was basically dead. Everyone see it and feels it. Not just me
 
BOT Snake

BOT Snake

TD Admin
i just experienced 80 percent choke and this is how it was when it trrt

Tracing route to 208.68.90.170 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.2.1
3 14 ms 13 ms 15 ms bas1-streetsville52_lo0_SYMP.net.bell.ca [64.
.200.230]
4 14 ms 13 ms 13 ms dis5-clarkson16_8-2-0_100.net.bell.ca [64.230
.38]
5 105 ms 27 ms 28 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.
.106]
6 * * * Request timed out.
7 26 ms 26 ms 26 ms ae2-40g.cr2.ord1.us.nlayer.net [69.31.111.149
8 26 ms 26 ms 26 ms ae3-60g.cr1.ord1.us.nlayer.net [69.31.111.153
9 37 ms 39 ms 37 ms xe-5-3-0.cr1.ewr1.us.nlayer.net [69.22.142.75
10 38 ms 38 ms 37 ms ae2-60g.cr1.nyc2.us.nlayer.net [69.31.95.174]
11 50 ms 47 ms 48 ms xe-0-0-0.cr1.tor1.ca.nlayer.net [69.22.142.14

12 49 ms 49 ms 50 ms as40028.xe-3-3-0.cr1.tor1.ca.nlayer.net [69.3
43.158]
13 47 ms 47 ms 48 ms ar1.yyz01.3z.ca [208.68.88.177]
14 49 ms 49 ms 48 ms 208.68.90.170

Trace complete.
 
Low Budget

Low Budget

DGN Staff
Staff member
Guys, routing is completely out of our control. As we stated before, there is no problem with the actual dedicated server itself, cpu usage and load are perfectly fine. The problem is a host/ISP issue. I will fire up an email to the host and have them look into it, but if this is the routing they have and cannot change it then we are SOL. Our only option then will be to change host, and we've pretty much tried all the good Toronto hosts over the years. So maybe it's time to bail on Toronto and go with a reliable game host in Chicago like NFO. Are you guys willing to sacrifice low local ping for better performance. You decide.

Posted using dat Q10
 
Macido

Macido

DARKLY Regular
Can we nail down which ISP's are the problem, some people seem to have 0 problems on the server, what are they using!
I'm Bell Fibe, i'd gladly change if I knew what did not do this.
 
Low Budget

Low Budget

DGN Staff
Staff member
Macido said:
Can we nail down which ISP's are the problem, some people seem to have 0 problems on the server, what are they using!
I'm Bell Fibe, i'd gladly change if I knew what did not do this.
Click to expand...

I'm also will Bell Fibe. Seems to be all bell customers getting shitty routing. Rogers fags are fine.

Posted using dat Q10
 
Shotgun Jesus

Shotgun Jesus

Professional Cocksucker
Staff member
I'm on Rogers and I have no problem. Bell is a Brains-level faggot.

Server is always full. Besides, a shitty game should feel like shit. :rip: shitty ISP pakis.

Shit.
 
Roach

Roach

TD Admin
Low Budget said:
I'm also will Bell Fibe. Seems to be all bell customers getting shitty routing. Rogers fags are fine.

Posted using dat Q10
Click to expand...
also on bell, with alot of hiccups
checked with support and its just an issue in this area, they are working on it
 
Macido

Macido

DARKLY Regular
Roach said:
also on bell, with alot of hiccups
checked with support and its just an issue in this area, they are working on it
Click to expand...

ah, so server is in Toronto and so are most of us Bell users, but it's going all the way to Chicago and NYC then back?
i'll give them a call this weekend as well If i get time
 
Macido

Macido

DARKLY Regular
SJ can you post what your route looks like, or what it's supposed to look like connecting to the server from being in the same city
 
Shotgun Jesus

Shotgun Jesus

Professional Cocksucker
Staff member
Macido said:
SJ can you post what your route looks like, or what it's supposed to look like connecting to the server from being in the same city
Click to expand...

2 209.148.244.117 (209.148.244.117) 14.300 ms 17.618 ms 14.038 ms
3 69.63.249.58 (69.63.249.58) 13.820 ms 13.998 ms 11.897 ms
4 209.148.224.246 (209.148.224.246) 56.313 ms 10.544 ms 11.148 ms
5 gw-spdnetwork.torontointernetxchange.net (206.108.34.81) 10.627 ms 11.046 ms 10.195 ms
6 208.68.90.171 (208.68.90.171) 9.543 ms 9.640 ms 9.730 ms
 
Macido

Macido

DARKLY Regular
I have been asking around when the choke hits the server. Was great for an hour today then it started spiking again so I asked around, it's affecting Roger's users alike at the same time. That routing thing very well may be an issue but it may not be ISP dependent. It's too coincidental for JUST ISP in my opinion.
I wonder if the bell and rogers are throttling our access the server?
 
Low Budget

Low Budget

DGN Staff
Staff member
Everyone having choke problems on Toronto due to routing, try out the 128tick Chicago CSGO server. Click on the banner to join (IP: 74.91.113.242:27015):

 
You must log in or register to reply here.
Top