Popping in today with an update.
My game connection appears to be stable and functional tonight!

I did run a tracert to each of the 3 IPs I did before, just for comparison:

204.2.29.6
Code:
  6    12 ms    12 ms    12 ms  64.15.5.82
  7    11 ms    13 ms    20 ms  ae88.edge2.NewYork6.Level3.net [4.30.181.89]
  8    13 ms    20 ms    17 ms  NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
  9    14 ms    12 ms    14 ms  ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129]
 10    34 ms    40 ms    35 ms  ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
 11    41 ms    40 ms    37 ms  ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
 12    78 ms    82 ms    80 ms  ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13    92 ms    88 ms    85 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 14    86 ms    85 ms    82 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 15     *       81 ms     *     204.2.29.241
 16    83 ms    84 ms    83 ms  204.2.29.6
This result is consistent with the results I was getting yesterday. Same locations, same general communication times - except for the 12th hop, at 129.250.5.17. My results yesterday for that hop were consistently 200+, or timing out.

204.2.229.9
Code:
  6    12 ms    18 ms    17 ms  rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42]
  7    17 ms    29 ms    11 ms  ae88.edge2.NewYork6.Level3.net [4.30.181.89]
  8    15 ms    16 ms    13 ms  NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
  9    14 ms    16 ms    13 ms  ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50]
 10    88 ms    85 ms    87 ms  ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146]
 11    86 ms    86 ms    87 ms  ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183]
 12   102 ms   100 ms    99 ms  ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13]
 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     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
This result is also consistent with my tests run yesterday.

204.2.29.122
Code:
  6    13 ms    19 ms    13 ms  64.15.1.88
  7    13 ms    16 ms    12 ms  ae88.edge2.NewYork6.Level3.net [4.30.181.89]
  8    13 ms    15 ms    12 ms  NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
  9    16 ms    12 ms    12 ms  ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129]
 10    39 ms    34 ms    33 ms  ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
 11    43 ms    36 ms    34 ms  ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
 12    77 ms    99 ms     *     ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13    82 ms    83 ms    84 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 14    86 ms    81 ms    80 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 15     *        *        *     Request timed out.
 16    81 ms    81 ms    91 ms  204.2.29.122
These results are mostly consistent with yesterdays - except, again, the 12th hop at 129.250.5.17, which was often at 200+ or timing out yesterday.

To me, it looks like that particular node was having some sort of issue, which has now been resolved!