Jump to content

Ping spikes

cheiften98
By cheiften98
in Troubleshooting
 Share
Posted

i made a forum post a couple of days ago but didnt get any replies really. 
sorry for spam.

the last week i keep getting ping spikes. my ping is around 60-100 (depending on the server, time of day and game) which is normal for me but now its around that but every 15-20 seconds it will spike to 300+. pretty much any online game is unplayable atm. ive messaged my ISP but i doubt anything will come from it. 
can anyone help me please :(

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/
Share on other sites
Link to post
Share on other sites
Posted
7 minutes ago, cheiften98 said:

i made a forum post a couple of days ago but didnt get any replies really. 
sorry for spam.

the last week i keep getting ping spikes. my ping is around 60-100 (depending on the server, time of day and game) which is normal for me but now its around that but every 15-20 seconds it will spike to 300+. pretty much any online game is unplayable atm. ive messaged my ISP but i doubt anything will come from it. 
can anyone help me please :(

What kind of internet connect do you have, model of modem, router/AP you have, type of connection to your router/AP. NIC model.

What troubleshooting steps have you done so far?

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544613
Share on other sites
Link to post
Share on other sites
Posted
  • Author
3 minutes ago, ddennis002 said:

What kind of internet connect do you have, model of modem, router/AP you have, type of connection to your router/AP. NIC model.

What troubleshooting steps have you done so far?

ive done the basics. updates network interfaces, restarted pc, router. 
updated firmware on router
ran ccleaner

i have fixed wireless broadband. there is an antenna on top of the house and im using a powerline adaptor so im wired.

its only in the last week tho. last 3 years have been normal. i mean its shit internet but the spikes are abnormal. 

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544622
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, cheiften98 said:

ive done the basics. updates network interfaces, restarted pc, router. 
updated firmware on router

i have fixed wireless broadband. there is an antenna on top of the house and im using a powerline adaptor so im wired.

its only in the last week tho. last 3 years have been normal. i mean its shit internet but the spikes are abnormal. 

try doing a continues ping to google.com and see what your min/max/avg and loss is

 

open command prompt/power shell

copy/paste command below

 

ping google.com -l 1024 -n 1000

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544633
Share on other sites
Link to post
Share on other sites
Posted
  • Author
4 minutes ago, ddennis002 said:

try doing a continues ping to google.com and see what your min/max/avg and loss is

 

open command prompt/power shell

copy/paste command below

 

ping google.com -l 1024 -n 1000

http://prntscr.com/nl6zr

http://prntscr.com/nl7071 this just happend but i was uploading the screenshot. 

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544643
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, cheiften98 said:

http://prntscr.com/nl6zr

http://prntscr.com/nl7071 this just happend but i was uploading the screenshot. 

so its a ping of 1000 packets let it run till the end. And see what the results are.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544666
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ddennis002 said:

so its a ping of 1000 packets let it run till the end. And see what the results are.

oh my bad. will send send again after. thanks for taking the time to help.

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544668
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Spoiler

Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=53ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=55ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=59ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Request timed out.
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=51ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=67ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Request timed out.
Reply from 172.217.17.14: bytes=64 (sent 1024) time=72ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=22ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=57ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=21ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=21ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=111ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=23ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=62ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=56ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=77ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=25ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=81ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=75ms TTL=50

Ping statistics for 172.217.17.14:
    Packets: Sent = 607, Received = 605, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 111ms, Average = 37ms
Control-C
^C
C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

i think i may have cancelled it early as my friend asked to see. i pressed "ctrl a then ctrl c" oops.

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544704
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, cheiften98 said:
  Hide contents

Ping statistics for 172.217.17.14:
    Packets: Sent = 607, Received = 605, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 111ms, Average = 37ms

 

Looks good on that part, try doing this command and post results

 

tracert google.com

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544725
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, cheiften98 said:
  Reveal hidden contents

Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=53ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=55ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=59ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Request timed out.
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=51ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=67ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Request timed out.
Reply from 172.217.17.14: bytes=64 (sent 1024) time=72ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=22ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=57ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=21ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=21ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=111ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=23ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=62ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=56ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=77ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=52ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=36ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=44ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=29ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=50ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=25ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=41ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=35ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=38ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=28ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=34ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=81ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=27ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=43ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=37ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=32ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=45ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=42ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=40ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=47ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=31ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=49ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=30ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=33ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=39ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=46ms TTL=50
Reply from 172.217.17.14: bytes=64 (sent 1024) time=75ms TTL=50

Ping statistics for 172.217.17.14:
    Packets: Sent = 607, Received = 605, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 111ms, Average = 37ms
Control-C
^C
C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

C:\Users\Ben>

i think i may have cancelled it early as my friend asked to see. i pressed "ctrl a then ctrl c" oops.

Try running the command again. From your first image I can see that it is a fairly low end router and that may have something to do with it. If you could run the command above again and reply with the results that appear at the end, that would help a lot.

 

The results will look something like this: 

Ping statistics for 151.101.128.81:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 35ms, Average = 33ms

 

i7-4790k @ 4.7GHz, 16GB DDR3 @1866MHz, MSI Gaming X 8G GTX 1080@2060MHz, 500GB SSD, 2TB Raid 0 HDD, 240GB Raid 0 SSD, EVGA SuperNOVA 850W PSU, Fractal Design Define R5 Windowed

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544728
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, ddennis002 said:

Looks good on that part, try doing this command and post results

 

tracert google.com

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

C:\Users\Ben>tracert google.com

Tracing route to google.com [172.217.17.14]
over a maximum of 30 hops:

  1     3 ms     4 ms     3 ms  192.168.0.1
 

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544730
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, cheiften98 said:

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

C:\Users\Ben>tracert google.com

Tracing route to google.com [172.217.17.14]
over a maximum of 30 hops:

  1     3 ms     4 ms     3 ms  192.168.0.1
 

This will be about 10-20 hops depending on your location. repost when complete.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544733
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, southpaw5271 said:

Try running the command again. From your first image I can see that it is a fairly low end router and that may have something to do with it. If you could run the command above again and reply with the results that appear at the end, that would help a lot.

 

The results will look something like this: 


Ping statistics for 151.101.128.81:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 35ms, Average = 33ms

 

His results are already posted above.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544735
Share on other sites
Link to post
Share on other sites
Posted
  • Author
2 minutes ago, southpaw5271 said:

Try running the command again. From your first image I can see that it is a fairly low end router and that may have something to do with it. If you could run the command above again and reply with the results that appear at the end, that would help a lot.

 

The results will look something like this: 


Ping statistics for 151.101.128.81:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 35ms, Average = 33ms

 

its in the spoiler. right at the bottom. it ran for 600 packets.

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544736
Share on other sites
Link to post
Share on other sites
Posted

C:\Users\windo>tracert google.com

Tracing route to google.com [172.217.4.46]
over a maximum of 30 hops:

  1    72 ms    84 ms    69 ms  192.168.42.1
  2    78 ms    88 ms    84 ms  72.14.232.108
  3    83 ms    91 ms    88 ms  108.170.243.193
  4    73 ms    89 ms    86 ms  216.239.47.129
  5    84 ms    82 ms    85 ms  ord38s18-in-f14.1e100.net [172.217.4.46]

Trace complete.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544737
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ddennis002 said:

C:\Users\windo>tracert google.com

Tracing route to google.com [172.217.4.46]
over a maximum of 30 hops:

  1    72 ms    84 ms    69 ms  192.168.42.1
  2    78 ms    88 ms    84 ms  72.14.232.108
  3    83 ms    91 ms    88 ms  108.170.243.193
  4    73 ms    89 ms    86 ms  216.239.47.129
  5    84 ms    82 ms    85 ms  ord38s18-in-f14.1e100.net [172.217.4.46]

Trace complete.

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

C:\Users\Ben>tracert google.com

Tracing route to google.com [172.217.16.238]
over a maximum of 30 hops:

  1     4 ms     4 ms     3 ms  192.168.0.1
  2     4 ms     4 ms     3 ms  192.168.80.1
  3    31 ms    17 ms     5 ms  172.30.176.1
  4    15 ms    19 ms    10 ms  10.100.207.1
  5    17 ms    23 ms    10 ms  172.17.102.1
  6    15 ms    23 ms    23 ms  172.17.101.1
  7    17 ms    30 ms    24 ms  172.27.0.49
  8    23 ms    42 ms    39 ms  185.66.56.1
  9    35 ms    20 ms    36 ms  svint01-vadavo.redes.vadavo.net [185.123.207.5] 
 10    28 ms    20 ms    21 ms  vadavo-net-es-vlc-nix-cr02.vadavo.net [185.123.204.252]
 11    35 ms    24 ms    25 ms  de-cix.mad.google.com [185.1.68.25]
 12    70 ms    35 ms    43 ms  108.170.253.241
 13   107 ms    30 ms    28 ms  108.170.230.191
 14    53 ms    34 ms    28 ms  mad08s04-in-f14.1e100.net [172.217.16.238]

Trace complete.
 

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544740
Share on other sites
Link to post
Share on other sites
Posted

Again looks good.

 

So this is what I would do. Download PingPlotter

 

What games are giving you issues? Find where those games are connecting to IP address is what you need. 

 

https://www.pingplotter.com/fix-your-network/getting-started/troubleshooting-with-pingplotter.html

 

Here are some basics of how to use the programs. You are going to want to let this run while in your game so it can pull in your network traffic.

 

If you have any question just post and I'll do my best to walk you though it. Once we get a good amount of data when the issue occurs then we can determine where the cause is coming from. Right now it might not be on your end, just from running the tests above.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544766
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, ddennis002 said:

Again looks good.

 

So this is what I would do. Download PingPlotter

 

What games are giving you issues? Find where those games are connecting to IP address is what you need. 

 

https://www.pingplotter.com/fix-your-network/getting-started/troubleshooting-with-pingplotter.html

 

Here are some basics of how to use the programs. You are going to want to let this run while in your game so it can pull in your network traffic.

 

If you have any question just post and I'll do my best to walk you though it. Once we get a good amount of data when the issue occurs then we can determine where the cause is coming from. Right now it might not be on your end, just from running the tests above.

been playng squad and ping goes from 60-90 then spikes to 300 and i teleport around. the new game Mordhau is the same. rocket league and sea of thieves was like 500 ping constant. 
how would i find out the ip for the games i play on. just from the server ip?

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544776
Share on other sites
Link to post
Share on other sites
Posted
Just now, cheiften98 said:

been playng squad and ping goes from 60-90 then spikes to 300 and i teleport around. the new game Mordhau is the same. rocket league and sea of thieves was like 500 ping constant. 
how would i find out the ip for the games i play on. just from the server ip?

google the games, or you can run a program called wireshark to analyze your network traffic

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544781
Share on other sites
Link to post
Share on other sites
Posted
  • Author
14 minutes ago, ddennis002 said:

google the games, or you can run a program called wireshark to analyze your network traffic

how do i enter the IP in ping plotter. 
i think this is it for the server im on
213.32.112.184:7787

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544811
Share on other sites
Link to post
Share on other sites
Posted
  • Author
2 minutes ago, cheiften98 said:

how do i enter the IP in ping plotter. 
i think this is it for the server im on
213.32.112.184:7787

ahhh the 7787 is the port. its running now.
http://prntscr.com/nl7z1w

i guess ill play for 15mins then post.

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544821
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, cheiften98 said:

http://prntscr.com/nl84sx

in game my ping is not that. im around 90 then spiking to 300+
at night or early in the morning (5am) its the same thing.

Are you sure you don't have a Hardware issue? CPU usage, gpu issue lagging, unstable OC, Storage issue. 

As far as a networking point of view everything looks good. And since its effects right now from what we can tell just games. Ping is a measurement of how long it takes for a packet to prepared, packaged, sent, received, then acknowledged. I would say the part of sent and received  and acknowledged looks good. So until otherwise proven the problem most like resides in the prepared and packaged side of things, which is going to depend on the game, and the system processing the data and putting the information into packets to be sent. The delay is somewhere in there.

We know its not game related as its affecting multiple games, so my guess is an issue with the system or windows.

Internet Connection

My Rig: AMD Ryzen 9 3900X @ 4.3Ghz | Asus Prime X470-Pro | Corsair Vengeance RGB Pro 32 GB (4 x 8GB) DDR-4 3000Mhz OC'd @ 3400Mhz 16-20-20-38 |

EVGA RTX 2070 8GB XC Gaming OC @ 2145Mhz Boosted/ 1925Mhz Memory | WD SN750 500GB M.2 NVME | Gigabye 240GB SSD | 
XSPC EX 360mm | Corsair XC7 RGB CPU WB | EK-Vector RTX 2080 | Alphacool Eisbecher D5 150mm Plexi | XSPC Fittings | XSPC FLX Clear 7/16" ID, 5/8" OD |
Corsair LL120 x6 | Corsair RM750x White 2018 | Corsair Commander Pro | Corsair Obsidian 500D RGB SE | Corsair RGB LED Lighting PRO Expansion |
Corsair Strafe RGB MK.2 | Corsair Ironclaw RGB Wireless 18,000DPI | Acer 32" 4K 60Hz HDR600 Cert. ET322QK CBMIIPZX |

Passmark Score

3dmark Score

PC Parts Picker Link to Build

Network

Netgear LBR20 LTE Router | Verizon Unlimited Prepaid Hotspot Plan

HP 2530-48G-PoEP Switch

Rasberry Pi 4 Running Pihole

Linksys Velop 3 Mesh Wifi AP's

 

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544921
Share on other sites
Link to post
Share on other sites
Posted
  • Author
4 minutes ago, ddennis002 said:

Are you sure you don't have a Hardware issue? CPU usage, gpu issue lagging, unstable OC, Storage issue. 

As far as a networking point of view everything looks good. And since its effects right now from what we can tell just games. Ping is a measurement of how long it takes for a packet to prepared, packaged, sent, received, then acknowledged. I would say the part of sent and received  and acknowledged looks good. So until otherwise proven the problem most like resides in the prepared and packaged side of things, which is going to depend on the game, and the system processing the data and putting the information into packets to be sent. The delay is somewhere in there.

We know its not game related as its affecting multiple games, so my guess is an issue with the system or windows.

what could i do to troubleshoot now? my games im playing on are on my ssd.

 

Ryzen 5 5600x, GTX 1070 Duel Asus OC Edition, 16gb ram, Asus Tuf Gaming x570-plus

Link to comment
https://linustechtips.com/topic/1061576-ping-spikes/#findComment-12544933
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×