High Latency and Packet loss

I have the Nokia gateway & the excessive ping latency is common to all three of the T-Mobile gateways. A gateway replacement is a waste of time, effort & money. The problem has been reported by users coast to coast pretty much. You can do an ICMP ping for ipv4 or ipv6 and the result is the same. I have used Apple & Linux clients testing & it is pretty poor. It is common to see 70-80% packet loss running pings. Sure ICMP will have low priority & can be ignored but this is a recent behavioral change.

--- 8.8.8.8 ping statistics ---

100 packets transmitted, 19 packets received, 81.0% packet loss

round-trip min/avg/max/stddev = 75.896/110.618/150.142/18.738 ms

from netstat info:

Input histogram:

                echo reply: 56

                destination unreachable: 6175

                time exceeded: 104

Regarding the speedtest.net operation:

When a speedtest.net "test" is conducted to the server with a Wireshark capture you can see it opens a TCP session to the target test server. The TCP session (in my test run) is setup between TCP ports 8080 & 52830 for the packet exchange between the local client and the destination server. The local client TCP source port changes depending upon the packets. There are also some UDP exchange from time to time between the test server and the test client.

82.83.133.40.in-addr.arpa name = charlotte02.speedtest.windstream.net. < Target Server

Just prior to the session setup the local client, my MacBook Pro, repeats sending echo requests at 82.83.133.40. Over the course of the text there are 22 of the ICMP packets but all fail.

Resultado: All fail to reach the server. (no response found) ← Reason

Curious behavior as the trace route hits 192.0.0.1; then there are 4 responses 

traceroute to 40.133.83.82 (40.133.83.82), 64 hops max, 52 byte packets

1  www.webgui.nokiawifi.com (192.168.12.1)  1.042 ms  0.393 ms  0.330 ms

2  192.0.0.1 (192.0.0.1)  0.533 ms  0.560 ms  0.454 ms

3  * 192.0.0.1 (192.0.0.1)  27.806 ms *

4  * 192.0.0.1 (192.0.0.1)  42.273 ms  30.483 ms

5  192.0.0.1 (192.0.0.1)  27.970 ms  36.486 ms  28.959 ms

6  * * *

7  * * *

8  * * *

9  * * *

10  * 10.164.165.59 (10.164.165.59)  495.730 ms *

Non-authoritative answer:

10.164.165.59.in-addr.arpa name = 59.165.164.10.man-static.vsnl.net.in.

So it appears the traffic goes out the gateway but even performing the trace route using port 8080 or 443 it has issues. I have no clear idea where 192.0.0.1 is for sure. 

Is anyone else seeing the trace route where 192.0.0.1 is the next hop after the gateway? 

(00:50:b6:88:1a:f8 is the MAC address associated with the 192.0.0.1 IPv4 address from the Wireshark packet cap)

I am still picking the packet capture apart as there are a variety of odd issues but the speed test is completed regardless of the issues with the exchange of packets.