Please provide more information on this – our helpdesk is getting calls about this. Are you saying just route 67.20.176.130 to a pingable IP? Frank From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Josh Luthman via Outages Sent: Tuesday, October 07, 2014 10:42 AM To: Paul Miller Cc: outages@outages.org Subject: Re: [outages] Belkin [heartbeat.belkin.com] Just because you can ping it does not mean it will work. I've confirmed with other users this is the case. I believe there is some sort of HTTP request that confirms the connection is working (like Windows, Android, etc). Another resolution is to just loopback 67.20.176.130 (seems to be this IP for everyone so far). Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Oct 7, 2014 at 11:17 AM, Paul Miller via Outages <outages@outages.org <mailto:outages@outages.org> > wrote: On one of my netblocks my subscribers can nolonger ping Belkin. I can ping heartbeat.belkin.com <http://heartbeat.belkin.com> from my webservers and from subscriber units on a different netblock. Apparently Belkin routers ping the home base every couple seconds to determine the correct color of the Internet light on the router (orange or blue *sigh*). Worse, when it can't ping the Belkin site the router seems to pack up and redirect my subscribers to their router configuration page. I found this pretty easy to work around. I simply DNATed the pings intended for heartbeat.belkin.com <http://heartbeat.belkin.com> to one of my local nameservers and that seems to get them back online. It's a silly workaround, but if anyone else is seeing all the Belkin routers on their network pack up, this could be why. -Paul _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages