Standard Horizon web site down?

[transmitterdan]

For several days (possibly longer) the web site Welcome to StandardHorizon.com will not come up for me. Although, Welcome to StandardHorizon.co.uk will come up. Also, Welcome to Yaesu.com won't come up either. Can someone outside the US verify if either web site works?

[Target9000]

The normal site comes up for me.

[Richard_W]

All three sites worked for me.

[transmitterdan]

Thanks, it appears to be a bad router configuration somewhere within my ISP (verizon).

[transmitterdan]

After a bunch of time on the phone with Verizon tech support they think that some big ISP in the cloud has determined that Welcome to StandardHorizon.com and Welcome to Yaesu.com (same IP address) is a "dangerous" web server and so it is on a black list. They say that only the web site administrator can get the web site off the black list. I don't know if that's true or not but it seems to be so. I can reach the web site from my iPhone but not from my computer on the Verizon network. If anyone happens to know someone at Standard Horizon or Yaesu please tell them their web site may have been black listed by persons unknown. There could be many other people that can't access their site.

[marlinmike]

just email them from your iPhone!

[transmitterdan]

I did but probably they'll think it's some crackpot. Wouldn't be the first time..👍

[irwin37]

Hate to say it but it could be your computer, the ip may be being redirected. You may have picked up some malware or bad code from a site you visited. I had this happen and the only way I was able to get it to work was to uninstall Firefox and reinstall it. The only other way this might be happening is if a static DNS server ip was put on your machine or the DNS server you use (Your ISP) is having problems.

[transmitterdan]

Originally Posted by irwin37

Hate to say it but it could be your computer, the ip may be being redirected.

It's somewhere in Verizon I think as even their local NOC engineer cannot reach that IP address. The DNS is working correctly. One of the routers in or very near the cloud has a route table entry that directs all packets destined for that site into a black hole at AT&T. It's easy to see where it goes wrong from a trace route. Verizon claims it's not one of their routers but I am suspicious about that. I suspect it is one of theirs else it would be affecting more people. And i suspect the poor Yaesu web site admin will have a hard time getting their site off the router's black list if they even know about the problem.

I was not surprised when Verizon said it's not their problem.

[StandardHorizon]

transmitterdan,

I have forwarded your post to our IT department. Thank you for letting us know that you are experiencing issues viewing our website using Verizon (ISP).
Best regards,
R. Jason Kennedy
Executive Vice President
Standard Horizon / YAESU Aviation
6125 Phyllis Dr. Cypress, CA 90630
714.827.7600 (office)

[StandardHorizon]

Transmitterdan,

Our IT department was not able to duplicate the issue that you reported, also they have performed a search of blacklisted websites and standardhorizon.com and Yaesu.com are not listed.

Best regards,
Jason Kenendy

[DeepFrz]

I was always able to get to the site without a problem. I think it must be your computer.

[transmitterdan]

The Verizon NOC could not reach it either. Don't know how that could be due to my computer.

[transmitterdan]

Originally Posted by StandardHorizon

Transmitterdan,

Our IT department was not able to duplicate the issue that you reported, also they have performed a search of blacklisted websites and standardhorizon.com and Yaesu.com are not listed.

Best regards,
Jason Kenendy

Jason,

Thanks for looking into this. I will give you this to show to your IT department. I get the same thing on my laptop and my iPhone so it's not my computer. Verizon insists that only the web site owner can fix this although I don't believe them.

C:\Users\Dan>tracert www.standardhorizon.com
Tracing route to www.standardhorizon.com [71.139.254.252]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.1.1
2 11 ms 6 ms 9 ms L100.DLLSTX-VFTTP-66.verizon-gni.net [96.226.243.1]
3 9 ms 12 ms 12 ms G0-9-2-7.DLLSTX-LCR-22.verizon-gni.net [130.81.182.158]
4 12 ms 9 ms 13 ms ae4-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.66]
5 11 ms 12 ms 11 ms 0.xe-3-0-3.BR1.DFW13.ALTER.NET [152.63.98.245]
6 13 ms 12 ms 12 ms 192.205.37.125
7 47 ms 107 ms 51 ms cr2.dlstx.ip.att.net [12.122.212.14]
8 57 ms 49 ms 107 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 117 ms 47 ms 47 ms gar7.an1ca.ip.att.net [12.122.104.65]
10 * * * Request timed out.
11 * * * Request timed out.
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 * * * Request timed out.
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.
C:\Users\Dan>tracert www.google.com
Tracing route to www.google.com [173.194.77.147]
over a maximum of 30 hops:
1 1 ms <1 ms 4 ms 192.168.1.1
2 7 ms 7 ms 12 ms L100.DLLSTX-VFTTP-66.verizon-gni.net [96.226.243.1]
3 11 ms 12 ms 14 ms G0-9-4-0.DLLSTX-LCR-21.verizon-gni.net [130.81.194.192]
4 58 ms 10 ms 9 ms so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
5 79 ms 12 ms 13 ms 0.ae3.XL3.DFW7.ALTER.NET [152.63.3.229]
6 12 ms 13 ms 16 ms TenGigE0-6-4-0.GW4.DFW13.ALTER.NET [152.63.101.21]
7 108 ms 73 ms 119 ms google-gw.customer.alter.net [152.179.51.26]
8 * * * Request timed out.
9 14 ms 13 ms 14 ms 72.14.237.217
10 20 ms 21 ms 20 ms 216.239.47.121
11 20 ms 16 ms 18 ms 216.239.46.59
12 * * * Request timed out.
13 18 ms 18 ms 17 ms ob-in-f147.1e100.net [173.194.77.147]
Trace complete.
C:\Users\Dan>

This is about all I can do to show the problem is not in my computer.

Thanks,
Dan