About my current internet . . .

JohnOPPAI08

Prominent
Aug 5, 2017
29
0
530
So lets see i dont know where to begin but maybe you guys can give me advice. Currently my internet speed is only 2mbps which is common from where i live. i usually dont have problems with this speed its just something to do with the sending and reciving of data? i dont know what its called. for example when i select videos on youtube it takes so much time to play from the start, but when i try downloading on steam the speed stay the same. and it just so frustrating that other can log in to uplay but i cant. i tried port forwarding, change dns, also tried flushing dns on my current games it work in the past but now it doent apply anymore.
 
Go to speedtest.net (if it takes too long to load go to "Alternative) and post results here, both upload and download, and watch out for caps.

Alternative: Type in start CMD, right click and run it as administrator (should be named Command Prompt), then type in "", "ping 8.8.8.8 -n 30" -n means numbers of times to ping that server.

Try also 1.1.1.1

Those are DNS, if the dns is high i will suggest you an VPN.
 
If your speed is 2MBPS, no amount of port forwarding or DNS changes will help you. Gaming is most likely out of the question.

A good simple way to test your actual speed is url=https://fast.com/]fast.com[/url] (sponsored by Netflix)

YouTube and many other video providers has technology that will reduce the amount of data they stream to lower quality and resolution to match your bandwidth. The same is not applicable to Steam and games.
 

JohnOPPAI08

Prominent
Aug 5, 2017
29
0
530
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1743ms TTL=44
Reply from 8.8.8.8: bytes=32 time=65ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=61ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=60ms TTL=44
Reply from 8.8.8.8: bytes=32 time=61ms TTL=44
Reply from 8.8.8.8: bytes=32 time=61ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=61ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=64ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=60ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44
Reply from 8.8.8.8: bytes=32 time=64ms TTL=44
Reply from 8.8.8.8: bytes=32 time=63ms TTL=44
Reply from 8.8.8.8: bytes=32 time=61ms TTL=44
Reply from 8.8.8.8: bytes=32 time=62ms TTL=44

Ping statistics for 8.8.8.8:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 1743ms, Average = 118ms

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=53ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=56ms TTL=52
Reply from 1.1.1.1: bytes=32 time=63ms TTL=52
Reply from 1.1.1.1: bytes=32 time=57ms TTL=52

Ping statistics for 1.1.1.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 63ms, Average = 55ms

-PING = 49 ms
-DOWNLOAD = 1.92 Mbps
-UPLOAD 0.38 = Mbps

 

JohnOPPAI08

Prominent
Aug 5, 2017
29
0
530
its funny that in Rainbow six siege i have this problem on getting into the server but once i got in i dont encounter any problems only in getting in its always said that their servers are not reachable and there are not even in maintenance
 
You got more stable ping with 1.1.1.1 dns, you can change that by typing in start network and sharing center, then to Change adapter settings, on local area connection right click it properties, then double click internet protocol version 4,
Window should pop up,
Tick/select Use the following dns server addresses type in it 1.1.1.1 and as alternative 1.0.0.1
I used it for 1-2 weeks but it seems that it has some instability at some points.
But try it out anyways.

https://1.1.1.1/#setup-instructions