Question Ping spikes almost every 11 minutes or so on second hop ?

[Fixmypingplease]

Basically as the title says I've been having short bursts of high latency on a wired connection for over 2 weeks. I pinged to 8.8.8.8 and traced the first, second and last hops. I also did this after disconnecting every other device connected to the network, then tried the same thing on a different computer. Both computers show the same results of the ping spiking on the second hop very consistently at about 11 minute intervals. In my head that makes me think that it is the router having problems reaching the second hop. I've only just began trying to learn about all of this in the last few days though so I was hoping to get other opinions on what the problem could be.

https://share.pingplotter.com/BwqGDP6k55J.png

Top graph is the second hop
Middle graph is the final hop
Bottom graph is the first hop

I'm not sure why the first hop shows a lot of packet-loss but from what I've read on other posts is to not worry about it as these pings are low priority and will show that type of packet loss sometimes.

 

[Ralston18]

Make and model modem? Make and model Router? Or Make & model modem/router if combined?

ISP?

Do three things:

1) Run and post the results of "ipconfig /all" (without quotes) via the Command Prompt.

2) Run and post the results of "pathping 8.8.8.8." (without quote) via the Command Prompt.

3) Run and post the results of "tracert 8.8.8.8" (without quotes) via the Command Prompt.

 

[Fixmypingplease]

Modem/Router is the xfi xb6

ISP is Xfinity

Ipconfig all results:

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

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-04C5HV4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.ct.comcast.net

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . : hsd1.ct.comcast.net
Description . . . . . . . . . . . : Realtek Gaming 2.5GbE Family Controller
Physical Address. . . . . . . . . : 04-7C-16-86-80-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:18b:8100:3c30::7822(Preferred)
Lease Obtained. . . . . . . . . . : Sunday, July 9, 2023 2:27:12 AM
Lease Expires . . . . . . . . . . : Wednesday, July 12, 2023 7:30:31 PM
IPv6 Address. . . . . . . . . . . : 2601:18b:8100:3c30:ab54:4e4b:5a26:4d9a(Preferred)
Temporary IPv6 Address. . . . . . : 2601:18b:8100:3c30:bda9:58a1:6342:ee9e(Preferred)
Link-local IPv6 Address . . . . . : fe80::a2aa:243e:c2c:1eb6%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.215(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, July 9, 2023 2:23:20 AM
Lease Expires . . . . . . . . . . : Tuesday, July 11, 2023 7:09:37 PM
Default Gateway . . . . . . . . . : fe80::461c:12ff:fed9:8a35%10
10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 100957206
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-FA-9E-0F-A8-A1-59-43-34-9D
DNS Servers . . . . . . . . . . . : 2001:558:feed::1
2001:558:feed::2
1.1.1.1
8.8.8.8
2001:558:feed::1
2001:558:feed::2
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : 70-D8-23-9C-5B-E0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : 72-D8-23-9C-5B-DF
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.ct.comcast.net
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX211 160MHz
Physical Address. . . . . . . . . : 70-D8-23-9C-5B-DF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2
Physical Address. . . . . . . . . : 70-D8-23-9C-5B-E3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Path Ping Results:

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

C:\WINDOWS\system32>pathping 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
0 DESKTOP-04C5HV4.hsd1.ct.comcast.net [10.0.0.215]
1 10.0.0.1
2 100.92.58.66
3 po-302-321-rur101.killngwrth81.ct.hartford.comcast.net [68.85.143.249]
4 68.86.230.134
5 96.108.68.221
6 96.108.68.165
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-04C5HV4.hsd1.ct.comcast.net [10.0.0.215]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 100.92.58.66
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% po-302-321-rur101.killngwrth81.ct.hartford.comcast.net [68.85.143.249]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% 68.86.230.134
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% 96.108.68.221
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% 96.108.68.165

Trace complete.

Tracert Results:

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

C:\Users\antho>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 10.0.0.1
2 12 ms 9 ms 11 ms 100.92.58.66
3 13 ms 8 ms 11 ms po-302-321-rur101.killngwrth81.ct.hartford.comcast.net [68.85.143.249]
4 10 ms 11 ms 9 ms 68.86.230.134
5 9 ms 11 ms 10 ms 96.108.68.221
6 12 ms 12 ms 9 ms 96.108.68.165
7 * * * Request timed out.
8 17 ms 14 ms 16 ms be-501-ar01.needham.ma.boston.comcast.net [162.151.52.34]
9 26 ms 30 ms 19 ms be-32021-cs02.newyork.ny.ibone.comcast.net [96.110.42.5]
10 20 ms 19 ms 31 ms be-3212-pe12.111eighthave.ny.ibone.comcast.net [96.110.34.38]
11 44 ms 22 ms 22 ms 66.208.229.86
12 21 ms 21 ms 21 ms 142.251.225.89
13 23 ms 20 ms 21 ms 142.251.60.227
14 21 ms 24 ms 23 ms dns.google [8.8.8.8]

Trace complete.

 

[bill001g]

I would first disable IPv6 on your pc and maybe on your router if you can.
It might affect your actual machine performance but it does not explain the pingplot results that are using IPv4. IPv6 has little benefit and causes strange issues for some people so you might as well disable it. If you are lucky it will resolve your actual issue and the pingplotter data might just be testing error.

Packet loss tends to be easier to explain and and get the ISP to fix. It tends to be due to some defective cable or device.

Ping/latency spikes are due to some device holding the data. This most times is due to some kind of overload condition. It most times is over use of some data connection ie you have 100mbps internet and you tried to use 110mbps. It can also be a cpu overload condition. You can check your data usage to see if you might exceed your ISP bandwidth you buy but in your case it is not likely, the pings look different they are not just single spikes.

It is not likely your router but you can check. I would make sure no fancy features are enabled. Things like parantal controls or really anything else that looks at traffic can be a issue. All these can use CPU and a router cpu is tiny. Normally I would say make sure the firmware is upgraded and reset the router to factory setting only the admin and wifi passwords. When you have a modem/router combo you generally have no ability to change the firmware and limited ability to reset and configure things.

It is not likely but it really is the only thing you have any control over.

You could also I guess load a linux USB boot image and see if you see similar issues and/or try a different device in your house. In general network problem that affect ping/trace that are related to the pc will also show up in hop 1. It could in theory I guess be hidden by the fake loss in the testing.

After this you are kinda stuck. Most this is in the ISP control and the ISP tends to only care about packet loss. Their testing equipment can easily detect say a wire that is getting too much signal derogation but a cable does not have a memory buffer to store data so it can't affect the ping times. These are tricky to get resolved because it is either some overload of the ISP infrastructure which they tend to not want to admit or some equipment has some issue. The first level techs generally do not have the skills to fix these kind of problems. All you can do is pester them. If you lease the modem maybe see if they will blindly replace it for you. Not likely the issue but maybe you get lucky.

 

[Fixmypingplease]

Gotcha, I greatly appreciate all the advice. I'll go through and check each of these and will give an update if anything solves it.

 

[Ralston18]

What devices are connected?

Most home networks are set up as follows (line diagram where --- > represents an Ethernet cable):

ISP === (DSL, Coax, Fiber) ==> Modem --- > [WAN Port] Router [LAN ports] --- > wired devices and ~~~ > wireless to wireless devices.

Modem and router may be combined.

Feel free to edit and correct my line diagram as necessary. Include all devices and connections.

Make and model information for modem and router?

 

[Fixmypingplease]

What devices are connected?

Most home networks are set up as follows (line diagram where --- > represents an Ethernet cable):

ISP === (DSL, Coax, Fiber) ==> Modem --- > [WAN Port] Router [LAN ports] --- > wired devices and ~~~ > wireless to wireless devices.

Modem and router may be combined.

Feel free to edit and correct my line diagram as necessary. Include all devices and connections.

Make and model information for modem and router?

Our setup is ISP === Coax ==> Modem/Router combo --> my PC
As for wireless there are a lot connected:
2 Roku Tvs
3 Phones
2 laptops
2 Amazon Tablets
1 Alexa
I did try resetting the wifi password to disconnect all these and test the ping on my pc with nothing connected and still got the spikes. Then did the same with a laptop after disconnecting the pc from the network.

Router is xfi xb6 from xfinity.

 

[Ralston18]

Are you able to access the router's admin menus by typing 10.0.0.1 into a browser?

You will need the router's login name and password.

 

[Fixmypingplease]

Are you able to access the router's admin menus by typing 10.0.0.1 into a browser?

You will need the router's login name and password.

So after getting a new modem(Xfinity xb7) today and the ping has been steady for over an hour with the exception of one 250ms spike. Which is still promising to me since the previous results showed 2 spikes next to each other and they were 10 times the size of this one. Just in case though, I do know how to access the admin menu so what would I be doing if the issue comes back?

 

[Ralston18]

XB7: Modem/router combo - correct?

This device?

https://support.meetcircle.com/hc/e...XB6, also,Providers to their internet service

= = = =

What you would be doing is looking for log entries/errors that correspond with the times of the spikes.

Or anything else that might start happening.

My suggestion is to begin monitoring the logs now making it more likely that you will note some change or changes from the normal router activities.

Verify that the logs are being saved in some manner and at least not immediately deleted after some configured amount of time.

Overall, become as knowledgeable and familar as you can with the xb7.

Just in case the spiking returns.

 

[Fixmypingplease]

Yeah that's the one.
Gotcha, I'll start doing this from now on. I appreciate all the help, thanks!