Hm.

If you're able to, maybe leave the cmd window minimized with "tracert sylestia.com" written in.

Then as soon as you get a hang up, alt tab and press enter and see what the results are?

Got it!

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert sylestia.com

Tracing route to sylestia.com [173.236.9.242]
over a maximum of 30 hops:

1 9 ms 2 ms 2 ms www.routerlogin.com [192.168.1.1]
2 * * * Request timed out.
3 18 ms 55 ms 54 ms ae5-153.core01.smrctx.grandecom.net [216.82.213.254]
4 117 ms 17 ms 12 ms xe-0-1-0.0.aggr02.austtx.grandecom.net [24.155.121.118]
5 64 ms 75 ms 125 ms lag-8-868.ear1.Dallas1.Level3.net [4.30.74.53]
6 * * * Request timed out.
7 83 ms 99 ms 102 ms GIGLINX-INC.bar2.Phoenix1.Level3.net [4.28.83.42]
8 115 ms 99 ms 100 ms agg-c01.d01.s02.phx01.singlehop.net [108.178.63.62]
9 76 ms 99 ms 100 ms aswg-c02.d01.s02.phx01.singlehop.net [108.178.63.58]
10 61 ms 146 ms 202 ms server4.sylestia.com [173.236.9.242]

Trace complete.

C:\WINDOWS\system32>

and


Tracing route to sylestia.com [173.236.9.242]
over a maximum of 30 hops:

1 * * 2 ms www.routerlogin.com [192.168.1.1]
2 * * * Request timed out.
3 240 ms 15 ms 12 ms ae5-153.core01.smrctx.grandecom.net [216.82.213.254]
4 199 ms 117 ms 147 ms xe-0-1-0.0.aggr02.austtx.grandecom.net [24.155.121.118]
5 78 ms 122 ms 86 ms lag-8-868.ear1.Dallas1.Level3.net [4.30.74.53]
6 * * * Request timed out.
7 114 ms 100 ms 83 ms GIGLINX-INC.bar2.Phoenix1.Level3.net [4.28.83.42]
8 110 ms 100 ms 99 ms agg-c01.d01.s02.phx01.singlehop.net [108.178.63.62]
9 111 ms 99 ms 99 ms aswg-c02.d01.s02.phx01.singlehop.net [108.178.63.58]
10 114 ms 94 ms 101 ms server4.sylestia.com [173.236.9.242]

Trace complete.

So, it doesn't look too awful, either of them.

They do seem quite sporadic though... the same node is as low as 12 and as high as 240. That definitely indicates some issues going on. Even in the same trace... 240, then 15, and 12. So something is going on.

The other thing I noticed is on the second one... it couldn't reach your router on the first two attempts. This is probably the most telling issue.

At this point, I'd assume you have an issue with the connection to your router and/or your router to your modem.

I would make sure that all wires are properly connected and are in good condition.


There was actually a player just last week who was reporting the exact same issue and it ended up being a loose connection to their modem from their router.

Ok thank you! I'll have to check my router now >.<