1 Message
Problems with internet traffic
I cannot connect to work today and conference calls keep dropping out. When pinging 8.8.8.8 I see extremely high latency and request timeout messages.
64 bytes from 8.8.8.8: icmp_seq=165 ttl=57 time=14.571 ms
64 bytes from 8.8.8.8: icmp_seq=166 ttl=57 time=15.548 ms
64 bytes from 8.8.8.8: icmp_seq=167 ttl=57 time=15.467 ms
64 bytes from 8.8.8.8: icmp_seq=168 ttl=57 time=15.601 ms
64 bytes from 8.8.8.8: icmp_seq=169 ttl=57 time=14.683 ms
64 bytes from 8.8.8.8: icmp_seq=170 ttl=57 time=15.834 ms
64 bytes from 8.8.8.8: icmp_seq=171 ttl=57 time=12.978 ms
64 bytes from 8.8.8.8: icmp_seq=172 ttl=57 time=16.904 ms
64 bytes from 8.8.8.8: icmp_seq=173 ttl=57 time=15.266 ms
64 bytes from 8.8.8.8: icmp_seq=174 ttl=57 time=20.264 ms
64 bytes from 8.8.8.8: icmp_seq=175 ttl=57 time=17.882 ms
Request timeout for icmp_seq 176
Request timeout for icmp_seq 177
Request timeout for icmp_seq 178
Request timeout for icmp_seq 179
Request timeout for icmp_seq 180
Request timeout for icmp_seq 181
Request timeout for icmp_seq 182
Request timeout for icmp_seq 183
Request timeout for icmp_seq 184
Request timeout for icmp_seq 185
Request timeout for icmp_seq 186
Request timeout for icmp_seq 187
Request timeout for icmp_seq 188
Request timeout for icmp_seq 189
64 bytes from 8.8.8.8: icmp_seq=176 ttl=57 time=14629.891 ms
64 bytes from 8.8.8.8: icmp_seq=177 ttl=57 time=13625.692 ms
64 bytes from 8.8.8.8: icmp_seq=178 ttl=57 time=12623.267 ms
64 bytes from 8.8.8.8: icmp_seq=179 ttl=57 time=11618.498 ms
64 bytes from 8.8.8.8: icmp_seq=180 ttl=57 time=10614.476 ms
64 bytes from 8.8.8.8: icmp_seq=181 ttl=57 time=9612.053 ms
64 bytes from 8.8.8.8: icmp_seq=182 ttl=57 time=8607.284 ms
64 bytes from 8.8.8.8: icmp_seq=183 ttl=57 time=7604.430 ms
64 bytes from 8.8.8.8: icmp_seq=184 ttl=57 time=6599.163 ms
64 bytes from 8.8.8.8: icmp_seq=185 ttl=57 time=5597.520 ms
64 bytes from 8.8.8.8: icmp_seq=186 ttl=57 time=4595.801 ms
64 bytes from 8.8.8.8: icmp_seq=187 ttl=57 time=3591.370 ms
64 bytes from 8.8.8.8: icmp_seq=188 ttl=57 time=2588.083 ms
64 bytes from 8.8.8.8: icmp_seq=189 ttl=57 time=1583.303 ms
64 bytes from 8.8.8.8: icmp_seq=190 ttl=57 time=579.540 ms
64 bytes from 8.8.8.8: icmp_seq=191 ttl=57 time=23.341 ms
64 bytes from 8.8.8.8: icmp_seq=192 ttl=57 time=19.483 ms
64 bytes from 8.8.8.8: icmp_seq=193 ttl=57 time=22.299 ms
64 bytes from 8.8.8.8: icmp_seq=194 ttl=57 time=20.311 ms
64 bytes from 8.8.8.8: icmp_seq=195 ttl=57 time=9.881 ms
BruceW
Gold Problem Solver
•
26.8K Messages
2 years ago
Ping is helpful in identifying problems, but doesn't do much to help us understand what's causing them. Also it's best to ping a web server rather than a DNS server.
Are you connecting via Wifi or Ethernet? If Wifi, it's best to switch to an Ethernet cable connection if possible for testing. That would allow you to determine whether the problem is the Wifi signal or the link between your modem or gateway and Comcast's network. Network connection problems that affect both Ethernet and Wifi devices are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.
If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you still need help, please post your Internet plan speed and the following information from your modem or gateway (from http://192.168.100.1 or http://10.0.0.1):
Copy and pasted text is preferred over images. Be aware that, if you post any images, your message will be made Private for a time, as all images must be approved by the Forum Moderators before the messages containing them become generally visible.
If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.
If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.
(edited)
0
0
XfinityBenjaminM
Official Employee
•
2.5K Messages
2 years ago
@user_bwf4zs Hello! We just wanted to check and see if you had a chance to review the information that our amazing Gold Problem Solver @BruceW provided you? If you are still in need of any assistance, please let us know.
(edited)
0
0