- HughesNet Community
- :
- About lighthope1
HughesNet Community
About lighthope1
Senior
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
238
Posts
36
Kudos
1
Solution
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
10-03-2021
03:38 AM
|
03-14-2020
10:49 PM
1 Kudo
@lm8542 wrote: Yeah, neat tool it came out 502.38 when I entered the beam etc. But when it was last working like thas was early last year, spring 2019. The photo's I posted I can't even get to load but if anyone can see them they show the latency I get 628ms immediatly going up continuously like within 5 seconds 2100, 3500, 6800,12000, 16000 I don't remember it getting above 16000 ms but the photo I uploaded today was 14368ms. I don't think anyone else on Hughes.net is getting that kind of latency. Usually when it tops off at say 12000-16000ms it goes down to like 4000-8000ms. Those numbers don't allow for anything other than logging in and logging out. I am surprised I can even log in. I've gotten 44,000 latency. It's better in the morning/afternoon. Evenings will kill you.
... View more
03-13-2020
08:52 PM
Oh, btw, because of CenturyLink's position in the chain, this is going to affect everything. So you can't bounce to...say...Final Fantasy XIV or Guild Wars 2. You'll get the same problem. You can always ask to switch satellites. That could help. Problem is, the satellite that will likely solve your latency problem will drag you down with speed problems. Pick your poison.
... View more
03-13-2020
08:49 PM
@lm8542 wrote: Thanks for posting. wikipedia says Level 3 communications officially merged with centurylink in November 2017. Most updated info I could find. Yeah, they are a serious problem child for World of Warcraft players. You'll see huge hangtimes from them. If you go to the technical support forums and search for centurylink, you'll see a tsunami of complaints about them. Centurylink will tell you go pound sand. They don't care. HughesNet can complain, since they are the the next link in the chain. They are aware of the problem, but don't know if they have done anything about it. They can reroute around them, but as I said, it's a massive undertaking according to the high-level I talked to. So don't look for that to happen either. Honestly, there's not much that can be done by you other than to eat it and continue to play, accepting the impossible latency spike, or stop playing and save the money. Wish I had better news. Maybe CenturyLink will eventually fix it.
... View more
03-13-2020
06:05 PM
The LEOs will kill HughesNet (and Viasat). From what I understand, they plan to offer higher data plans, higher speeds, and far FAR less ping times than Hughes do. Don't know about price, though. Haven't heard a peep on that.
... View more
03-13-2020
06:02 PM
1 Kudo
Correction: It may be CenturyLink, not Qwest. Whoever owns L3.
... View more
03-13-2020
02:19 PM
@lm8542 wrote: The top part of my post was omitted somehow without me being aware of it. Needless to say I have been using Hughesnet since 2011 and have been playing wow (world of warcraft) with the expected latency on both gen 4 and gen 5 after upgrade. The latency was playable and between 400ms-1200ms depending on the time of day. But last year I had to suspend playing this game because I thought it was the game as they released a new update. However, after contacting blizzard tech support and giving them my winMTR results I was told by the tech that it was a hughesnet problem and my first post is part of his reply to my request for help. Level3 is a known problem. It's a serious bottleneck. Basically, anything owned by Qwest has been having trouble with WoW players. Lucky for me, almost everything goes through a Quest server on my route, so I experience monsterous latency. So WoW playing is nearly impossible. The only solution is for HughesNet to route around the problem servers, though after talking with a very high up person, that is a major undertaking. Qwest won't help unless you are their customer. Could you post your original post in full? (You said some of it was cut off) That might help.
... View more
03-05-2020
01:40 PM
Switched to a new satellite and all my data token bytes are gone. Had 20 gb. Now zero
... View more
Labels:
- Labels:
-
Support Center
01-31-2020
10:42 PM
Has HughesNet been giving some extra data in the data token slot? My data token went up from 14g to 21g and I never used a token. Not complaining! Just was curious if HughesNet was giving out a little gift. Good timing. I had to blow a lot of data downloading a 43 g package yesterday.
... View more
Labels:
- Labels:
-
Plans
12-20-2019
04:02 PM
1 Kudo
@RandyPAlex wrote: My speeds seem to be quite good but the latency is CRAZY bad. I'm having the same problem you are. So let me tell you how it all shook out. You're going to have a near impossible time getting HughesNet to admit there is a problem. Talk to their first level tech support and they will follow the script and eventually turn you over to engineering. That is, even if you can get past them. Their first line of defense will be that the latency you are experiencing is normal. (Yes, they will really tell you that!) Next is advanced support. Some will try to help, but ultimately they will fall back on to that "everything is normal" line. You're not going to get anywhere with them. Laghingly, one mod on this forum even told me to go find another ISP if I didn't like it. (He was reported) I had to climb very high up the ladder to get a real response. But I did get a response. They are starting (just starting, mind you!) to look into an issue of a data clog by the infamous CenturyLink. Other than that, they can try realigning your dish or switching you to a different satellite. Beyond that, you're kind of stuck. That was my choice. They sent a tech out to realign the dish. (They are still working on that. The tech brought the wrong equipment so he has to come back.) Or they can switch me to a different, overloaded satellite. So if the realignment doesn't work out, my choice is high latency or slow speeds. Another possibility is bad gateway management or bad traffic shaping, but based on the data, it really looks like a data clog just outside the gateway. As of this moment, HughesNet is not acknowledging that. But I did get them to look at it. At least, that was what the higher-up told me. He seemed honest, so I will give him the benefit of the doubt. Wish I had better news. But there it is.
... View more
12-15-2019
03:42 PM
@MarkJFine wrote: Hey... if someone can do something with this, have at it (and you'll also have a friend for life): This is going to take HughesNet rerouting traffic around the bad servers. CenturyLink certainly has no incentive to fix the problem as long as their own customers aren't complaining. (And I hear they are complaining) When I was running traceroutes, I would always see a timeout from a CenturyLink server. Either a quest or Level13 like you have in your image. If rerouting is to take place, HughesNet says this is a major, major issue, so it is going to take a lot of feedback to convince them to do this. So anyone who is being affected by this really should be speaking up and providing the data. They ARE looking into this. At least, that is what they told me. Well, the higher-up told me. And as you, completely random but extremely often, like every second.
... View more
12-13-2019
02:34 PM
I sent my report to HughesNet regarding the huge latency spikes (and, as I said, I named names, both those employees who were helpful as well as those who were not helpful). (As an aside, they did find a problem, which they are going to work on.) During our recent phone conversation, they were interested in this data clog by CenturyLink. I referred them to the forum here where it is talked about, and HughesNet said they were going to send someone to research it. I thought it would be good to have a new thread where people can list the observations/experiences so maybe HughesNet could located and identify the specific problem with CenturyLink. HughesNet said if there is indeed a data clog by CenturyLink, it would be a major fix. So any data we can give them I think would be very helpful.
... View more
Labels:
- Labels:
-
Performance
12-11-2019
09:19 PM
1 Kudo
I've had HughesNet since 2003 I think. I remember when a single raindrop would knock out your interent for days. I have to admit, today it takes a significant amount of snow to stop the signal from getting through. On that note at least, HughesNet has done a massive improvement from 16 years ago.
... View more
12-01-2019
07:38 PM
@Cblucas3 wrote: You say testmy.net is not accurate. I believe it to be "real world". Testmy is extremely accurate, no matter how much the white knights here want to protect HughesNet. I've found it to be very reflective of the latency issues that I am having as well, and apparently you are having as well. I can't even get Facebook pages to load today without timing out. Good luck getting HughesNet to acknowledge a problem. As you can see, they locked my thread where I was reporting it. My guess is actually a data clog by CenturyLink. You may be able to see this yourself by running a traceroute. But then, that is just a guess. HughesNet would actually know, but they aren't talking. Other possibilities are oversaturation (overselling) of a beam, but I don't think so. Bad traffic management or data shaping is also something to be considered. These options would be the best possibilites, because HughesNet could actually do somethng about it. If it really is CenturyLink, it becomes harder as HughesNet may or many not have options available. If they can route their data around CenturyLink, then the problem is fixable. If CenturyLink is their connection to terrestrial internet, they we are all in a hole. Good luck. Hope it all works out for you.
... View more
11-26-2019
10:49 PM
20 second latency spikes tonight.
... View more
11-25-2019
06:09 PM
You already said you were going to stay out of this thread, @MarkJFine. Please stick with your resolve. You are not a helpful person. To address what you said so others are not confused with your deflection: HughesNet says there is no problem. HughesNet says that these high latency spikes are normal. HughesNet says if we don't like it, we can go find another ISP. We are only speculating that CenturyLink is the problem. The fact is, we don't know because HughesNet won't comment on the issue or even acknowledge it. It would be absolutely fantastic if HughesNet jumped in and said: Thank you for your feedback and the data you and others have provided. Out engineers have looked at the problem and we have found that the latency is coming from our connection to CenturyLink, which is our direct connection from the gateway you use to the main internet. We are currently working with CenturyLink to resolve this problem and we will give you regular updates on its status and when it will be resolved. Until then, please continue to report to us latency spikes and anthing you are doing that may help us find a pattern. Thank you for your contiued patience in this matter. To be honest, though, at this point it would be difficult to beleive even that statement now, as it would be read as them just telling us what we want to hear. It is something they should have come forward and said right at the beginning. As maratsade said, it is good for the rest of us to share our experiences so we can help isolate this issue, find out what is causing it so maybe a solution can be found, and also so others can see how HughesNet works (or not works) with its customers. @MarkJFine wrote: @lighthope1 wrote: You must be referring to HughesNet since they don't see a problem. No... You. The absolute last thing I'm going to say on the matter: If Facebook is having a problem, should HughesNet assume responsibility and acknowledge that as well? Because that's precisely the same thing as what you're insinuating. The problem is so much larger than HughesNet that you're having a problem comprehending that. Bottom line: Your internet works from you to HughesNet, to CenturyLink, to whomever, to Facebook, and back. HughesNet's responsibility to you is just that, between them and you. Anything beyond that is OUT OF THEIR CONTROL.
... View more
11-25-2019
04:42 PM
@MarkJFine wrote: I know... was just reinforcing my earlier comment that others don't want to accept. You must be referring to HughesNet since they don't see a problem.
... View more
11-25-2019
04:42 PM
@maratsade wrote: It wasn't me asking the question, @MarkJFine . I was quoting Lighthope. 🙂 Edit: but it does appear that CL is right messed up. If I had to bet money, I'd say it was CenturyLink that was the actual problem. The issue we have here is that HughesNet won't even acknowledge there is a problem, and then spout off brain-dead statements like "That is how satellite tech works" and "You can go find another ISP."
... View more
11-25-2019
04:39 PM
@maratsade wrote: Thank you, Lighthope. Earlier on in the thread, you had posted that "I also tried the command prompt ping test. That comes out at 600ms fairly consistently. So now we have to ask the question: Why does a ping test come with low ping, but streaming data have such problems." Are there specific pages (like the ones you had linked to upthread) that have issues loading, or does everything load slowly or fail to load? ETA: you don't have to respond if you don't want to. I'm just curious, as a subscriber, about the experiences of fellow subscribers. Various pages load slow. It is inconsistent. Facebook, however, is one of the worst, likely because it hooks into so many other things.
... View more
11-24-2019
08:49 PM
@GabeU wrote: @maratsade wrote: Has HughesNet made any offers to you? (discounts, for example) From the look of it.... https://community.hughesnet.com/t5/Tech-Support/HughesNet-Tier-4-support-refused-to-help-with-unusual-high/m-p/116071/highlight/true#M78333 "I see that our representatives have already applied a monthly discount to your account, as a form of compensation. Currently, this is the extent of what can be done." In the very next post, I stated that the discount applied was for "the months of detrmental speeds (400K mbps was the lowest recorded speed), and had nothing to do with the high latency that is being experienced now". So no, I have received no compensation for the high latency spikes.
... View more
11-24-2019
08:47 PM
No they have not. Not for this issue anyway. @maratsade wrote: Has HughesNet made any offers to you? (discounts, for example) @lighthope1 wrote: I have several tools to measure latency. Some are in-programme, some are from testmy.net, some from other stand-alone mesurement tools. The report goes to HughesNet corporate and will also be published publicly. I have kept a written log of every interaction I have had regarding this issue including the names of people. I will be naming names, both of those who have been helpful and those who have not been. HughesNet can decide if this has been acceptable customer service or not. And, of course, others can as well.
... View more
11-24-2019
06:49 PM
1 Kudo
The point is that bad service should not just be "accepted". We shouldn't learn to live with things that can be addressed but aren't because they know they are a monopoly, because someone is bad at their job, or if someone outright lies about something so as to not take responsibility. I'm not talking about people who don't understand satellite. I see a lot of posts from people who burn through their data either from downloading huge movies or because they have devices that suck up data. I'm not talking about people who don't understand latency and the fact that the satellite is 20K+ miles out there and it takes time for a signal to travel. What I am talking about is bad data management, bad trafficing, and other issues that are real and either are in the pervue of HughesNet or shoud at least be acknowledged. I posted very recently about the trouble CenturyLink is giving HughesNet. Even others have posted about it. But as we have seen, HughesNet won't even acknowledge that. Talk about head-in-the-sand! When HughesNet or anyone has a problem, ignoring it doesn't make it go away. And accepting it doesn't make it better. We should never become someone who accepts poor service. That just encourages more poor service.
... View more
11-24-2019
06:35 PM
@GabeU wrote: @lighthope1 If you're still subject to the two year agreement, have they offered to allow you to cancel without penalty? I am not subject to it; I've long past it. Sadly, there is no other internet service in the area. I can't hit Viasat's satellite because of trees and there is no cell service in the area. Belive me, if there was any other option, HughesNet would be far in my rearview mirror.
... View more
11-24-2019
06:33 PM
@maratsade wrote: Where are you getting your latency measurements? And where do you plan to file your written report? I have several tools to measure latency. Some are in-programme, some are from testmy.net, some from other stand-alone mesurement tools. The report goes to HughesNet corporate and will also be published publicly. I have kept a written log of every interaction I have had regarding this issue including the names of people. I will be naming names, both of those who have been helpful and those who have not been. HughesNet can decide if this has been acceptable customer service or not. And, of course, others can as well.
... View more
11-24-2019
03:27 PM
Still no contact from HughesNet. No data suggesting that there is any follow-through or investigation into extremely high latency spikes. Still getting 10K+ latency spikes. Facebook won't load. (Though Facebook has its own issues. It's so full of bloat and spyware, likely it is timing out due to this latency problem.) I'll give this some extra time before I file my written report to see if they actually do anything. Giving every chance possible.
... View more
11-17-2019
05:45 PM
@GabeU wrote: @lighthope1 I think the problem you're going to have is that you're dismissive of anything anyone tells you, even when factual, if it doesn't fit the narrative you've invested in, which is that the problem is HughesNet's and that need to fix it. The issue is out of their control. Good luck to you. What issue? HughesNet says there is no issue. That it's normal and to be expected. Good luck to these HughesNet employees if their manager ever sees how they addressed this problem.
... View more
11-17-2019
04:56 PM
1 Kudo
@MarkJFine wrote: I'm not going to argue with you. You go right ahead and continue directing your anger to everyone not responsible for your problem. I'm out. If you're not going to be helpful, there's no reason for you to reply.
... View more
11-17-2019
04:16 PM
@MarkJFine wrote: You may be angry, but your anger is misplaced. Why are you getting angry with HughesNet and their representatives, when they only have visibility into what they're responsible for? They're not responsible for CenturyLink's wonky backbone any more than you are. To quote my own post: The problem is getting HughesNet to even admit something is wrong. But this outright lie by some HughesNet employees. To have a problem. To show evidence of a problem. And to have HughesNet blow you off. That is where the anger comes from. You: Doctor, I need help. My arm is severed off. Doctor: No it isn't. You: Yes it is. You can see it's severed off. Doctor: No I can't. You: I'm holding my severed arm in my other hand. Doctor: What you are experiencing are typical side effects due to the current state of arms, just a bit more severe.
... View more
11-17-2019
03:27 PM
@MarkJFine wrote: Qwest is your gateway's internet provider. CenturyLink now owns all of Qwest, just like they own all of Level3. If you didn't think CentryLink was the problem, now you should. Based on some other posts, that was actually my guess. Qwest/CenturyLink is the source of the data clog. The problem is getting HughesNet to even admit something is wrong. For example, take a look at this complete ignorant reply by @Damian. What you are experiencing are typical side effects due to the current state of satellite internet technology, just a bit more severe. Seriously? Seriously?! And to make it worse, that is the same by-the-book answer I got from another HughesNet employee, indicating that they are trained to disavow any problem rather than address it. You know, I would have been accepting of an answer that went, "We know there is a problem. It seems Qwest is throttling our gateway connection to the internet. We are working on a solution either with them or a work around them. Please be patient as we continue to address this issue you are having." I would naturally be frustrated that the problem is continuing, but at least I would know the problem is being acknowledged and worked on. But this outright lie by some HughesNet employees. No, I won't say lie. Perhaps they really are not good at thier job and don't understand how things work. Perhaps they need to be retained or reassigned. I will be generous and consider that possibility. But that is where the real frustration come from. To have a problem. To show evidence of a problem. And to have HughesNet blow you off. And to have one of them...Damian...say well just go find another isp. Wow, just wow. I will certainly be mentioning that in the letter to Corporate I'll be sending shortly once I compile some more data on how this issue is being addressed or (currently) not being addressed.
... View more
11-15-2019
11:01 PM
Here are some traceroutes. Interesting that it always times out around the qwest.net one. Tracing route to dmukx06zie5kn.cloudfront.net [2600:9000:2164:b200:1a:81cc:6dc0:93a1] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:5b0:4fd1:9ad8:280:aeff:fe72:b44 2 622 ms 618 ms 628 ms 2001:5b0:4f00:1101::1 3 619 ms 656 ms 640 ms 2001:5b0:4f00:fffa::105 4 611 ms 628 ms 625 ms 2001:5b0:4f00:fffa::104 5 622 ms 618 ms 628 ms 2001:428:6402:10:0:36:0:1 6 656 ms 608 ms 652 ms 2001:428:6402:10:0:e:0:2 7 * * * Request timed out. 8 * * * Request timed out. 9 609 ms 634 ms 623 ms 2600:9000:fff:ff00::300 10 638 ms 668 ms 645 ms 2600:9000:fff:ff01:0:50:102:41 11 609 ms 641 ms 638 ms 2600:9000:fff:ff00::401 12 * * * Request timed out. 13 * * * Request timed out. 14 649 ms 620 ms 581 ms 2600:9000:2164:b200:1a:81cc:6dc0:93a1 Trace complete. Tracing route to tvbythenumbers.zap2it.com [192.0.79.32] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.42.1 2 613 ms 612 ms 648 ms host174330065208.direcway.com [174.33.208.65] 3 693 ms 608 ms 618 ms host17433005213.direcway.com [174.33.213.5] 4 614 ms 578 ms 636 ms host17433004213.direcway.com [174.33.213.4] 5 611 ms 614 ms 643 ms tuk-edge-14.inet.qwest.net [65.153.170.53] 6 637 ms 620 ms 637 ms sjp-brdr-06.inet.qwest.net [67.14.34.214] 7 * * * Request timed out. 8 646 ms 663 ms 628 ms Comcast-level3-60G.SanJose1.Level3.net [4.68.75.106] 9 643 ms 648 ms 608 ms 50.248.116.14 10 620 ms 598 ms 599 ms wordpress.com [192.0.79.32] Trace complete. Tracing route to miceage.com [50.63.202.25] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.42.1 2 644 ms 598 ms 629 ms host174330065208.direcway.com [174.33.208.65] 3 605 ms 638 ms 648 ms host17433005213.direcway.com [174.33.213.5] 4 633 ms 628 ms 577 ms host174330033213.direcway.com [174.33.213.33] 5 595 ms 638 ms 638 ms tuk-edge-14.inet.qwest.net [65.153.170.53] 6 634 ms 608 ms 628 ms sea-brdr-03.inet.qwest.net [67.14.41.154] 7 * * * Request timed out. 8 686 ms 659 ms 696 ms 4.69.216.158 9 628 ms 648 ms 656 ms 4.53.228.238 10 691 ms 658 ms 658 ms ae1.ibrsa0107-01.lax1.bb.godaddy.com [148.72.34.7] 11 * * * Request timed out. 12 678 ms 648 ms 678 ms 148.72.32.16 13 652 ms 638 ms 675 ms be38.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.69] 14 660 ms 668 ms 658 ms ip-184-168-0-102.ip.secureserver.net [184.168.0.102] 15 663 ms 698 ms 654 ms ip-50-63-202-25.ip.secureserver.net [50.63.202.25] Trace complete. Tracing route to youtube.com [2607:f8b0:400a:800::200e] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:5b0:4fd1:9ad8:280:aeff:fe72:b44 2 635 ms 628 ms 638 ms 2001:5b0:4f00:1101::1 3 624 ms 618 ms 598 ms 2001:5b0:4f00:fffa::105 4 * 617 ms * 2001:5b0:4f00:fffa::10a 5 674 ms 661 ms 608 ms 2001:428:6402:10:0:36:0:1 6 615 ms 608 ms 608 ms 2001:428::205:171:3:129 7 635 ms 608 ms 628 ms 2001:428:6402:10:0:2b:0:2 8 640 ms 658 ms 639 ms 2001:4860:0:1041::1 9 615 ms 628 ms 628 ms 2001:4860:0:1::1e6f 10 634 ms 648 ms 595 ms sea15s07-in-x0e.1e100.net [2607:f8b0:400a:800::200e] Trace complete. Tracing route to testmy.net [2606:4700:20::681a:573] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:5b0:4fd1:9ad8:280:aeff:fe72:b44 2 659 ms 618 ms 658 ms 2001:5b0:4f00:1101::1 3 610 ms 606 ms 636 ms 2001:5b0:4f00:fffa::105 4 622 ms * * 2001:5b0:4f00:fffa::10a 5 607 ms 638 ms 628 ms 2001:428:6402:10:0:36:0:1 6 607 ms 628 ms 648 ms 2001:428:0:1:205:171:0:58 7 865 ms 1028 ms 898 ms 2001:428:a01:a::2 8 644 ms 628 ms 638 ms 2001:1900:2100::457a 9 584 ms 630 ms 626 ms 2606:4700:20::681a:573 Trace complete. Tracing route to us.blizzard.com [137.221.106.102] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.42.1 2 643 ms 618 ms 608 ms host174330065208.direcway.com [174.33.208.65] 3 649 ms 643 ms 618 ms host17433005213.direcway.com [174.33.213.5] 4 634 ms 628 ms 638 ms host174330033213.direcway.com [174.33.213.33] 5 614 ms 628 ms 658 ms tuk-edge-14.inet.qwest.net [65.153.170.53] 6 634 ms 609 ms 648 ms sea-brdr-03.inet.qwest.net [67.14.41.154] 7 * * * Request timed out. 8 * * * Request timed out. 9 676 ms 668 ms 628 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.net [4.71.135.106] 10 683 ms 674 ms 683 ms ae1-br01-eqla1.as57976.net [137.221.68.33] 11 637 ms 700 ms 668 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69] 12 622 ms 656 ms 627 ms et-0-0-31-pe01-swlv10.as57976.net [137.221.83.67] 13 641 ms 677 ms 669 ms las-swlv10-ia-bons-02.as57976.net [137.221.66.19] 14 671 ms 661 ms 664 ms 137.221.105.17 15 677 ms 678 ms 658 ms 137.221.106.102 Trace complete. Tracing route to google.com [2607:f8b0:400a:803::200e] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2001:5b0:4fd1:9ad8:280:aeff:fe72:b44 2 596 ms 658 ms 628 ms 2001:5b0:4f00:1101::1 3 624 ms 628 ms 618 ms 2001:5b0:4f00:fffa::105 4 646 ms * * 2001:5b0:4f00:fffa::104 5 638 ms 595 ms 621 ms 2001:428:6402:10:0:36:0:1 6 637 ms 618 ms 632 ms 2001:428::205:171:3:129 7 640 ms 639 ms 618 ms 2001:428:6402:10:0:2b:0:2 8 624 ms 648 ms 598 ms 2001:4860:0:4::1 9 620 ms * * 2001:4860:0:1::255b 10 619 ms 637 ms 610 ms sea30s02-in-x0e.1e100.net [2607:f8b0:400a:803::200e] Trace complete.
... View more
Latest Tags
No tags yet
- HughesNet Community
- :
- About lighthope1