U

Tuesday, November 26th, 2024 1:41 AM

Packet loss Northern Virginia

Tried the Xfinity AIbot to the end. All users, all devices, to all sites on the Internet we've tried.

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

C:\>ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=39ms TTL=56
Reply from 8.8.8.8: bytes=32 time=16ms TTL=56
Reply from 8.8.8.8: bytes=32 time=16ms TTL=56
Reply from 8.8.8.8: bytes=32 time=56ms TTL=56
Reply from 8.8.8.8: bytes=32 time=38ms TTL=56
Request timed out.
Reply from 8.8.8.8: bytes=32 time=28ms TTL=56

Ping statistics for 8.8.8.8:
    Packets: Sent = 7, Received = 6, Lost = 1 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 56ms, Average = 32ms
Control-C
^C


C:\>pathping 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
  0  Fafnir [192.168.0.151]
  1  192.168.0.1
  2     *     172.20.38.243
  3  po-82-rur202.alexandria.va.bad.comcast.net [68.87.131.57]
  4     *     po-2-rur201.alexandria.va.bad.comcast.net [96.110.234.217]
  5  68.86.204.101
  6  be-399-arsc1.capitolhghts.md.bad.comcast.net [96.216.131.253]
  7     *     be-31421-cs02.beaumeade.va.ibone.comcast.net [96.110.40.21]
  8     *     be-3213-pe13.ashburn.va.ibone.comcast.net [68.86.166.214]
  9     *        *        *
Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Fafnir [192.168.0.151]
                                0/ 100 =  0%   |
  1    3ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                               19/ 100 = 19%   |
  2  ---     100/ 100 =100%    81/ 100 = 81%  172.20.38.243
                                0/ 100 =  0%   |
  3   26ms    27/ 100 = 27%     8/ 100 =  8%  po-82-rur202.alexandria.va.bad.comcast.net [68.87.131.57]
                                0/ 100 =  0%   |
  4   25ms    34/ 100 = 34%    15/ 100 = 15%  po-2-rur201.alexandria.va.bad.comcast.net [96.110.234.217]
                                0/ 100 =  0%   |
  5   29ms    26/ 100 = 26%     7/ 100 =  7%  68.86.204.101
                                0/ 100 =  0%   |
  6   36ms    25/ 100 = 25%     6/ 100 =  6%  be-399-arsc1.capitolhghts.md.bad.comcast.net [96.216.131.253]
                                0/ 100 =  0%   |
  7   27ms    19/ 100 = 19%     0/ 100 =  0%  be-31421-cs02.beaumeade.va.ibone.comcast.net [96.110.40.21]
                               81/ 100 = 81%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  be-3213-pe13.ashburn.va.ibone.comcast.net [68.86.166.214]

Trace complete.

Official Employee

 • 

2.2K Messages

6 months ago

 

user_7relre,

Thank you for reaching out and creating a new post. I hope your week has been off to a great start so far. I see you posted some troubleshooting you completed above, and I appreciate you being proactive. I know seeing any type of network issue or latency can be frustrating, but we're here to help. Is this something that just started today? Any recent changes on your end regarding equipment or set-up? 

 

forum icon

New to the Community?

Start Here