Skip to main content

    Support

    Offers

Bommer4's profile
Bommer4
1st Topic
1st Like

Visitor

 • 

8 Messages

Tuesday, September 28th, 2021 4:37 PM

Closed

Loses all internet connect for 30-1 minute every hour or so

Every hour or so I lose all my internet connectivity. When playing games Ill be told i'll have packetloss of around 50%. https://imgur.com/a/Ip0Xqeo This is a screen shot of right after when it happens. 

Question

 • 

Updated 

4 years ago

156

5

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

EG

Expert

 • 

111.7K Messages

4 years ago

The packet loss begins right at your own home network / gateway device. Is this with a WiFi connection ? If so, for a test, does a computer / device that is hardwired directly to the router / gateway device with an ethernet cable have the same problem ?

1

0

Bommer4

Visitor

 • 

8 Messages

@EG The test was done with ethernet directly into Xfinity Gateway 

4 years ago

0

EG

Expert

 • 

111.7K Messages

4 years ago

There could be a problem with your computer / NIC (Network Adapter), the ethernet cable, or the gateway itself. If you are using a flavor of the Windows O/S, open a command prompt window and issue this command: ping -n 50 127.0.0.1 When it completes, copy the text output and paste it in your next post here.

(edited)

1

0

Bommer4

Visitor

 • 

8 Messages

@EG Well I've trouble shooted all cables. And PC. This also happened on my other old router before I switched over to the xfinity one. Don't think you'll get much from this. Also keep in mind that this happens intermittently. 

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

(edited)

4 years ago

0

EG

Expert

 • 

111.7K Messages

4 years ago

That tested your computer / network adapter. No packet loss there. Now, lets test your ethernet cable and gateway device. Use this command: ping -n 50 10.0.0.1

1

0

Bommer4

Visitor

 • 

8 Messages

@EG 

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=14ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 14ms, Average = 1ms

4 years ago

0

EG

Expert

 • 

111.7K Messages

4 years ago

Hmmm...... That's strange. The Pingplotter output clearly showed 50% packet loss right at the gateway's IP...... Please try one more test. Use the same command but change the IP address to that of your Comcast WAN default gateway's address (hop #2 on the Pingplotter output).

1

0

Bommer4

Visitor

 • 

8 Messages

@EG

Pinging 96.120.40.241 with 32 bytes of data:
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=15ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=23ms TTL=254
Reply from 96.120.40.241: bytes=32 time=15ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=14ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=15ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=6ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=13ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=14ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=6ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=6ms TTL=254
Reply from 96.120.40.241: bytes=32 time=14ms TTL=254

Ping statistics for 96.120.40.241:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 23ms, Average = 9ms

4 years ago

0

EG

Expert

 • 

111.7K Messages

4 years ago

Well none of the tests have revealed the issue except for the Pingplotter, sorry. Are you still experiencing the issue ?

2

0

Bommer4

Visitor

 • 

8 Messages

@EG Yes I am. Did it again while it was happening, because it only happens like once an hour or so

Pinging 96.120.40.241 with 32 bytes of data:
Reply from 96.120.40.241: bytes=32 time=42ms TTL=254
Reply from 96.120.40.241: bytes=32 time=33ms TTL=254
Request timed out.
Request timed out.
Reply from 96.120.40.241: bytes=32 time=16ms TTL=254
Reply from 96.120.40.241: bytes=32 time=39ms TTL=254
Reply from 96.120.40.241: bytes=32 time=87ms TTL=254
Reply from 96.120.40.241: bytes=32 time=20ms TTL=254
Request timed out.
Reply from 96.120.40.241: bytes=32 time=24ms TTL=254
Request timed out.
Reply from 96.120.40.241: bytes=32 time=34ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 96.120.40.241: bytes=32 time=26ms TTL=254
Request timed out.
Reply from 96.120.40.241: bytes=32 time=31ms TTL=254
Reply from 96.120.40.241: bytes=32 time=18ms TTL=254
Reply from 96.120.40.241: bytes=32 time=52ms TTL=254
Request timed out.
Reply from 96.120.40.241: bytes=32 time=29ms TTL=254
Reply from 96.120.40.241: bytes=32 time=25ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 96.120.40.241: bytes=32 time=16ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=36ms TTL=254
Reply from 96.120.40.241: bytes=32 time=13ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=30ms TTL=254
Reply from 96.120.40.241: bytes=32 time=26ms TTL=254
Reply from 96.120.40.241: bytes=32 time=14ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=8ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=10ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=7ms TTL=254
Reply from 96.120.40.241: bytes=32 time=16ms TTL=254
Reply from 96.120.40.241: bytes=32 time=12ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=23ms TTL=254
Reply from 96.120.40.241: bytes=32 time=11ms TTL=254
Reply from 96.120.40.241: bytes=32 time=9ms TTL=254
Reply from 96.120.40.241: bytes=32 time=13ms TTL=254
Reply from 96.120.40.241: bytes=32 time=18ms TTL=254

Ping statistics for 96.120.40.241:
    Packets: Sent = 50, Received = 40, Lost = 10 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 87ms, Average = 20ms

4 years ago

0

Bommer4

Visitor

 • 

8 Messages

While that was also happening I did on to 10.0.0.1 and it showed no packetloss

4 years ago

0

forum icon

New to the Community?

Start Here