High ping nightly at around 10 PM with new ISP -- only FFXIV affected

[thrashette]

Hello, I recently switched from Verizon DSL (3 mbps) to Comcast (250 mbps). 3 mbps is no longer sufficient bandwidth for my needs, so I simply can't switch back. However, I haven't gotten around to deactivating Verizon yet, so I'm able to troubleshoot using my old network.

What's happening is, every night, at around 10 PM, my ping spikes to over 200 ms. The lag makes it hard to even craft or gather, and I occasionally disconnect. No other services are affected, and as you can see in the traceroutes provided below, the congestion is not on my end nor on my ISP's.

I am not an expert on these things, but it simply appears as though I'm being placed on a congested route on NTT's end from wherever the midpoint between my ISP and NTT are.

I'm wondering if this is an issue I should contact my ISP about. I'm unsure who owns the "midpoint" routers and whether or not my ISP would have control over that part of my route. Regardless, it appears to me as though specific NTT servers are becoming overloaded at peak time, while others are unaffected. I've had the same result with my desktop, laptop, and even my mobile phone.


Here is the "good" route with Verizon (high ping on hop 2 because Wi-Fi):

Tracing route to 204.2.229.10 over a maximum of 30 hops

  1     1 ms     4 ms     1 ms  verizon.home [192.168.1.1]
  2    30 ms    13 ms    15 ms  10.4.50.1
  3     *       14 ms    14 ms  P0-1-1-2.BLTMMD-LCR-21.verizon-gni.net [130.81.135.98]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    17 ms    16 ms    17 ms  0.et-5-3-0.BR1.IAD8.ALTER.NET [140.222.239.79]
  7    18 ms    17 ms    17 ms  ae-4.r06.asbnva02.us.bb.gin.ntt.net [129.250.8.209]
  8    18 ms    17 ms    17 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
  9    77 ms    77 ms    78 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
 10    80 ms    82 ms    83 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 11    80 ms    80 ms    82 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 12    81 ms    94 ms    83 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 13    81 ms    81 ms    81 ms  204.2.229.234
 14    97 ms    80 ms    80 ms  204.2.229.10

Here's the "bad" route with Comcast (wired):

Tracing route to 204.2.229.10 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  10.0.0.1
  2    11 ms    10 ms     9 ms  96.120.104.129
  3     9 ms     8 ms    10 ms  ae-34-rur01.princefrdrck.md.bad.comcast.net [68.85.80.21]
  4     8 ms    10 ms    10 ms  68.85.133.162
  5    10 ms    10 ms    10 ms  68.85.133.97
  6    11 ms    10 ms    11 ms  ae-13-ar01.capitolhghts.md.bad.comcast.net [68.87.168.61]
  7    13 ms    14 ms    11 ms  be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
  8    12 ms    13 ms    13 ms  be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
  9    11 ms    11 ms    12 ms  ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
 10   201 ms     *      197 ms  ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
 11    13 ms    13 ms    13 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
 12   211 ms   217 ms   207 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
 13   197 ms   214 ms     *     ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14   214 ms   203 ms   212 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15   207 ms   208 ms   205 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16     *      204 ms   200 ms  204.2.229.234
 17   202 ms   198 ms   190 ms  204.2.229.10

Any help or insight would be appreciated.


EDIT: Never mind, I guess I'm blind. The route appears to go straight from Comcast to NTT with no "midpoint," and the high ping begins on NTT's routers.