1 Message
Packet drops pretty bad causing issues with Zoom calls, etc.
I have switched routers and modems.
This is still occurring. It has to be the inbound line from Xfinity.
What can I do to resolve this it is very very annoying while i am trying to work!
This is via a direct connection to the router via ethernet cable.
Do I need to schedule a service call to resolve? It is definetly an issue with the cable line. i have restarted everything and also changed cables etc. Still an issue.
Thanks
PING google.com (142.250.191.78): 56 data bytes
64 bytes from 142.250.191.78: icmp_seq=0 ttl=116 time=15.728 ms
64 bytes from 142.250.191.78: icmp_seq=1 ttl=116 time=16.644 ms
64 bytes from 142.250.191.78: icmp_seq=2 ttl=116 time=16.387 ms
64 bytes from 142.250.191.78: icmp_seq=3 ttl=116 time=17.345 ms
64 bytes from 142.250.191.78: icmp_seq=4 ttl=116 time=14.451 ms
64 bytes from 142.250.191.78: icmp_seq=5 ttl=116 time=19.474 ms
64 bytes from 142.250.191.78: icmp_seq=6 ttl=116 time=14.938 ms
64 bytes from 142.250.191.78: icmp_seq=7 ttl=116 time=16.577 ms
64 bytes from 142.250.191.78: icmp_seq=8 ttl=116 time=17.973 ms
64 bytes from 142.250.191.78: icmp_seq=9 ttl=116 time=14.430 ms
64 bytes from 142.250.191.78: icmp_seq=10 ttl=116 time=18.043 ms
64 bytes from 142.250.191.78: icmp_seq=11 ttl=116 time=15.537 ms
64 bytes from 142.250.191.78: icmp_seq=12 ttl=116 time=18.060 ms
64 bytes from 142.250.191.78: icmp_seq=13 ttl=116 time=17.229 ms
64 bytes from 142.250.191.78: icmp_seq=14 ttl=116 time=19.129 ms
64 bytes from 142.250.191.78: icmp_seq=15 ttl=116 time=16.591 ms
64 bytes from 142.250.191.78: icmp_seq=16 ttl=116 time=18.414 ms
64 bytes from 142.250.191.78: icmp_seq=17 ttl=116 time=15.987 ms
64 bytes from 142.250.191.78: icmp_seq=18 ttl=116 time=18.031 ms
64 bytes from 142.250.191.78: icmp_seq=19 ttl=116 time=16.509 ms
64 bytes from 142.250.191.78: icmp_seq=20 ttl=116 time=18.189 ms
64 bytes from 142.250.191.78: icmp_seq=21 ttl=116 time=13.940 ms
64 bytes from 142.250.191.78: icmp_seq=22 ttl=116 time=47.533 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
64 bytes from 142.250.191.78: icmp_seq=25 ttl=116 time=16.534 ms
64 bytes from 142.250.191.78: icmp_seq=26 ttl=116 time=14.235 ms
64 bytes from 142.250.191.78: icmp_seq=27 ttl=116 time=14.772 ms
64 bytes from 142.250.191.78: icmp_seq=28 ttl=116 time=19.435 ms
64 bytes from 142.250.191.78: icmp_seq=29 ttl=116 time=17.575 ms
64 bytes from 142.250.191.78: icmp_seq=30 ttl=116 time=15.645 ms
64 bytes from 142.250.191.78: icmp_seq=31 ttl=116 time=14.039 ms
64 bytes from 142.250.191.78: icmp_seq=32 ttl=116 time=13.864 ms
64 bytes from 142.250.191.78: icmp_seq=33 ttl=116 time=28.977 ms
64 bytes from 142.250.191.78: icmp_seq=34 ttl=116 time=13.691 ms
64 bytes from 142.250.191.78: icmp_seq=35 ttl=116 time=19.507 ms
64 bytes from 142.250.191.78: icmp_seq=36 ttl=116 time=15.217 ms
64 bytes from 142.250.191.78: icmp_seq=37 ttl=116 time=18.913 ms
64 bytes from 142.250.191.78: icmp_seq=38 ttl=116 time=16.179 ms
64 bytes from 142.250.191.78: icmp_seq=39 ttl=116 time=14.481 ms
64 bytes from 142.250.191.78: icmp_seq=40 ttl=116 time=13.840 ms
64 bytes from 142.250.191.78: icmp_seq=41 ttl=116 time=16.559 ms
64 bytes from 142.250.191.78: icmp_seq=42 ttl=116 time=14.640 ms
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
64 bytes from 142.250.191.78: icmp_seq=45 ttl=116 time=14.422 ms
64 bytes from 142.250.191.78: icmp_seq=46 ttl=116 time=16.259 ms
64 bytes from 142.250.191.78: icmp_seq=47 ttl=116 time=13.855 ms
64 bytes from 142.250.191.78: icmp_seq=48 ttl=116 time=14.597 ms
64 bytes from 142.250.191.78: icmp_seq=49 ttl=116 time=15.137 ms
64 bytes from 142.250.191.78: icmp_seq=50 ttl=116 time=26.072 ms
64 bytes from 142.250.191.78: icmp_seq=51 ttl=116 time=15.417 ms
64 bytes from 142.250.191.78: icmp_seq=52 ttl=116 time=15.464 ms
64 bytes from 142.250.191.78: icmp_seq=53 ttl=116 time=17.299 ms
64 bytes from 142.250.191.78: icmp_seq=54 ttl=116 time=17.978 ms
64 bytes from 142.250.191.78: icmp_seq=55 ttl=116 time=20.076 ms
64 bytes from 142.250.191.78: icmp_seq=56 ttl=116 time=21.470 ms
64 bytes from 142.250.191.78: icmp_seq=57 ttl=116 time=18.352 ms
64 bytes from 142.250.191.78: icmp_seq=58 ttl=116 time=22.830 ms
Request timeout for icmp_seq 59
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
64 bytes from 142.250.191.78: icmp_seq=65 ttl=116 time=22.701 ms
64 bytes from 142.250.191.78: icmp_seq=66 ttl=116 time=16.616 ms
64 bytes from 142.250.191.78: icmp_seq=67 ttl=116 time=13.308 ms
XfinityThomasB
Official Employee
•
1.5K Messages
1 month ago
Hello user_iml5pj
Was the service initially self installed or was the service setup by one our techs? I was also curious if this is an xFi gateway or owned and managed personally? Thank you!
Ethernet cables carry a specific category rating that determines max speeds. The higher the category, the faster the cable. For assistance with installation of select equipment and services not covered by Xfinity, see HelloTech overview.
If you use your own router along with your gateway, make sure the gateway is in Bridge Mode. Learn more about Bridge Mode. You'll also want to position the antennae of your router so that one is pointing vertically (12 o'clock), and the other one is pointing horizontally (either three or nine o'clock) to broadcast the strongest signal.
Visit our Online Support Center to find common solutions and self-help options, troubleshoot or manage your account, and more.
0
0