As title says, my route to SE's server destination has changed. Or at least it seems to have changed. The New York hop never appeared before.
Code:
Tracing route to 199.91.189.39 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 10.1.10.1
3 9 ms 8 ms 7 ms 96.120.36.173
4 7 ms 9 ms 7 ms xe-11-2-2-sur01.gardens.fl.pompano.comcast.net [68.85.83.241]
5 10 ms 17 ms 9 ms xe-4-1-3-0-ar02.stuart.fl.pompano.comcast.net [162.151.42.173]
6 14 ms 13 ms 12 ms hu-0-9-0-1-ar01.northdade.fl.pompano.comcast.net [69.139.182.37]
7 * 14 ms 18 ms ae13.edge2.Miami1.Level3.net [4.68.62.149]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 50 ms 69 ms 51 ms ae-101-101.ebr1.Washington12.Level3.net [4.69.204.229]
13 52 ms 50 ms 50 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.214]
14 * * * Request timed out.
15 * 43 ms 43 ms ae-1-11.ebr4.NewYork1.Level3.net [4.69.204.198]
16 51 ms 49 ms 49 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
17 49 ms 50 ms 50 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
18 50 ms 49 ms 50 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
19 72 ms 72 ms 72 ms 192.34.76.10
20 72 ms 71 ms 72 ms 199.91.189.242
21 72 ms 81 ms 72 ms 199.91.189.39
Trace complete.
Code:
Pinging 199.91.189.39 with 32 bytes of data:
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=73ms TTL=239
Reply from 199.91.189.39: bytes=32 time=72ms TTL=239
Reply from 199.91.189.39: bytes=32 time=71ms TTL=239
Ping statistics for 199.91.189.39:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 73ms, Average = 72ms
SE may manage to keep me as a customer after all. I hope others who have been experiencing this gawd awful lags over the past few months have also had it sorted out as well.