4 ms·

Good point. The status page is on another cloud but since this is a DNS issue, the subdomain is down. In the future, we'll investigate running this page on a se

by ted0 13y ago

Good point. The status page is on another cloud but since this is a DNS issue, the subdomain is down. In the future, we'll investigate running this page on a secondary DNS.

jik 13y ago
According to whois for namecheap.com, the DNS for that domain is hosted on dynect.net, and "host status.namecheap.com" resolves just fine (to 204.232.212.56), so it does not appear to be a DNS issue that is preventing your status page from working.
- ted0 13y ago
  I stand corrected. It's on Rackspace, which apparently is also experiencing issues.
  - ted0 13y ago
    Rackspace helped us get our status page back online: http://status.namecheap.com/ http://status.namecheap.com/
irontoby 13y ago
Posting up-to-the-minute updates on Twitter is also a good idea. Lots of tweets come back from a search for "Namecheap" & you want to be sure you're a part of that conversation!
- Jailout2000 13y ago
  They've been posting updates 30 minutes before your post buddy, and still are now. https://twitter.com/Namecheap https://twitter.com/Namecheap
- ted0 13y ago
  Yes, we are actively posting updates on Twitter.
duhorg 13y ago
Perhaps also investigate allowing customers to slave their own secondary DNS, too? (That is, allow AXFRs.) This has been a feature requested for, as far as I can tell from the support forums, four years now. It should be possible to make this allowed/disallowed per-zone, and as far as I'm concerned, I don't care who is able to download my tiny zone file. It would allow me to add more diversified DNS servers in the face of things like a DoS against Namecheap.