Teksavvy Cable or DSL for the Best Routing to TD's Toronto CS:GO Server?

Discussion in 'Technology' started by Sgt. Rex Power Colt, Jun 19, 2014.

Thread Status:
This thread is more than 365 days old. Therefore, it is better than any of the shit that gets posted nowadays.
  1. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
    After all this time, I'm finally in a position where I can switch over to a different ISP. I have Start Communications in the back of my mind because tytanium recommends them, but I'm considering Teksavvy for myself at the moment. I spoke to a Teksavvy sales associate today regarding the routing for their DSL service, and according to them, I should be routed to the Toronto Internet Exchange. Before I move forward with this, though, I was hoping that I could get some intel from you guys. Cable or DSL - which service has better routing? Teksavvy customers - can you run a traceroute to the Toronto CS:GO server and post the results here? I'd greatly appreciate it. Thanks a lot in advance.
    #1
  2. OG buckshot jr

    OG buckshot jr TD Admin

    Joined:
    Sep 30, 2008
    Messages:
    11,025
    Likes Received:
    2,280
    I use DSL from teksavvy. Fast, never ever ever ever slow, and always have a bomb diggity ping in every game ever made, even games that aren't even out yet. And yes, I'm always hooked into torix.
    #2
  3. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
    Thanks for the reply, BJ! I placed an order for the 25/10 DSL yesterday. If I'm not getting under 15 ping at all times in TD, I'm not going to be very happy, lol. And it will be interesting to see how my ping changes for Planetside 2. I've been playing a ton of it lately, and I'm currently getting between 50-80 ping (strangely enough, it's actually very playable like that). I'm a little bit more forgiving with PS2, though, due to the location of the server and the number of players that are on.

    What continues to be a mystery for me, though, is that I used to get under 15 ping consistently in TD with Bell up until July of last year, iirc. I don't understand how this is possible considering that Bell apparently isn't hooked into TORIX, but perhaps there's something that I'm missing here. And then somewhere along the way, I was relegated to shit routing and has been getting progressively more shitty as time has gone on.
    #3
  4. OG buckshot jr

    OG buckshot jr TD Admin

    Joined:
    Sep 30, 2008
    Messages:
    11,025
    Likes Received:
    2,280
    You won't be let down! It depends on the lines around your house, but teksavvy checks the level of service you can get. I have 25/10 as well, and the bitch kicks in top speed all day - in fact, I often download large patches in bf4/steam at 4MB/s, which is about 32mbps. No torrent throttling either :)
    #4
  5. up-n-atom

    up-n-atom DARKLY Regular

    Joined:
    Jan 30, 2014
    Messages:
    237
    Likes Received:
    113
    Been with their cable service (Wolfdale POI) since the beginning with only 1 hiccup so far due to side walk construction and subsequently my line being cut. It took Rogers 2 weeks to fix and stupidly I had to phone Rogers on behave of TekSavvy. I previously had their DSL service (Cooksville CO, Where's my CO) but Bell tampered way too much from minor things I could fix like disconnecting the line from the demarc to the major and inevitable of being switched to a further slam because of priority customers. If you ever do have a problem the story is always the same and the blame is shifted to Rogers and/or Bell. It's a must to keep logs to get the most helpful response and always keep an eye on http://www.dslreports.com/forum/teksavvy. FYI, If you ever suspect routing issues and/or packet loss, run WinMTR and post the log on that forum.

    Toronto Darkly
    Code:
    Tracing route to 208.68.90.171 over a maximum of 30 hops
    
      1    <1 ms    <1 ms    <1 ms  pfsense.localdomain [192.168.1.1]
      2     9 ms     7 ms     7 ms  10.125.12.129
      3     8 ms    11 ms    11 ms  209.148.244.93
      4    10 ms    11 ms    11 ms  69.63.249.57
      5    11 ms    18 ms    13 ms  ae2_2140-bdr03-tor.teksavvy.com [69.196.136.131]
    
      6    13 ms    14 ms    12 ms  gw-spdnetwork.torontointernetxchange.net [206.10
    8.34.81]
      7    11 ms    10 ms    10 ms  208.68.90.171
    
    Trace complete.
    Chicago Darkly
    Code:
    Tracing route to v-74-91-113-242.unman-vds.internap-chicago.nfoservers.com [74.9
    1.113.242]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  pfsense.localdomain [192.168.1.1]
      2     8 ms     8 ms     6 ms  10.125.12.129
      3    16 ms    14 ms    11 ms  209.148.244.93
      4    10 ms    11 ms    11 ms  69.63.249.57
      5    12 ms    13 ms    11 ms  ae1_2120-bdr04-tor.teksavvy.com [69.196.136.68]
    
      6    12 ms    10 ms    11 ms  te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.12
    2.69.201]
      7    25 ms    29 ms    25 ms  be2079.ccr41.ord01.atlas.cogentco.com [154.54.27
    .181]
      8    24 ms    25 ms    26 ms  be2005.ccr21.ord03.atlas.cogentco.com [66.28.4.7
    4]
      9    23 ms    22 ms    22 ms  38.104.102.102
     10    26 ms    23 ms    22 ms  border6.po2-bbnet2.chg.pnap.net [64.94.32.75]
     11    22 ms    23 ms    24 ms  v-74-91-113-242.unman-vds.internap-chicago.nfose
    rvers.com [74.91.113.242]
    
    Trace complete.
    #5
  6. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
    Will do.

    I should be up with Teksavvy by the end of next week. I'll post the results when I have them.
    #6
  7. Wake

    Wake I'm New Here

    Joined:
    Jan 21, 2014
    Messages:
    8
    Likes Received:
    2
    Been using Teksavvy DSL 25/10 for over a year now. I get around 5 to 12 ping on the scoreboard all the time, and about ~25 (?) in the console.

    All I can say is the internet itself is near flawless, perfect even if you compare it to Bell or Rogers. You get what you pay for; nothing less, nothing more. Service only goes down when there's severe weather in Toronto, or when they're updating their hardware/doing maintenance overnight.

    Toronto Darkly
    Code:
    Tracing route to 208.68.90.171 over a maximum of 30 hops
     
      1    <1 ms    <1 ms    <1 ms  GATEWAY [192.168.2.1]
      2    6 ms    6 ms    9 ms  lo-100.lns02.tor.packetflow.ca [206.248.154.122]
     
      3    6 ms    5 ms    5 ms  ae3_2120-bdr03-tor.teksavvy.com [69.196.136.74]
     
      4    6 ms    5 ms    5 ms  gw-spdnetwork.torontointernetxchange.net [206.10
    8.34.81]
      5    5 ms    5 ms    5 ms  208.68.90.171
     
    Trace complete.
    
    Chicago Darkly
    Code:
    Tracing route to v-74-91-113-242.unman-vds.internap-chicago.nfoservers.com [74.9
    1.113.242]
    over a maximum of 30 hops:
     
      1    <1 ms    <1 ms    <1 ms  GATEWAY [192.168.2.1]
      2    6 ms    5 ms    5 ms  lo-100.lns02.tor.packetflow.ca [206.248.154.122]
     
      3    6 ms    5 ms    5 ms  ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
     
      4    6 ms    6 ms    5 ms  te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.12
    2.69.201]
      5    21 ms    20 ms    20 ms  be2079.ccr41.ord01.atlas.cogentco.com [154.54.27
    .181]
      6    21 ms    21 ms    20 ms  be2005.ccr21.ord03.atlas.cogentco.com [66.28.4.7
    4]
      7    18 ms    18 ms    17 ms  38.122.180.138
      8    *      18 ms    17 ms  border11.po1-bbnet1.chg.pnap.net [64.94.32.23]
      9    18 ms    17 ms    18 ms  v-74-91-113-242.unman-vds.internap-chicago.nfose
    rvers.com [74.91.113.242]
     
    Trace complete.
    
    #7
  8. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
  9. OG buckshot jr

    OG buckshot jr TD Admin

    Joined:
    Sep 30, 2008
    Messages:
    11,025
    Likes Received:
    2,280
    #9
    Sgt. Rex Power Colt likes this.
  10. up-n-atom

    up-n-atom DARKLY Regular

    Joined:
    Jan 30, 2014
    Messages:
    237
    Likes Received:
    113
    Having my yearly troubles... This time either Rogers modified some infrastructure or someone has plugged in some bad hardware on our street sending noise over the line. Had to issue a support ticket which required a technician to come by and stabilize the RF signals, they attached two new filters to the line. I was disconnected for a two days. I'm pinging high to the server due to a delay at gw-spdnetwork.torontointernetxchange.net and TekSavvy can't do anything to remedy that since it's the last hop. Overall this years major problem was fixed relatively quickly but it still required downtime.
    Last edited: Oct 6, 2014
    #10
  11. OG buckshot jr

    OG buckshot jr TD Admin

    Joined:
    Sep 30, 2008
    Messages:
    11,025
    Likes Received:
    2,280
    Funny you mention torix delays, maybe that's what's been fucking our server experience.....?
    #11
  12. up-n-atom

    up-n-atom DARKLY Regular

    Joined:
    Jan 30, 2014
    Messages:
    237
    Likes Received:
    113
    It's only apparent within the 7-11pm timeframe; either throttling or congestion. My troubles don't seem to be resolved either :( I received an update to my ticket and the applied filters by the technician improved the RF signals but remain below TekSavvy's specifications. I will probably suffer some more downtime while Rogers figures this out.
    #12
  13. $alvador

    $alvador TD Member

    Joined:
    May 8, 2011
    Messages:
    1,167
    Likes Received:
    239
    my shit is going thru chitown like a bitch
    #13
  14. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
    I thought the leading theory for this was SourceMod issues? No?
    #14
  15. OG buckshot jr

    OG buckshot jr TD Admin

    Joined:
    Sep 30, 2008
    Messages:
    11,025
    Likes Received:
    2,280
    I was just reaching out :S
    #15
  16. everyth1ng

    everyth1ng DARKLY Regular

    Joined:
    May 17, 2013
    Messages:
    725
    Likes Received:
    258
    Yeah, sorry to hear that you've been experiencing problems @up-n-atom .

    Things have been going well for me for the most part, but I've been getting some questionable routing to Chicago recently (when connecting to servers in Chicago). I haven't looked into it yet, but that's about the only issue I've experienced so far aside from the occasional downtime for Bell maintenance.
    #16
  17. up-n-atom

    up-n-atom DARKLY Regular

    Joined:
    Jan 30, 2014
    Messages:
    237
    Likes Received:
    113
    Would someone with rogers and another with bell be so kind to post your routes to the new server, thanks. Teksavvy has bad routing... pnap.net being the worst and last hop :(

    Code:
    |------------------------------------------------------------------------------------------|
    |                                      WinMTR statistics                                   |
    |                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |------------------------------------------------|------|------|------|------|------|------|
    |                 hummingbird.localdomain -    0 |   38 |   38 |    0 |    0 |    0 |    0 |
    |                           10.125.12.129 -    0 |   38 |   38 |    6 |    8 |   18 |    7 |
    |                          209.148.244.93 -    0 |   38 |   38 |    9 |   13 |   19 |   19 |
    |                            69.63.249.57 -    0 |   38 |   38 |    8 |   13 |   20 |   20 |
    |         ae2_2110-bdr03-tor.teksavvy.com -    0 |   38 |   38 |    9 |   15 |   41 |   19 |
    |te0-7-0-22.ccr22.yyz02.atlas.cogentco.com -    0 |   38 |   38 |   10 |   13 |   17 |   14 |
    |   be2080.ccr42.ord01.atlas.cogentco.com -    0 |   38 |   38 |   25 |   28 |   34 |   27 |
    |   be2003.ccr21.ord03.atlas.cogentco.com -    0 |   38 |   38 |   26 |   29 |   33 |   28 |
    |                          38.104.102.102 -    0 |   38 |   38 |   25 |   27 |   32 |   28 |
    |         border6.po1-bbnet1.chg.pnap.net -    0 |   38 |   38 |   25 |   35 |  119 |   30 |
    |c-216-52-143-77.managed-vds.internap-chicago.nfoservers.com -    0 |   38 |   38 |   25 |   27 |   33 |   29 |
    |________________________________________________|______|______|______|______|______|______|
       WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
    
    Last edited: Nov 11, 2014
    #17
  18. Low Budget

    Low Budget DGN Staff Staff Member

    Joined:
    Sep 30, 2008
    Messages:
    6,092
    Likes Received:
    1,407
    Bell Fibe 25/10
    #18
  19. MetalLobster

    MetalLobster TD Admin

    Joined:
    Jul 28, 2012
    Messages:
    1,046
    Likes Received:
    513
    Acanac Cable 30/5 (Rogers reseller)


    Code:
    Tracing route to c-216-52-143-77.managed-vds.internap-chicago.nfoservers.com [21
    6.52.143.77]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  192.168.11.1
      2    18 ms    13 ms    10 ms  10.101.127.1
      3    12 ms    16 ms    16 ms  24.156.150.117
      4    22 ms    12 ms    14 ms  gw02.mtnk-6-1-2.mtnk.phub.net.cable.rogers.com [
    69.63.248.1]
      5    12 ms    21 ms    12 ms  xe-1-2-0-0.ipr02.totftds.distributel.net [206.80
    .255.53]
      6    87 ms    83 ms    79 ms  ae0-709.tor10.ip4.gtt.net [216.221.159.49]
      7    23 ms    25 ms    23 ms  xe-3-2-0.chi12.ip4.gtt.net [141.136.105.193]
      8    28 ms    27 ms    25 ms  internap-gw.ip4.gtt.net [77.67.70.2]
      9    26 ms    29 ms    23 ms  border6.po1-bbnet1.chg.pnap.net [64.94.32.11]
    10    32 ms    25 ms    41 ms  c-216-52-143-77.managed-vds.internap-chicago.nfo
    servers.com [216.52.143.77]
    
    Trace complete.



    Yeah, tell me about it. I'm going up +50ms...

    Update: Got a more consistent result now

    Code:
    Tracing route to c-216-52-143-77.managed-vds.internap-chicago.nfoservers.com [21
    6.52.143.77]
    over a maximum of 30 hops:
    
      1     2 ms     1 ms     1 ms  192.168.11.1
      2    11 ms    10 ms     8 ms  10.101.127.1
      3    12 ms    11 ms    13 ms  24.156.150.117
      4    15 ms    12 ms    15 ms  gw02.mtnk-6-1-2.mtnk.phub.net.cable.rogers.com [
    69.63.248.1]
      5    11 ms    11 ms    11 ms  xe-1-2-0-0.ipr02.totftds.distributel.net [206.80
    .255.53]
      6    12 ms    12 ms    11 ms  ae0-709.tor10.ip4.gtt.net [216.221.159.49]
      7    20 ms    21 ms    19 ms  xe-10-3-0.chi12.ip4.gtt.net [141.136.106.13]
      8    22 ms    24 ms    24 ms  internap-gw.ip4.gtt.net [77.67.70.2]
      9    21 ms    21 ms    21 ms  border6.po1-bbnet1.chg.pnap.net [64.94.32.11]
    10    20 ms    21 ms    23 ms  c-216-52-143-77.managed-vds.internap-chicago.nfo
    servers.com [216.52.143.77]
    
    Trace complete.
    Last edited: Nov 12, 2014
    #19
  20. up-n-atom

    up-n-atom DARKLY Regular

    Joined:
    Jan 30, 2014
    Messages:
    237
    Likes Received:
    113
    Thanks @Low Budget and @MetalLobster both of your routes seem to also suffer some congestion a long the way. I don't experience any loss so it's a mute point for TekSavvy. From their support website

    I'm not certain if that pertains to just TekSavvy or all of Rogers network. I'm under the impression they're traffic shaping again since they've announced Shomi but they'll deny that.

    Going to try again around 2am and hopefully there is some west coast action towards pnap.net.
    Last edited: Nov 11, 2014
    #20
Thread Status:
This thread is more than 365 days old. Therefore, it is better than any of the shit that gets posted nowadays.

Share This Page