No, it's there, not too early. Best guess is that you have an old cache. This happens sometimes, from what I hear from release team folks. Should sort itself soon.
(I'm noting this separately from my other comment)
I found that not using the ISP DNS on your router helps with this problem on several sites, this being one of them, among other benefits
I recommend everyone use something like OpenDNS, Google's public DNS resolver (if you're comfortable with that) or CloudFlare via 1.1.1.1 (and associated addresses), or any other myriad of reputable third party DNS services
OK, can see it now, too. Caches...