It's working for most people yes. There were DNS changes whose propagation take up to 48 hours, nothing to do with sysadmins or server config, it's just the way internet works. Most of the world received the changes properly 12+ hours ago, you're probably colliding with either your ISP's or your endpoint's DNS cache. Flushing local DNS cache from OS and browser (or trying another browser) may provide remedy
The http IP address mentioned isn't configured properly to use the mainnet and not maintained as a service by Heat Ledger Ltd.
http://heatledger.com company web site isn't hosting a wallet service, is mostly for view only and is not secured by SSL currently like most standard web sites.
maintained by your company? What ip is the secure connection supposed to resolve to?
Seems like I'm not the only one with problems.