Game Down 1/24/2018

[wehr]

Team,

Seems like the game is down, looking at both tcp port 4000 and 6000 there are no responsive.
C:\Users\xxxx>nping -tcp -p 4000 jedimud.net

Starting Nping 0.7.60 ( nmap.org/nping ) at 2018-01-24 17:36 Eastern Sta
ndard Time
SENT (3.4160s) TCP 192.168.1.137:65511 > 50.4.82.130:4000 S ttl=64 id=50339 iple
n=40 seq=2235279642 win=1480
SENT (6.1460s) TCP 192.168.1.137:65511 > 50.4.82.130:4000 S ttl=64 id=50339 iple
n=40 seq=2235279642 win=1480
SENT (7.1600s) TCP 192.168.1.137:65511 > 50.4.82.130:4000 S ttl=64 id=50339 iple
n=40 seq=2235279642 win=1480
SENT (8.1740s) TCP 192.168.1.137:65511 > 50.4.82.130:4000 S ttl=64 id=50339 iple
n=40 seq=2235279642 win=1480
SENT (9.1880s) TCP 192.168.1.137:65511 > 50.4.82.130:4000 S ttl=64 id=50339 iple
n=40 seq=2235279642 win=1480

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 5 (270B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)
Nping done: 1 IP address pinged in 10.20 seconds

C:\Users\xxxxx>nping -tcp -p 6000 jedimud.net

Starting Nping 0.7.60 ( nmap.org/nping ) at 2018-01-24 17:36 Eastern Sta
ndard Time
SENT (3.0730s) TCP 192.168.1.137:19925 > 50.4.82.130:6000 S ttl=64 id=62186 iple
n=40 seq=713102092 win=1480
SENT (5.7250s) TCP 192.168.1.137:19925 > 50.4.82.130:6000 S ttl=64 id=62186 iple
n=40 seq=713102092 win=1480
SENT (6.7390s) TCP 192.168.1.137:19925 > 50.4.82.130:6000 S ttl=64 id=62186 iple
n=40 seq=713102092 win=1480
SENT (7.7530s) TCP 192.168.1.137:19925 > 50.4.82.130:6000 S ttl=64 id=62186 iple
n=40 seq=713102092 win=1480
SENT (8.7670s) TCP 192.168.1.137:19925 > 50.4.82.130:6000 S ttl=64 id=62186 iple
n=40 seq=713102092 win=1480

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 5 (270B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)
Nping done: 1 IP address pinged in 9.78 seconds

[DaHart85]

AP lost power, will be back up when he regains it