F5F Stay Refreshed Power Users Networks Connection loss in online games

Connection loss in online games

Connection loss in online games

P
pachi8810
Junior Member
6
09-06-2019, 06:24 PM
#1
someone can assist me with this problem. i recently switched to a fiber internet provider from xfinity. when playing games like cod, madden, or twitch, i experience brief disconnections lasting 2-3 seconds—enough to interrupt my gameplay, but it resolves after about five minutes. i’ve tried everything possible on my pc, cleared dns, reset the modem, and even changed the ethernet cables. the issue occurs both when connected wirelessly and when plugging directly into the modem. netlink reports no network or speed problems, nor packet loss or latency spikes. i still had service with xfinity before, so i connected my old device and it worked fine. after switching to the new fiber service, the problem returns. i’m confused about why this only happens with the new provider.
P
pachi8810
09-06-2019, 06:24 PM #1

someone can assist me with this problem. i recently switched to a fiber internet provider from xfinity. when playing games like cod, madden, or twitch, i experience brief disconnections lasting 2-3 seconds—enough to interrupt my gameplay, but it resolves after about five minutes. i’ve tried everything possible on my pc, cleared dns, reset the modem, and even changed the ethernet cables. the issue occurs both when connected wirelessly and when plugging directly into the modem. netlink reports no network or speed problems, nor packet loss or latency spikes. i still had service with xfinity before, so i connected my old device and it worked fine. after switching to the new fiber service, the problem returns. i’m confused about why this only happens with the new provider.

S
shipflewup
Member
151
09-14-2019, 01:56 AM
#2
An AI could be more capable than some of the basic technicians you interact with at an ISP. You essentially need to carry out their tasks for them. I think they didn’t run enough tests since this happens only every few minutes. It’s a typical test. Start by opening a cmd window and maintaining a steady ping to 8.8.8.8. You should notice packet loss coinciding with problems in the game. If the issue is just the game, it becomes quite complicated because it suggests the problem lies between the ISP the game uses and your own ISP, while there’s no conflict between you and Google. When you see loss to 8.8.8.8, proceed by running tracert 8.8.8.8. This usually doesn’t directly reveal the issue. The main aim is simply to identify the IP addresses of the routers along the path. For most users, you should use the ISP router at the end of your line as a hop, or possibly hop3 if you have multiple routers at home. At this point, try pinging that IP address together with 8.8.8.8. You’re looking for loss to the ISP router at the same time you experience issues in the game. If this happens, you’ll need to gather evidence to present to your ISP, showing they are responsible. You can also perform a ping from your router IP (hop 1) and from the ISP router (hop 2) simultaneously. This should indicate no loss at your router but loss at the ISP router. This strongly suggests the problem isn’t with your equipment or anything inside your home—it becomes apparent once you’re outside. It depends on the ISP’s technical team whether they understand ping commands; they likely use different tools and may detect loss after sufficient testing. Generally, a fiber connection can have issues, but even a small crack somewhere in the path can cause them.
S
shipflewup
09-14-2019, 01:56 AM #2

An AI could be more capable than some of the basic technicians you interact with at an ISP. You essentially need to carry out their tasks for them. I think they didn’t run enough tests since this happens only every few minutes. It’s a typical test. Start by opening a cmd window and maintaining a steady ping to 8.8.8.8. You should notice packet loss coinciding with problems in the game. If the issue is just the game, it becomes quite complicated because it suggests the problem lies between the ISP the game uses and your own ISP, while there’s no conflict between you and Google. When you see loss to 8.8.8.8, proceed by running tracert 8.8.8.8. This usually doesn’t directly reveal the issue. The main aim is simply to identify the IP addresses of the routers along the path. For most users, you should use the ISP router at the end of your line as a hop, or possibly hop3 if you have multiple routers at home. At this point, try pinging that IP address together with 8.8.8.8. You’re looking for loss to the ISP router at the same time you experience issues in the game. If this happens, you’ll need to gather evidence to present to your ISP, showing they are responsible. You can also perform a ping from your router IP (hop 1) and from the ISP router (hop 2) simultaneously. This should indicate no loss at your router but loss at the ISP router. This strongly suggests the problem isn’t with your equipment or anything inside your home—it becomes apparent once you’re outside. It depends on the ISP’s technical team whether they understand ping commands; they likely use different tools and may detect loss after sufficient testing. Generally, a fiber connection can have issues, but even a small crack somewhere in the path can cause them.