I know at least one other person lost their connection a few minutes ago, and I know it's some kind of network issue. When my connection broke, I tried to reach the old.armageddon.org site to see if it was a game crash, but the page wouldn't load. Step 2, try to trace the route:
1 2 ms 2 ms 2 ms 10.40.5.1
2 4 ms 5 ms 4 ms 10.255.255.66
3 4 ms 4 ms 4 ms 10.255.3.1
4 17 ms 5 ms 4 ms 168.28.223.131
5 5 ms 5 ms 4 ms 168.28.192.49
6 25 ms 7 ms 6 ms 131.144.208.85
7 13 ms 6 ms 6 ms 131.144.101.2
8 7 ms 5 ms 5 ms gi0-7.na21.b006506-1.atl01.atlas.cogentco.com [38.88.10.209]
9 7 ms 6 ms 6 ms vl3860.mag03.atl01.atlas.cogentco.com [38.20.35.149]
10 6 ms 6 ms 6 ms te0-7-0-10.mpd21.atl01.atlas.cogentco.com [154.54.81.33]
11 20 ms 17 ms 18 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
12 25 ms 24 ms 26 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
13 27 ms 29 ms 30 ms be2357.ccr21.jfk01.atlas.cogentco.com [154.54.43.102]
14 29 ms 32 ms 31 ms te7-1.mag02.jfk01.atlas.cogentco.com [154.54.80.94]
15 25 ms 24 ms 26 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
16 24 ms 23 ms 24 ms 38.105.245.50
17 24 ms 24 ms 25 ms edge-10-teb2.us.as19318.net [66.45.224.182]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
Yep, looks like a network issue. During this time, I also couldn't load the regular armageddon.org webpage. Some time passed (15 min maybe), and now the issue seems to have cleared up. Now the route looks like this:
1 2 ms 2 ms 3 ms 10.40.5.1
2 4 ms 6 ms 4 ms 10.255.255.66
3 4 ms 3 ms 59 ms 10.255.3.1
4 6 ms 4 ms 4 ms 168.28.223.131
5 7 ms 5 ms 5 ms 168.28.192.49
6 5 ms 13 ms 6 ms 131.144.208.85
7 80 ms 218 ms 41 ms 131.144.101.2
8 7 ms 5 ms 6 ms gi0-7.na21.b006506-1.atl01.atlas.cogentco.com [38.88.10.209]
9 7 ms 6 ms 6 ms vl3860.mag03.atl01.atlas.cogentco.com [38.20.35.149]
10 26 ms 6 ms 15 ms te0-7-0-10.mpd21.atl01.atlas.cogentco.com [154.54.81.33]
11 41 ms 18 ms 17 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
12 56 ms 30 ms 23 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
13 30 ms 31 ms 24 ms be2357.ccr21.jfk01.atlas.cogentco.com [154.54.43.102]
14 32 ms 33 ms 43 ms te7-1.mag02.jfk01.atlas.cogentco.com [154.54.80.94]
15 25 ms 30 ms 31 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
16 40 ms 27 ms 26 ms 38.105.245.50
17 33 ms 26 ms 28 ms edge-10-teb2.us.as19318.net [66.45.224.182]
18 25 ms 23 ms 24 ms openvz28.interserver.net [199.231.184.130]
19 24 ms 28 ms 28 ms ginka.armageddon.org [206.72.201.199]
Nice, right? I can load old.armageddon.org and armageddon.org again. Unfortunately, I still can't log in! Neither my usual mud client nor the web client work! I am worried about my character.
Anybody have any words of enlightenment or commiseration?
Edit to add: Curiously, this seems to be different from the atlas.cogentco problem like we had in December. The route was breaking for me closer to ginka, at edge-10-teb2.us.as19318.net, whatever that is. The google did nothing.