It was over before it started . We are now seeing the end of the beginning of the end of the em drive . <| sep |> Yep , so it ' s a situational buff debuff at best . <| sep |> Yeah , happens to me sometimes too . It ' s leftover artifacts graphical remnants from the weekly skillseed chart . Just restart the app and it ' s fine . <| sep |> Nmen d re vl dags att planera fr flytt till annat EUland <| sep |> Feels bad man . Im done with that banner . Gotta buy all the Sale Stones and safe them for SSBK for another disappointment <| sep |> I don ' t know about you guys but The Donald was right when he said we would win so much we would be sick of winning except I ' m not sick of winning yet <| sep |> If what uEk 49 ten suggested doesn ' t work , try this instead . 1 Check what ' s the IP address of your router . It ' s usually something like 192 . 168 . 0 . 1 or 10 . 0 . 0 . 1 , but check it if you ' re not certain . If you never changed that , it will be on the box or on the router itself . If you did , then you should know the address . 2 Check if it ' s an actual issue with network connection or just the DNS . DNS is the thing that translates humanfriendly names like google . com into the IP address that the infrastructure can understand 216 . 58 . 214 . 206 . Open your browser and in the address bar type . If Google loads , you know there ' s a problem with your DNS not translating as it should . Next step depends on your router is it your own hardware that you configured or is it provided by the ISP ? In the latter case , call support and tell them what ' s going on . If it ' s your own equipment , check the configuration and if everything looks good , call the ISP and ask for assistance with configuring the WAN connection . If Google doesn ' t load , the issue is with the connection itself and we need to where is the fault . 3 Trace the route to one of Google ' s servers . Open the command prompt and type tracert 8 . 8 . 8 . 8 . This might take a while but it will show you the exact path of your packets . The first hop should be your router , the second should be somewhere in the infrastructure of your ISP . If the packets can ' t even get to your router , you know you have an inhouse problem . If it reaches the router and then disappears , you can safely call the ISP and ask what ' s going on .