Follow up:


My ISP informed me they could not do anything about the situation due to detecting no issue sending packets passed their own servers. Once outside those servers, I'm basicly out of luck. However, the routing gods had mercy on me and have restored me to my former glory. I can successfully connect again. Updated route shown below for historical purposes.





*****************************

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC86U-5C70 [REDACTED]
2 21 ms 7 ms 2 ms REDACTED
3 8 ms 8 ms 8 ms h66-244-251-181.bigpipeinc.com [66.244.251.181]
4 8 ms 8 ms 8 ms rc4fs-be31-100.mt.shawcable.net [66.163.66.82]
5 19 ms 19 ms 18 ms rc3ec-be10.il.shawcable.net [66.163.65.6]
6 26 ms 26 ms 26 ms chi-b23-link.ip.twelve99.net [80.239.128.180]
7 26 ms 26 ms 29 ms ae-25.a06.chcgil09.us.bb.gin.ntt.net [129.250.8.61]
8 27 ms 27 ms 31 ms ae-10.r23.chcgil09.us.bb.gin.ntt.net [129.250.3.37]
9 74 ms 76 ms 75 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 78 ms 78 ms 78 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
11 78 ms 77 ms 78 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
12 * * * Request timed out.
13 78 ms 78 ms 77 ms 204.2.229.10