test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Horrendous tracert times (SNR & DC) thanks to Cogent

ovrkylovrkyl Member Posts: 309 Arc User
edited May 2015 in Windows and General: PC, Network, and Other Technical Issues
You guys REALLY need to find someone else, other than Cogent. Really. Seriously. Their service has become so pi$$ poor that it will be blamed on you regardless if it's just their traffic hubs or your game server.

Big problems tonight. Apparently Cogent's hamsters are in rebellion at be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174] 'cause their times SUCK!

After taking a long time getting in through the launcher and waiting for characters to appear, got SERVER NOT RESPONDING almost immediately after Play, then DCed. Haven't gotten in once.

Tracert results...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\█████>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 3 ms 3 ms 2 ms ██.█.█.█
2 9 ms 8 ms 12 ms ██.███.██.██
3 10 ms 12 ms 24 ms xe-1-0-0-0-sur03.longview.wa.bverton.comcast.net [68.87.216.241]
4 9 ms 11 ms 13 ms ae-2-0-sur04.longview.wa.bverton.comcast.net [68.87.222.206]
5 19 ms 13 ms 11 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
6 16 ms 19 ms 19 ms he-0-4-0-1-11-cr02.seattle.wa.ibone.comcast.net [68.86.95.93]
7 16 ms 15 ms 15 ms he-0-12-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.82.230]
8 23 ms 18 ms 16 ms as174.seattle.wa.ibone.comcast.net [66.208.228.110]
9 44 ms 44 ms 44 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
10 44 ms 43 ms 44 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
11 701 ms 724 ms * be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
12 68 ms 66 ms 68 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
13 75 ms 90 ms 77 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
14 89 ms 88 ms 89 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
15 92 ms 93 ms 90 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
16 92 ms 91 ms 95 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
17 103 ms 94 ms 101 ms 38.111.40.114
18 90 ms 93 ms 140 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.
...and again (just posting that hop as other times are good as above)...
. . .
10 43 ms 44 ms 44 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
11 713 ms 710 ms 701 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
12 70 ms 71 ms 72 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
. . .
...and a 3rd time (same same)...
. . .
10 98 ms 50 ms 44 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
11 665 ms 695 ms 683 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
12 73 ms 67 ms 68 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
. . .

If you're paying them to use their network service, you're getting ripped off no matter how "affordable" they are.

PLEASE DUMP COGENT!?!?!?
This is my signature. There are many like it, but this one is mine.
Post edited by ovrkyl on

Comments

  • wozronnwozronn Member Posts: 13 Arc User
    edited May 2015
    It's funny that you mention Cogent. I've been playing STO and Champions for a couple of years and every single time I had connection problems, it was Cogent that caused it.
    Yet both Cryptic and PWE keep using it!

    At the moment I'm one pissed off lifetimer. I can't even log in from Australia and sure enough, Cogent is to blame.

    At least during Delta Rising I got to play. It's almost as if PWE rented extra server capacity for the demand, and the net behaved itself.

    Now we're back to rubbish server capacity being provided over a sub-mediocre network, and the money I spent over the last two months (don't tell the wife) is apparently wasted.

    I thought PWE/Cryptic had lifted their game... apparently they only did it for long enough to scrape a gullible userbase for more cash.
  • ovrkylovrkyl Member Posts: 309 Arc User
    edited May 2015
    ...and now it's getting worse!? FFS people, get competent ISP services already! It took hours for me just to cycle my toons to do their DOff/R&D/rep dailies! This is unacceptable!

    One of the hops (the same one as before) pinged at over ONE SECOND!?
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 2 ms 2 ms 2 ms ██.█.█.█
    2 11 ms 8 ms 8 ms ██.███.██.██
    3 11 ms 9 ms 11 ms xe-1-0-0-0-sur03.longview.wa.bverton.comcast.net [68.87.216.241]
    4 12 ms 11 ms 10 ms ae-2-0-sur04.longview.wa.bverton.comcast.net [68.87.222.206]
    5 14 ms 10 ms 14 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
    6 23 ms 20 ms 17 ms he-0-4-0-5-10-cr02.seattle.wa.ibone.comcast.net [68.86.94.181]
    7 19 ms 25 ms 15 ms he-0-12-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.82.230]
    8 17 ms 17 ms 17 ms as174.seattle.wa.ibone.comcast.net [66.208.228.110]
    9 47 ms 47 ms 47 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
    10 45 ms 44 ms 44 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    11 738 ms 1009 ms 968 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    12 70 ms 75 ms 68 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    13 75 ms 75 ms 95 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
    14 192 ms 91 ms 92 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
    15 392 ms 95 ms 91 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
    16 266 ms 102 ms 94 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
    17 394 ms 299 ms 95 ms 38.111.40.114
    18 92 ms 93 ms 93 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.
    And for those critics out there, I've worked SONET in the past and this should never happen! People get fired for this! If Cogent can't maintain their own network, you need to switch to someone that gives a damn about the service they provide their customers.
    This is my signature. There are many like it, but this one is mine.
  • doctordositheusdoctordositheus Member Posts: 29 Arc User
    edited May 2015
    Hey, at least your traffic gets to its destination. My traffic continuously falls into a black hole once it reaches Boston. Darn Internet Gravity Wells!

    C:\Users\[Redacted]>tracert patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 1 ms 2 ms 2 ms [Redacted]
    2 51 ms 51 ms 54 ms [Redacted]
    3 53 ms 52 ms 51 ms dist4-vlan52.chcgil.sbcglobal.net [69.215.47.194
    ]
    4 54 ms 54 ms 55 ms 12.83.106.194
    5 59 ms 59 ms 54 ms 12.122.99.78
    6 54 ms 55 ms 56 ms gar13.cgcil.ip.att.net [12.122.132.121]
    7 54 ms 55 ms 54 ms be2000.ccr21.ord03.atlas.cogentco.com [154.54.12
    .85]
    8 57 ms 56 ms 58 ms be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.7
    3]
    9 70 ms 62 ms 63 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44
    .86]
    10 78 ms 77 ms 77 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25
    .89]
    11 78 ms 78 ms 81 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43
    .9]
    12 80 ms 79 ms 83 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
    om [154.54.46.134]
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 81 ms 80 ms 78 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.

    C:\Users\[Redacted]>tracert patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 1 ms 1 ms <1 ms [Redacted]
    2 52 ms 52 ms 53 ms [Redacted]
    3 57 ms 52 ms 51 ms dist4-vlan52.chcgil.sbcglobal.net [69.215.47.194
    ]
    4 56 ms 55 ms 55 ms 12.83.106.194
    5 57 ms 59 ms 56 ms 12.122.99.78
    6 55 ms 55 ms 56 ms gar13.cgcil.ip.att.net [12.122.132.121]
    7 53 ms 55 ms 57 ms be2000.ccr21.ord03.atlas.cogentco.com [154.54.12
    .85]
    8 53 ms 54 ms 53 ms be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.7
    3]
    9 65 ms 60 ms 62 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44
    .86]
    10 76 ms 77 ms 77 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25
    .89]
    11 78 ms 78 ms 78 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43
    .9]
    12 80 ms 77 ms 82 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
    om [154.54.46.134]
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 79 ms 80 ms 79 ms patchserver2.crypticstudios.com [208.95.185.41]


    Trace complete.


    The least they could do is send me a Hallmark™ card:
    "We are so sorry for your loss (of packets)."
  • ovrkylovrkyl Member Posts: 309 Arc User
    edited May 2015
    doctordositheus wrote: »
    The least they could do is send me a Hallmark™ card:
    "We are so sorry for your loss (of packets)."
    LOL

    When you care enough to send the very best...YOU DON'T USE COGENT!!!

    Cogent honestly is reminding me of those videos of FedEx drivers drop-kicking and throwing packages over fences and all kinds of mayhem. Even if Cryptic fixes the problems with their own game server and software, Cogent's abysmal networking service is going to sabotage it all with their pi$$-poor delivery to the clients.
    This is my signature. There are many like it, but this one is mine.
  • ovrkylovrkyl Member Posts: 309 Arc User
    edited May 2015
    C:\Users\█████>tracert patchserver.crypticstudios.com

    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 2 ms 1 ms 1 ms ██.█.█.█
    2 9 ms 9 ms 8 ms ██.███.██.██
    3 8 ms 11 ms 13 ms xe-1-0-0-0-sur03.longview.wa.bverton.comcast.net [68.87.216.241]
    4 14 ms 8 ms 11 ms ae-2-0-sur04.longview.wa.bverton.comcast.net [68.87.222.206]
    5 32 ms 21 ms 15 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
    6 20 ms 16 ms 16 ms he-0-4-0-4-11-cr02.seattle.wa.ibone.comcast.net [68.86.94.149]
    7 18 ms 16 ms 15 ms he-0-12-0-1-pe05.seattle.wa.ibone.comcast.net [68.86.84.66]
    8 17 ms 18 ms 15 ms 173.167.57.250
    9 * * * Request timed out.
    10 98 ms 95 ms 88 ms internap-gw.customer.alter.net [152.179.134.214]
    11 91 ms 90 ms 165 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
    12 100 ms 91 ms 91 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
     13 94 ms 95 ms 85 ms patchserverrebirth.crypticstudios.com [208.95.185.41]

    Trace complete.
    While I'm showing a leg timing out (and having DC on login issues at the moment, prompting the tracert), the hops highlighted in yellow are different from previous tracerts. Ping is OK to patchserver though.

    :eek: Did they actually stop using Cogent?! :eek:

    :DWOOHOO!!! :D

    Checked the IPs and it looks like, instead of the normal route through Cogent Hell, it took a different route out of Comcast, then ANS Communications, then Internap Network Services Corporation. Checked Cogent's network status and they claim all's well, so I wonder...

    EDITS
    This is my signature. There are many like it, but this one is mine.
  • ovrkylovrkyl Member Posts: 309 Arc User
    edited May 2015
    Tracing route to patchserver.crypticstudios.com [208.95.185.41]
    over a maximum of 30 hops:

    1 1 ms 4 ms 2 ms ██.█.█.█
    2 10 ms 9 ms 8 ms ██.███.██.██
    3 10 ms 10 ms 9 ms xe-1-0-0-0-sur03.longview.wa.bverton.comcast.net [68.87.216.241]
    4 10 ms 8 ms 9 ms ae-2-0-sur04.longview.wa.bverton.comcast.net [68.87.222.206]
    5 62 ms 13 ms 16 ms ae-56-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.209]
    6 19 ms 28 ms 18 ms he-0-4-0-7-11-cr02.seattle.wa.ibone.comcast.net [68.86.93.101]
    7 18 ms 15 ms 20 ms he-0-12-0-1-pe04.seattle.wa.ibone.comcast.net [68.86.82.230]
    8 21 ms 21 ms 16 ms as174.seattle.wa.ibone.comcast.net [66.208.228.110]
    9 44 ms 51 ms 44 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
    10 44 ms 44 ms 52 ms be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65]
    11 74 ms 67 ms 67 ms be2128.ccr21.mci01.atlas.cogentco.com [154.54.25.174]
    12 73 ms 67 ms 66 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
    13 78 ms 73 ms 77 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
    14 90 ms 94 ms 100 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
    15 96 ms 91 ms 90 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
    16 93 ms 91 ms 90 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.com [154.54.46.134]
    17 113 ms 104 ms 103 ms 38.111.40.114
    18 90 ms 93 ms 99 ms patchserverrebirth.crypticstudios.com [208.95.185.41]

    Trace complete.

    Well, doesn't look like they totally dumped Cogent, but there is a noticeable improvement in-game with SNRs, DCs, lag, and rubberbanding compared to 2 days ago. It's not totally lag-free or rid of SNRs and DCs, but it's much more playable. If they're distributing the load among multiple networks or whatever, it's working.

    Thank you, Cryptic!
    This is my signature. There are many like it, but this one is mine.
Sign In or Register to comment.