Have you guys started blocking port 443 (https) inbound in the last couple of days?

Hrm. It's very odd, then.

I suspected something was up because I can see the other blocked ports on a quick scan (most ports show up as closed, but the ones Cox blocks generate no response at all to a connection attempt), whereas what I see with this is that 443 is showing up as closed. (Suddenly, after months of successful operation.)

Fiddling with the static NAT mappings on my router, though, other ports work just fine when mapped to the same home-automation endpoint: 442, open and responsive, 444, open and responsive, but 443, nothing.

Thanks,

-c