Long latency when tethered
JoeFroggy
Newbie

There is an unacceptably long latency when I'm tethered.  It's so long, Goggle Earth times out completely.  So I cannot use Google Earth!

My web browser times out, too.  I have to close it, re-open it, and hit the site (any site) at least a few times before any response occurs.

This is really bad.

I just left AT&T and joined Verizon.  The AT&T network did not have this problem.  I used a Galaxy SIII on that network always with an LTE connection.  Tethering worked fine.

On the Verizon network, I use a new Galaxy S5.  Also with an LTE connection.  It just does not work properly, and in fact is not suitable for my work.

Is there any grace period for me to cancel this service and return to AT&T?

Labels (1)
0 Likes
Re: Long latency when tethered
Tidbits
Legend

14 days

0 Likes
Re: Long latency when tethered
JoeFroggy
Newbie

Thanks Tidbits.

Some interesting test results:

C:\>tracert googleearth.com

Tracing route to googleearth.com [173.194.115.81]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.42.129

  2    42 ms    40 ms    39 ms  5.sub-66-174-32.myvzw.com [66.174.32.5]

  3    40 ms    41 ms    39 ms  50.sub-69-83-173.myvzw.com [69.83.173.50]

  4    32 ms    41 ms    47 ms  177.sub-69-83-172.myvzw.com [69.83.172.177]

  5    33 ms    45 ms    39 ms  177.sub-69-83-173.myvzw.com [69.83.173.177]

  6    50 ms    42 ms    28 ms  194.sub-69-83-173.myvzw.com [69.83.173.194]

  7    43 ms    39 ms    40 ms  8.sub-69-83-162.myvzw.com [69.83.162.8]

  8    42 ms    20 ms    39 ms  73.sub-66-174-29.myvzw.com [66.174.29.73]

  9    33 ms    40 ms    39 ms  ae52.bar1.Phoenix1.Level3.net [4.28.80.33]

10     *       41 ms     *     ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.15]

11     *       56 ms    51 ms  ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.15]

12    40 ms    39 ms    40 ms  4.68.71.18

13    48 ms    60 ms    70 ms  209.85.248.185

14     *        *        *     Request timed out.

15     *        *        *     Request timed out.

16    80 ms     *       72 ms  72.14.237.220

17    90 ms    69 ms    79 ms  209.85.254.133

18    69 ms    59 ms    60 ms  dfw06s41-in-f17.1e100.net [173.194.115.81]

Trace complete.

It's consistently like this.

0 Likes