JulioF
join:2006-11-01
Leander, TX
|  SatMex 6 Is Down
According to HN tech support, SatMex 6 is now down and browsing is not possible.
I had phoned to report slow browsing on a different satellite (113W). They informed me that the sat I'm on is also experiencing issues.
And I have an open ticket regarding the same issues I experienced for over 5 weeks in December/January. Sending of emails fails with connection to the webserver being dropped, and unable to upload to websites due to FTP upload errors (connection is being dropped).
Last time this happened, they gave me all kind of song and dance routines for over 5 weeks. Problem was theirs, then problem was my transmitter. Tech with new transmitter arrived, and I explained what I had seen in the modem stats and how the disconnections had been acting.
He pointed me to 113W (away from SatMex 6) and everything worked fine until recently. I only experienced 5+ weeks of not being able to modify websites, and no ability to send emails.
If you're thinking of running a biz based on HN, as the chick in the commercial says... THINK AGAIN!
--
Hughesnet | small biz | .98 | 2 watt | 99 West | 1370 MHZ | Signal 81-85
WinXP SP2 | Intel 2.66 GHZ Core 2 Duo |
|
Aaul
@direcpc.com
| Did they happen to mention which others might be affected? I am on 99W and since Friday 8/29 any persistent connection activities have been failing (such as WOW, instant messenging, etc) and today I got home from work and it seems it's now affecting browsing as well. In fact, I've been trying to download Google's new Chrome browser (475kb file) and it keeps failing about 200kb into the download. A tracert to www.hughesnet.com still reveals data loss inside their network, and now today I'm seeing drops outside of Hughes as well:
Tracing route to www.hughesnet.com [208.236.67.84]
over a maximum of 30 hops:
1 * * * Request timed out.
2 1162 ms 1008 ms * dpc6682157194.direcpc.com [66.82.157.194]
3 * 887 ms 1156 ms dpc6682017213.direcpc.com [66.82.17.213]
4 * 1474 ms 1230 ms dpc6682016065.direcpc.com [66.82.16.65]
5 1418 ms * 842 ms dca-edge-18.inet.qwest.net [63.237.64.85]
6 * * * Request timed out.
7 * 1020 ms 801 ms dcp-brdr-02.inet.qwest.net [205.171.251.38]
8 * 1313 ms 975 ms 63.146.26.106
9 1172 ms * 833 ms 0.ge-5-1-0.XL3.IAD8.ALTER.NET [152.63.41.154]
10 2024 ms 966 ms 1007 ms 0.so-7-0-0.CL1.TCO1.ALTER.NET [152.63.39.226]
11 858 ms 942 ms * 193.ATM6-0.GW3.TCO1.ALTER.NET [152.63.36.217]
12 891 ms 795 ms 979 ms hughes3-gw.customer.alter.net [157.130.73.138]
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 * * ^C
Anyone else have any insight or spoken with Hughes since Friday and gotten anything other than "There's nothing wrong, you need to clear your cache." responses?
-James |
|
FreeBSD user
@direcpc.com | reply to JulioF
I'm on SATMEX 6 and have been up all day. I did see a signal strength drop around 75 to 59 just before 10:00 CDT. |
|
MatthewAlan
join:2007-09-01
united state | reply to JulioF
I thought 113W was SM6 0.o |
|
mdh
join:2006-12-28
Festus, MO | Yes, SatMex 6 is 113 West |
|
JulioF
join:2006-11-01
Leander, TX
| SatMex6 = 113W? Ok. Thanks. I used to be on one of the SatMex birds, before changing to 113W. Must have been SatMex 5.
And all seems to be fine, and actually functioning exceptionally well, today.
--
Hughesnet | small biz | .98 | 2 watt | 99 West | 1370 MHZ | Signal 81-85
WinXP SP2 | Intel 2.66 GHZ Core 2 Duo |
|
