cancel
Showing results for 
Search instead for 
Did you mean: 

The all to familiar problem, slow - slow - slow

Junior

Re: The all to familiar problem, slow - slow - slow

Regarding the slow throughput (not bps speed), do these tracerouts shed any light?  Seems like a lot of time-outs.

Tracing route to hughesnet.com [34.197.164.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.42.1
2 612 ms 604 ms 579 ms host1743300193203.direcway.com [174.33.203.193]
3 607 ms 549 ms 592 ms host17433005205.direcway.com [174.33.205.5]
4 652 ms 648 ms 650 ms host17433004205.direcway.com [174.33.205.4]
5 619 ms 639 ms 619 ms 4.14.190.73
6 * * * Request timed out.
7 635 ms 670 ms 619 ms 4.15.44.98
8 685 ms 662 ms 699 ms 176.32.125.220
9 700 ms 655 ms 702 ms 176.32.125.231
10 * * * Request timed out.
11 680 ms 659 ms 739 ms 52.93.129.237
12 658 ms 655 ms 725 ms 54.240.229.187
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 684 ms 655 ms 705 ms 52.93.28.162
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 689 ms 719 ms 654 ms ec2-34-197-164-140.compute-1.amazonaws.com [34.197.164.140]

Trace complete.

----

Tracing route to qrz.com [23.23.229.197]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.42.1
2 617 ms 609 ms 589 ms host1743300193203.direcway.com [174.33.203.193]
3 578 ms 589 ms 609 ms host17433005205.direcway.com [174.33.205.5]
4 626 ms 607 ms 562 ms host17433004205.direcway.com [174.33.205.4]
5 621 ms 579 ms 665 ms 4.14.190.73
6 * * * Request timed out.
7 631 ms 648 ms 669 ms 4.16.116.254
8 668 ms 712 ms 705 ms 54.239.104.64
9 704 ms 679 ms 679 ms 54.239.104.75
10 * * * Request timed out.
11 646 ms 679 ms 709 ms 54.239.43.174
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 742 ms 729 ms 719 ms 52.93.28.196
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

------------

Thanks,  Woody

 

 

Junior

Re: The all to familiar problem, slow - slow - slow

Here are some ping results:


Pinging hughsnet.com [46.166.182.64] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 46.166.182.64: bytes=32 time=753ms TTL=57
Reply from 46.166.182.64: bytes=32 time=756ms TTL=57

Ping statistics for 46.166.182.64:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 753ms, Maximum = 756ms, Average = 754ms

-------------

Pinging qrz.com [23.23.229.197] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 23.23.229.197:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

Distinguished Professor IV

Re: The all to familiar problem, slow - slow - slow

@hamradio 

 

My traceroutes to qrz and HughesNet look very similar, as does the ping to qrz (100% failure).  My Hughes ping is fine, though.  

 

I went to qrz.com, and after five minutes of it trying to load and still only having a blank screen, I closed it and tried again, at which point it opened and finished loading in 18 seconds.  I'll try it again in a couple of hours to see what happens.


AMD FX-6100 | Samsung 250GB 840 EVO SSD | Western Digital Blue 500GB HDD | 16GB DDR3-1866 | EVGA Geforce GTX 550ti | Windows 10 Pro 64-bit
Assistant Professor

Re: The all to familiar problem, slow - slow - slow

Think you're seeing the poor handoff between your gateway provider, CenturyLink (4.14.190.73) through a bunch of Amazon servers. For example, why they're routing you via Amazon Ireland (176.32.125.220 and 176.32.125.231) to get to the HughesNet site is anyone's guess.

 

If I recall, we might be on the same gateway. For what it's worth, I get similar results.


* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.
Junior

Re: The all to familiar problem, slow - slow - slow

Thanks for the reply.   The time outs appear to occur after directway.  Sounds like a HN problem in its routing...

I don't think there is anything I can do about routing issues.  No?, Yes? 

If no, then HN needs to "step-up" and fix the problem.

 

Woody - KZ4AK

 

Highlighted
Assistant Professor

Re: The all to familiar problem, slow - slow - slow

HN likely has a direct link to their provider. It's CenturyLink that does the routing, not HN.


* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.
Junior

Re: The all to familiar problem, slow - slow - slow


I have had similar experiences.  Sometimes a "forever wait", sometimes an incomplete load from sites.   Then, a fresh try sometimes works.   
@GabeU wrote:

@hamradio 

 

My traceroutes to qrz and HughesNet look very similar, as does the ping to qrz (100% failure).  My Hughes ping is fine, though.  

 

I went to qrz.com, and after five minutes of it trying to load and still only having a blank screen, I closed it and tried again, at which point it opened and finished loading in 18 seconds.  I'll try it again in a couple of hours to see what happens.


 

Junior

Re: The all to familiar problem, slow - slow - slow


Well Mark, that is interesting.  Too bad it is not something as a user of HN that I cannot do anything about that.   Sure do wish HN would address the problem.
Woody
@MarkJFine wrote:

HN likely has a direct link to their provider. It's CenturyLink that does the routing, not HN.


 

Assistant Professor

Re: The all to familiar problem, slow - slow - slow

CenturyLink has to admit *they* have a problem first, and they haven't in over a year.


* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.
Professor

Re: The all to familiar problem, slow - slow - slow

"It's not us; must be you" seems to be the go to answer from many providers of goods and services. 

 


@MarkJFine wrote:

CenturyLink has to admit *they* have a problem first, and they haven't in over a year.