connection errors

[Strider_xiii]

Here it is with the vpn set to ny which works

4 31 ms 13 ms 7 ms be6080.ccr31.jfk04.atlas.cogentco.com [38.104.72.1]
5 18 ms 9 ms 7 ms be3363.ccr42.jfk02.atlas.cogentco.com [154.54.3.125]
6 13 ms 8 ms 7 ms be3496.ccr31.jfk10.atlas.cogentco.com [154.54.0.142]
7 17 ms 11 ms 9 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
8 18 ms 9 ms 11 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 39 ms 40 ms 35 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 34 ms 32 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 98 ms 91 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 90 ms 99 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 82 ms 78 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 81 ms 81 ms * 204.2.29.241
15 81 ms 79 ms 83 ms 204.2.29.122

[DDRDiesel]

Here it is with the vpn set to ny which works

4 31 ms 13 ms 7 ms be6080.ccr31.jfk04.atlas.cogentco.com [38.104.72.1]
5 18 ms 9 ms 7 ms be3363.ccr42.jfk02.atlas.cogentco.com [154.54.3.125]
6 13 ms 8 ms 7 ms be3496.ccr31.jfk10.atlas.cogentco.com [154.54.0.142]
7 17 ms 11 ms 9 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
8 18 ms 9 ms 11 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 39 ms 40 ms 35 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 34 ms 32 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 98 ms 91 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 90 ms 99 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 82 ms 78 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 81 ms 81 ms * 204.2.29.241
15 81 ms 79 ms 83 ms 204.2.29.122

Thanks, that's a huge help with your other post. It seems when you're on the VPN, which is functional, you aren't going through the nodes owned by twelve99, but playing normally you're being routed through them then back to the NTT pathing. So it's hard to say if the NTT node is actually the problem or if it's a forwarding issue from the twelve99 nodes to the NTT nodes thereafter. This is something that has to be looked at and investigated by SE and their L2/L3 backbone partners, unfortunately I won't be able to investigate much further as that's where the general population's access stops