Had massive issues the past day or two (worse than normal lately, if that's possible) with really bad ping times on tracerts through Cogent Hell contributing to SERVER NOT RESPONDING and DCs.
Checked my tracert tonight though, due to a DC on login, and the route is way different. No sign of Cogent. Took a different path through ANS Communications and Internap Network Services Corporation networks. As Cogent's network status claims all's well, makes me wonder if Cryptic finally dumped ol' Cogent. Here's hoping...
Yes, I posted my tracerts and issues in the bug forums, but I'm just wondering if anyone has info on this development.
This is my signature. There are many like it, but this one is mine.
Had massive issues the past day or two (worse than normal lately, if that's possible) with really bad ping times on tracerts through Cogent Hell contributing to SERVER NOT RESPONDING and DCs.
Checked my tracert tonight though, due to a DC on login, and the route is way different. No sign of Cogent. Took a different path through ANS Communications and Internap Network Services Corporation networks. As Cogent's network status claims all's well, makes me wonder if Cryptic finally dumped ol' Cogent. Here's hoping...
Yes, I posted my tracerts and issues in the bug forums, but I'm just wondering if anyone has info on this development.
If people don't see the 38.111.x.x, then no more Cogent. I'll remote in after this meeting and check.
We'll be moving digital pipe thingies from one thingy to another thingy! This may cause a little trouble as they pull the pipe thing over. I think? That's mostly metaphorical.
Either way, good stuff!
"Logic is a little tweeting bird chirping in a meadow. Logic is a wreath of pretty flowers which smell BAD." - Spock
Whatever the change to thingies is, it sure made a sudden increase in SNR and DCs.
Also worth noting is when logging in to a character, the spawn zone on rare occasion happens to be an object which gets you stuck, or forces you into an area that you shouldn't be with no way back without changing instance, assuming there is an open instance to change to.
if these network issues are solved, i hope the bt lines in my area freshly upgraded optic connections will come online soon to their full speed, then, yeah probably running at 10 ms or less all the way to the boston server. who knows.. assuming the whole line is optic along the way and those copper lines are done away with.
T6 Miranda Hero Ship FTW. Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
Had massive issues the past day or two (worse than normal lately, if that's possible) with really bad ping times on tracerts through Cogent Hell contributing to SERVER NOT RESPONDING and DCs.
Checked my tracert tonight though, due to a DC on login, and the route is way different. No sign of Cogent. Took a different path through ANS Communications and Internap Network Services Corporation networks. As Cogent's network status claims all's well, makes me wonder if Cryptic finally dumped ol' Cogent. Here's hoping...
Yes, I posted my tracerts and issues in the bug forums, but I'm just wondering if anyone has info on this development.
That could explain why I've for the most part been able to play again.
Whatever the change to thingies is, it sure made a sudden increase in SNR and DCs.
Also worth noting is when logging in to a character, the spawn zone on rare occasion happens to be an object which gets you stuck, or forces you into an area that you shouldn't be with no way back without changing instance, assuming there is an open instance to change to.
If they performed a "hot swap", you'd see SNR's and dc's for certain groups going through the old 38.111.x.x
Looks like they did some clean-up and a new backbone:
us1.proxy.crypticstudios.com [208.95.184.152]
8 20 ms 19 ms 19 ms mai-b1-link.telia.net [62.115.40.145]
9 40 ms 39 ms 38 ms ash-bb4-link.telia.net [62.115.141.80]
10 45 ms 92 ms 79 ms nyk-bb2-link.telia.net [62.115.138.26]
11 50 ms 51 ms 51 ms bost-b1-link.telia.net [80.91.248.193]
12 52 ms 53 ms 53 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
13 54 ms 54 ms 55 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
14 63 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
15 * * * Request timed out.
16 52 ms 51 ms 51 ms us1.proxy.crypticstudios.com [208.95.184.152]
8 19 ms 19 ms 17 ms mai-b1-link.telia.net [62.115.40.145]
9 40 ms 38 ms 37 ms ash-bb4-link.telia.net [62.115.141.125]
10 43 ms 43 ms 42 ms nyk-bb2-link.telia.net [213.155.130.74]
11 47 ms 47 ms 47 ms bost-b1-link.telia.net [80.91.248.193]
12 64 ms 51 ms 53 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
13 52 ms 52 ms 69 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
14 60 ms 54 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
15 52 ms 51 ms 51 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
It looks like Cogent is still there in my traces, but the numbers are good so far:
7 18 ms 23 ms 15 ms bbr01sgnwmi-bue-5.sgnw.mi.charter.com [96.34.0.55]
8 21 ms 19 ms 20 ms be4309.rcr21.dtw04.atlas.cogentco.com [38.122.60.49]
9 24 ms 23 ms 23 ms be2006.ccr21.cle04.atlas.cogentco.com [154.54.5.9]
10 36 ms 35 ms 43 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
11 39 ms 39 ms 40 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
12 40 ms 39 ms 43 ms te0-0-1-0.rcr12.b002133-1.bos01.atlas.cogentco.com [66.28.4.42]
13 41 ms 42 ms 41 ms 38.104.252.70
14 44 ms 43 ms 43 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
15 41 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 40 ms 44 ms 41 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
It looks like Cogent is still there in my traces, but the numbers are good so far:
7 18 ms 23 ms 15 ms bbr01sgnwmi-bue-5.sgnw.mi.charter.com [96.34.0.55]
8 21 ms 19 ms 20 ms be4309.rcr21.dtw04.atlas.cogentco.com [38.122.60.49]
9 24 ms 23 ms 23 ms be2006.ccr21.cle04.atlas.cogentco.com [154.54.5.9]
10 36 ms 35 ms 43 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
11 39 ms 39 ms 40 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
12 40 ms 39 ms 43 ms te0-0-1-0.rcr12.b002133-1.bos01.atlas.cogentco.com [66.28.4.42]
13 41 ms 42 ms 41 ms 38.104.252.70
14 44 ms 43 ms 43 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
15 41 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 40 ms 44 ms 41 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Cogent is in your Trace at the beginning possibly because your ISP provider uses Cogent as their pathing source at some point. Cogent would be at the end if Cryptic were still using them. They are not show showing up anywhere in my TraceRt, so either Cryptic dropped Cogent or Cogent is now now hiding their information.
STO is about my Liberated Borg Federation Captain with his Breen 1st Officer, Jem'Hadar Tactical Officer, Liberated Borg Engineering Officer, Android Ops Officer, Photonic Science Officer, Gorn Science Officer, and Reman Medical Officer jumping into their Jem'Hadar Carrier and flying off to do missions for the new Romulan Empire. But for some players allowing a T5 Connie to be used breaks the canon in the game.
Tracing route to patchserverrebirth.crypticstudios.com [208.95.185.41]
7 38 ms 39 ms 38 ms Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]
8 113 ms 112 ms 112 ms ae3.cr1.lga5.us.zip.zayo.com [64.125.21.205]
9 114 ms 113 ms 113 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
10 118 ms 118 ms 118 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
11 113 ms 114 ms 115 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
12 114 ms 125 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 113 ms 112 ms 111 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Trace complete.
thats from my end. no sign of cogent at all.
T6 Miranda Hero Ship FTW. Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
I'll be monitoring that, as that's one of my hops to Cryptic.
internap-ic-304640-bost-b1.c.telia.net is on the Boston Exchange.
I'm just guessing here, but...
Partial load-balancing? Partial routing QoL improvements? Partial cleaning up of the physical and virtual net's between PWE and Cryptic? Cheaper infrastructure budget and better management on their end of the network? Better quality communication/routing between data centers?
I haven't had time to drill down through everything, but it looks like PWE/Cryptic reorganized their network on their side and set up some sort of unified private network further upstream to handle the traffic better for all of their services. Some of us who were coming in from Cogent are now pathed through other networks. This is could be a good thing, as they won't necessarily have to rely on one major backbone feeding them the traffic in one physical location. I'm guessing it might give them more options to shop around or make a deal w/ other backbones to feed them data, and reroute traffic as needed via backbones if one particular one has issues for whatever reason?
I'll need to get info from other people who were also seeing Cogent prior to PWE or Cryptic networks at Boston.
Really would like to talk to one of their network engineers and see what their roadmap is going forward.
Here's some info for you, darkknightucf, if it helps.
From Thu28May2015@0328±PDT (pre-maintenance):
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.
From Fri29May2015@0013±PDT (post-maintenance):
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.
Changed hops in yellow.
From Fri29May2015@1430±PDT (now):
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.
Damn, and I thought they'd gotten rid of them. Looks like your theories may be correct, darkknightucf. But at least there's a noticeable improvement, so far. If Cryptic wants the player load, at least it looks like they're anticipating and accommodating it (finally).
This is my signature. There are many like it, but this one is mine.
Comments
If people don't see the 38.111.x.x, then no more Cogent. I'll remote in after this meeting and check.
Fleet Defiant Kinetic Heavy Fire Support | Fleet Manticore Kinetic Strike Ship | Tactical Command Kinetic Siege Refit | Fleet Defiant Quantum Phase Escort | Fleet Valiant Kinetic Heavy Fire Support
Turning the Galaxy-X into a Torpedo Dreadnought & torpedo tutorial, with written torpedo guide.
"A good weapon and a great strategy will win you many battles." - Marshall
I knew using Kinetics would be playing the game on hard mode, but what I didn't realize was how bad the deck is stacked against Kinetics.
Also worth noting is when logging in to a character, the spawn zone on rare occasion happens to be an object which gets you stuck, or forces you into an area that you shouldn't be with no way back without changing instance, assuming there is an open instance to change to.
Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
That could explain why I've for the most part been able to play again.
If they performed a "hot swap", you'd see SNR's and dc's for certain groups going through the old 38.111.x.x
Looks like they did some clean-up and a new backbone:
us1.proxy.crypticstudios.com [208.95.184.152]
8 20 ms 19 ms 19 ms mai-b1-link.telia.net [62.115.40.145]
9 40 ms 39 ms 38 ms ash-bb4-link.telia.net [62.115.141.80]
10 45 ms 92 ms 79 ms nyk-bb2-link.telia.net [62.115.138.26]
11 50 ms 51 ms 51 ms bost-b1-link.telia.net [80.91.248.193]
12 52 ms 53 ms 53 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
13 54 ms 54 ms 55 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
14 63 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
15 * * * Request timed out.
16 52 ms 51 ms 51 ms us1.proxy.crypticstudios.com [208.95.184.152]
****************************************************************
patchserver.crypticstudios.com [208.95.185.41]
8 19 ms 19 ms 17 ms mai-b1-link.telia.net [62.115.40.145]
9 40 ms 38 ms 37 ms ash-bb4-link.telia.net [62.115.141.125]
10 43 ms 43 ms 42 ms nyk-bb2-link.telia.net [213.155.130.74]
11 47 ms 47 ms 47 ms bost-b1-link.telia.net [80.91.248.193]
12 64 ms 51 ms 53 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
13 52 ms 52 ms 69 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
14 60 ms 54 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
15 52 ms 51 ms 51 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
****************************************************************
I kept older results, and no more Cogent in the mix from my ISP (BrightHouse to RoadRunner hand-off).
Fleet Defiant Kinetic Heavy Fire Support | Fleet Manticore Kinetic Strike Ship | Tactical Command Kinetic Siege Refit | Fleet Defiant Quantum Phase Escort | Fleet Valiant Kinetic Heavy Fire Support
Turning the Galaxy-X into a Torpedo Dreadnought & torpedo tutorial, with written torpedo guide.
"A good weapon and a great strategy will win you many battles." - Marshall
I knew using Kinetics would be playing the game on hard mode, but what I didn't realize was how bad the deck is stacked against Kinetics.
7 18 ms 23 ms 15 ms bbr01sgnwmi-bue-5.sgnw.mi.charter.com [96.34.0.55]
8 21 ms 19 ms 20 ms be4309.rcr21.dtw04.atlas.cogentco.com [38.122.60.49]
9 24 ms 23 ms 23 ms be2006.ccr21.cle04.atlas.cogentco.com [154.54.5.9]
10 36 ms 35 ms 43 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25.89]
11 39 ms 39 ms 40 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43.9]
12 40 ms 39 ms 43 ms te0-0-1-0.rcr12.b002133-1.bos01.atlas.cogentco.com [66.28.4.42]
13 41 ms 42 ms 41 ms 38.104.252.70
14 44 ms 43 ms 43 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
15 41 ms 53 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 40 ms 44 ms 41 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
7 38 ms 39 ms 38 ms Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]
8 113 ms 112 ms 112 ms ae3.cr1.lga5.us.zip.zayo.com [64.125.21.205]
9 114 ms 113 ms 113 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
10 118 ms 118 ms 118 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
11 113 ms 114 ms 115 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
12 114 ms 125 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 113 ms 112 ms 111 ms patchserverrebirth.crypticstudios.com [208.95.185.41]
Trace complete.
thats from my end. no sign of cogent at all.
Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
http://www.dslreports.com/routerwatch/hbg-bb2-link.telia.net
I'll be monitoring that, as that's one of my hops to Cryptic.
internap-ic-304640-bost-b1.c.telia.net is on the Boston Exchange.
I'm just guessing here, but...
Partial load-balancing? Partial routing QoL improvements? Partial cleaning up of the physical and virtual net's between PWE and Cryptic? Cheaper infrastructure budget and better management on their end of the network? Better quality communication/routing between data centers?
I haven't had time to drill down through everything, but it looks like PWE/Cryptic reorganized their network on their side and set up some sort of unified private network further upstream to handle the traffic better for all of their services. Some of us who were coming in from Cogent are now pathed through other networks. This is could be a good thing, as they won't necessarily have to rely on one major backbone feeding them the traffic in one physical location. I'm guessing it might give them more options to shop around or make a deal w/ other backbones to feed them data, and reroute traffic as needed via backbones if one particular one has issues for whatever reason?
I'll need to get info from other people who were also seeing Cogent prior to PWE or Cryptic networks at Boston.
Really would like to talk to one of their network engineers and see what their roadmap is going forward.
Fleet Defiant Kinetic Heavy Fire Support | Fleet Manticore Kinetic Strike Ship | Tactical Command Kinetic Siege Refit | Fleet Defiant Quantum Phase Escort | Fleet Valiant Kinetic Heavy Fire Support
Turning the Galaxy-X into a Torpedo Dreadnought & torpedo tutorial, with written torpedo guide.
"A good weapon and a great strategy will win you many battles." - Marshall
I knew using Kinetics would be playing the game on hard mode, but what I didn't realize was how bad the deck is stacked against Kinetics.
From Thu28May2015@0328±PDT (pre-maintenance):
From Fri29May2015@0013±PDT (post-maintenance): Changed hops in yellow.
From Fri29May2015@1430±PDT (now):
Damn, and I thought they'd gotten rid of them. Looks like your theories may be correct, darkknightucf. But at least there's a noticeable improvement, so far. If Cryptic wants the player load, at least it looks like they're anticipating and accommodating it (finally).