Hi,
So before we get started I'd like show roughly what I am experiencing and request a ticket (as no ticket # was given to me about this issue).
Here is what my ping to Google looks like after October 28, 2019. I've had 2 techs do test, replace modem, put a noise barrier etc.
Ping statistics for 216.58.217.46:
Packets: Sent = 40, Received = 29, Lost = 11 (27% loss),
Reply from 216.58.217.46: Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 35ms, Average = 27ms
Roughly about. 1/4 of my packets are being lost. The 2nd tech that came through told me that an building upgrade was done in the apartment complex and probably mess up the wiring, however a building tech/maintenance person can only fix it, advanced technician can't do anything about it.
What I'd like ask is what's the difference between a advance technician and a building technician? Also may I have a ticket created for this issue?
Thank you
@Progmistro an advanced technician working on resolving issues within the home. A maintenance/building technician will need to investigate where the source of the problem is throughout the entire building, once the problem is found, they will implement a fix.
Just to make sure, do you notice packet loss to all websites/servers or just the one above?
Your specific tracking maintenance referral is FLDISP0028612.
All packets are being lost, youtube, Netflix, whatsapp, google. I can provide lots more if you guys like.
Here's the issues im seeing below, keep in mind I cant watch, play or access properly these streaming/websites
Google:
Ping statistics for 216.58.217.46:
Packets: Sent = 40, Received = 23, Lost = 17 (42% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 39ms, Average = 32ms
Google 8.8.8.8:
Ping statistics for 8.8.8.8:
Packets: Sent = 40, Received = 23, Lost = 17 (42% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 36ms, Average = 31ms
Youtube:
Ping statistics for 172.217.14.206:
Packets: Sent = 40, Received = 28, Lost = 12 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 40ms, Average = 31ms
Amazon.com:
Ping statistics for 176.32.103.205:
Packets: Sent = 40, Received = 32, Lost = 8 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 90ms, Average = 78ms
Whatsapp:
Ping statistics for 108.168.254.65:
Packets: Sent = 40, Received = 32, Lost = 8 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 477ms, Average = 101ms
Twitter:
Ping statistics for 104.244.42.65:
Packets: Sent = 40, Received = 27, Lost = 13 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 52ms, Average = 48ms
> All packets are being lost, youtube, Netflix, whatsapp, google.
Between your computer and the target computer are many "routers". Compare to having many traffic-lights at the intersections on the streets between your home and your work-place.
Between one router and the next router, packets can be lost.
Also, "inside" the router, packets can be lost.
So, a better question is "where are the packets being lost?" You can answer this question by using the "tracert" command instead of the "ping" command. Try it, and post the results here.
Finally, note that "busy" routers may intentionally drop "ping" packets, in order to give a higher priority to "real" traffic going through the router.
I'd have to ask around but maybe the building management knows something
Heres what im seeing, looks like the IP address 68.147.32.1 is timing out, what IP address is that?
Tracing route to amazom.ca [72.52.10.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 * * * Request timed out.
3 * * 8 ms rc3no-be135-1.cg.shawcable.net [64.59.132.165]
4 27 ms * * rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 44 ms * 51 ms rc4sj-be60.cl.shawcable.net [66.163.78.74]
6 * 50 ms 46 ms rc3sj-be10.cl.shawcable.net [66.163.67.81]
7 47 ms 46 ms * akamai.prolexic.com [206.223.116.136]
8 47 ms 46 ms * po110.bs-b.sech-sjc.netarch.akamai.com [209.200.184.200]
9 * * 46 ms a72-52-1-191.deploy.static.akamaitechnologies.com [72.52.1.191]
10 47 ms 50 ms 47 ms ae121.access-a.sech-sjc.netarch.akamai.com [209.200.184.205]
11 46 ms 46 ms 46 ms a72-52-10-14.deploy.static.akamaitechnologies.com [72.52.10.14]
Tracing route to google.ca [172.217.14.195]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.0.0.1
2 * 9 ms 8 ms 68.147.32.1
3 12 ms 9 ms 9 ms rc3no-be135-1.cg.shawcable.net [64.59.132.165]
4 * 24 ms 25 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 27 ms 27 ms 26 ms 72.14.242.90
6 * * * Request timed out.
7 32 ms * 32 ms 209.85.254.246
8 * 31 ms 28 ms 209.85.254.171
9 30 ms 26 ms 27 ms sea30s01-in-f3.1e100.net [172.217.14.195]
Tracing route to twitter.com [104.244.42.129]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.0.0.1
2 * * * Request timed out.
3 * 140 ms 169 ms rc3no-be135-1.cg.shawcable.net [64.59.132.165]
4 32 ms 28 ms * rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 29 ms 30 ms * rc1wt-be18-1.wa.shawcable.net [66.163.64.81]
6 * 33 ms 30 ms six.sea2.twttr.com [206.81.81.31]
7 * * * Request timed out.
8 53 ms 51 ms 48 ms 104.244.42.129
Trace complete.
Tracing route to google.com [172.217.14.238]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 10.0.0.1
2 * 2013 ms * 68.147.32.1
3 15 ms 11 ms * rc3no-be135-1.cg.shawcable.net [64.59.132.165]
4 27 ms * 28 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 * 32 ms 29 ms 72.14.242.90
6 * * * Request timed out.
7 33 ms * 35 ms sea30s02-in-f14.1e100.net [172.217.14.238]
Trace complete.
> looks like the IP address 68.147.32.1 is timing out, what IP address is that?
Not all routers are configured to respond to "PING" packets. Apparently, this router is so configured.
All IP-addresses from 68.144.0.0 through 68.151.255.255 have been allocated to Shaw Communications. So, it's just a router that is "local" to you, in Calgary.
A few "nearby" IP-addresses are: 68.147.32.2 (S0106f8a097f01802.cg.shawcable.net) and 68.147.32.3 (S0106087e641ad3af.cg.shawcable.net)
> Tracing route to amazom.ca [72.52.10.14]
Did you mean "amazon.ca" [54.239.19.238 or 54.239.18.172 or 52.94.225.242] ?
Fortunately, that "M" domain was registered by the "real" Amazon/Canada, not by somebody maliciously trying to "spoof" Amazon. That "M" web-site just redirects you to their real web-site.
Anyway, because TraceRoute shows those "stars" at the routers that are closest to you, you also will see "stars" at the routers that are closest to your target web-site. To compare, if there is a flag-person temporarily obstructing your automobile from leaving the street where your home is, you will have temporary delays, no matter what your destination is.
Contact Shaw Support, to get them to trouble-shoot your unacceptable packet-loss -- there is nobody on this forum who can remotely access your cable-modem, to run diagnostics on it.
@Progmistro thanks for confirming. As per my post above, there is an associated tracking referral for your building/area for our maintenance technician to investigate.