High/unstable ping on my wired connection but normal ping on a wireless laptop in the same room

Toggle sidebar Toggle sidebar
J

JamesMc19

Reputable
Sep 27, 2016
53
0
4,540
As the title says im getting high/unstable ping (fluctuates between 25 and 150) on my pc (wired connection) and using a laptop on the same internet but connected wireless is getting normal ping (~25). The game i tested this on was league of legends but it seems to carry over to other games to, just not as bad. I also tried connecting through wifi but for some reason i am unable to connect wirelessly, which could be linked.

Yesterday i did a reset of my pc and have so far only reinstalled the essentials, it was fine for a bit but has since started being unstable again.

Not sure if specs are needed but here they are anyway:
CPU: AMD fx 6300
MoBo: GIGABYTE GA-970A-UD3P.
OS: Windows 10
HDD: 1TB Seagate Barracuda Hard Drive 3.5" SATA III - ST1000DM003
RAM: Ballistix Sport 8GB (2x4GB) 1600MHz CL9 DDR3
GPU: Radeon R9 270x
PSU: EVGA 500W

If anything else is needed please ask.

EDIT: I am now able to connect through wifi but the problem still persists.

EDIT 2: Hooked my laptop up directly to the router through a wired connection and still saw regular spikes. I think its safe to assume that its an ISP problem now unless there could be other factors. Will take this thread down if needed since the problem is no longer as specific as the title suggests.
 
Sort by date Sort by votes
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
35,033
3,356
146,290
Ensure that your Ethernet cable is fully and firmly connected on both ends.

Try another known working Ethernet cable.

Verify that your network adapter is fully and firmly seated inside the pc.

Download, reinstall, and reconfigure the network adapter's drivers via the manufacturer's website.
 
Upvote 0 Downvote
J

JamesMc19

Reputable
Sep 27, 2016
53
0
4,540


Ok so i was able to gain a connection to wifi, and reinstalled on network drivers. However the problem still persists. I'm not sure if something is running in the background and soaking it all up but its definitely a fault within my pc.
 
Upvote 0 Downvote
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
35,033
3,356
146,290
Run Task Manager and Resource Monitor (one at a time) to observe what is going on with your system.

Just explore, get a sense of the tools and the information provided.

Remember that you can click the column headers to sort %'s etc. being presented.


 
Upvote 0 Downvote
J

JamesMc19

Reputable
Sep 27, 2016
53
0
4,540


Ran some tests as recommended and there are spikes but it seems that my pc isnt the only one affected anymore. Hooked my laptop up directly to the router through a wired connection and still saw regular spikes. I think its safe to assume that its an ISP problem now unless there could be other factors?
 
Upvote 0 Downvote
J

JamesMc19

Reputable
Sep 27, 2016
53
0
4,540


I pinged my router and google simultaneously as i went into a practice game of LoL and got the following results:

To Google:

Pinging google.com [172.217.23.46] with 32 bytes of data:
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=26ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=17ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=18ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=31ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=23ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=58ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=24ms TTL=54
Reply from 172.217.23.46: bytes=32 time=141ms TTL=54
Reply from 172.217.23.46: bytes=32 time=34ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=27ms TTL=54
Reply from 172.217.23.46: bytes=32 time=23ms TTL=54
Reply from 172.217.23.46: bytes=32 time=465ms TTL=54
Reply from 172.217.23.46: bytes=32 time=46ms TTL=54
Reply from 172.217.23.46: bytes=32 time=80ms TTL=54
Reply from 172.217.23.46: bytes=32 time=15ms TTL=54
Reply from 172.217.23.46: bytes=32 time=56ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=18ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=39ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=15ms TTL=54
Reply from 172.217.23.46: bytes=32 time=28ms TTL=54
Reply from 172.217.23.46: bytes=32 time=121ms TTL=54
Reply from 172.217.23.46: bytes=32 time=66ms TTL=54
Reply from 172.217.23.46: bytes=32 time=23ms TTL=54
Reply from 172.217.23.46: bytes=32 time=18ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=30ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=118ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=129ms TTL=54
Reply from 172.217.23.46: bytes=32 time=16ms TTL=54
Reply from 172.217.23.46: bytes=32 time=104ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=102ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=91ms TTL=54
Reply from 172.217.23.46: bytes=32 time=71ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=329ms TTL=54
Reply from 172.217.23.46: bytes=32 time=185ms TTL=54
Reply from 172.217.23.46: bytes=32 time=112ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=98ms TTL=54
Reply from 172.217.23.46: bytes=32 time=15ms TTL=54
Reply from 172.217.23.46: bytes=32 time=88ms TTL=54
Reply from 172.217.23.46: bytes=32 time=53ms TTL=54
Reply from 172.217.23.46: bytes=32 time=117ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=97ms TTL=54
Reply from 172.217.23.46: bytes=32 time=24ms TTL=54
Reply from 172.217.23.46: bytes=32 time=43ms TTL=54
Reply from 172.217.23.46: bytes=32 time=16ms TTL=54
Reply from 172.217.23.46: bytes=32 time=113ms TTL=54
Reply from 172.217.23.46: bytes=32 time=16ms TTL=54
Reply from 172.217.23.46: bytes=32 time=167ms TTL=54
Reply from 172.217.23.46: bytes=32 time=120ms TTL=54
Reply from 172.217.23.46: bytes=32 time=118ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=204ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=129ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=317ms TTL=54
Reply from 172.217.23.46: bytes=32 time=14ms TTL=54
Reply from 172.217.23.46: bytes=32 time=148ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=72ms TTL=54
Reply from 172.217.23.46: bytes=32 time=126ms TTL=54
Reply from 172.217.23.46: bytes=32 time=69ms TTL=54
Reply from 172.217.23.46: bytes=32 time=120ms TTL=54
Reply from 172.217.23.46: bytes=32 time=123ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=146ms TTL=54
Reply from 172.217.23.46: bytes=32 time=19ms TTL=54
Reply from 172.217.23.46: bytes=32 time=12ms TTL=54
Reply from 172.217.23.46: bytes=32 time=13ms TTL=54
Reply from 172.217.23.46: bytes=32 time=92ms TTL=54
Reply from 172.217.23.46: bytes=32 time=31ms TTL=54

Ping statistics for 172.217.23.46:
Packets: Sent = 103, Received = 103, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 465ms, Average = 57ms

To my router:
Packets: Sent = 194, Received = 194, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 122ms, Average = 26ms
(Will just post this just incase but ping is stable for a a few seconds then spikes which is the problem im facing in game but it seems both tests proved to be fairly negative).

EDIT: Just ran a tracert to facebook.

tracert Facebook.com

Tracing route to Facebook.com [157.240.20.35]
over a maximum of 30 hops:

1 4 ms 3 ms 4 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 12 ms 12 ms 11 ms 31.55.185.180
5 66 ms 178 ms 57 ms core1-hu0-8-0-1.colindale.ukcore.bt.net [195.99.127.144]
6 13 ms 12 ms 12 ms core3-hu0-8-0-0.faraday.ukcore.bt.net [195.99.127.36]
7 12 ms 19 ms 13 ms 62.6.201.145
8 12 ms 11 ms 12 ms 213.137.183.96
9 42 ms 29 ms 39 ms t2c4-xe-1-0-1-0.de-fra.eu.bt.net [166.49.208.38]
10 * * * Request timed out.
11 31 ms 32 ms 31 ms po141.asw01.fra2.tfbnw.net [204.15.21.250]
12 32 ms 31 ms 37 ms po211.psw04.fra3.tfbnw.net [204.15.21.85]
13 34 ms 78 ms 87 ms 157.240.36.123
14 30 ms 30 ms 30 ms edge-star-mini-shv-02-frt3.facebook.com [157.240.20.35]

Trace complete.
 
Upvote 0 Downvote
J

JamesMc19

Reputable
Sep 27, 2016
53
0
4,540


I believe it's ADSL and im just using a router.

Ran a pathping to facebook again and one to google. Here are the results:

pathping Facebook.com

Tracing route to Facebook.com [157.240.20.35]
over a maximum of 30 hops:
0 xxx.xxx.x.xxx
1 BTHUB [xxx.xxx.x.xxx]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 xxx.xxx.x.xxx
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% BTHUB [xxx.xxx.x.xxx]

Trace complete.

and

pathping -n Facebook.com

Tracing route to Facebook.com [157.240.20.35]
over a maximum of 30 hops:
0 xxx.xxx.x.xxx
1 xxx.xxx.x.xxx
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 xxx.xxx.x.xxx
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% xxx.xxx.x.xxx

Trace complete.
 
Upvote 0 Downvote
Ralston18

Ralston18

Titan
Moderator
Oct 11, 2014
35,033
3,356
146,290
ASDL.

Take a look at your incoming service connection from your ISP.

Somewhere along the way there should be a small device that splits the wire into two paths.

One path to your telephone(s) and the other path to your modem (BTHUB) or modem/router.

Splitters (also call filters) can be problematic. Since multiple devices are now being affected it may be worth while to replace the splitter.

Here are a couple of links with discussion, diagrams, and photographs.

https://mybroadband.co.za/vb/showthread.php/902617-Telkom-supplied-splitter-filter-question

http://www.steves-internet-guide.com/networking-components/

Easy to find other similar links and related videos.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom