6 ms·

Just for future reference, it's usually considered a good idea to put your status page on completely independent infrastructure so that it stays up even when th

by jik 13y ago

Just for future reference, it's usually considered a good idea to put your status page on completely independent infrastructure so that it stays up even when the rest of your stuff goes down. A status page that doesn't work during an outage isn't particularly useful.

kennhardy 13y ago
Like!
- backspaces 13y ago
  Not having separate status hosting is liken not salting passwords. As a NC user, I may leave just for this reason
ilikesnowflakes 13y ago
If the hackers really want to take you down, adding another server in isn't very hard...
- jik 13y ago
  If you're as big as NameCheap, you can afford to pay CloudFlare or somebody like it to protect your status page.
  - jkirker 13y ago
    Cloudflare has also been nailed the last 3 weeks in a row causing outages. Just search Twitter for cloudflare DDOS or NTP or etc. etc. etc. At the end of the day there are currently so many slave machines out there we are all vulnerable. It's just the nature of things. At least outages are only temporary. It's much better than the early days were we'd be down for 12 hours at a time. https://twitter.com/search?q=cloudflare%20attack&src=typd https://twitter.com/search?q=cloudflare%20attack&src=typd
- nc-customer 13y ago
  I suspect the hackers are targeting one of namecheap's customers, not namecheap directly. Because that's usually the case, a good approach is to not give all customers the exact same nameservers.
  - sparagi 13y ago
    I agree. We left Network Solutions b/c they were hit 3 times in less than a year. Maybe the website targets moved to Namecheap, so they were targeted also?
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.
- 13y ago

by jik 13y ago

kennhardy 13y ago

Like!

backspaces 13y ago
Not having separate status hosting is liken not salting passwords. As a NC user, I may leave just for this reason

ilikesnowflakes 13y ago

If the hackers really want to take you down, adding another server in isn't very hard...

jik 13y ago
If you're as big as NameCheap, you can afford to pay CloudFlare or somebody like it to protect your status page.
- jkirker 13y ago
  Cloudflare has also been nailed the last 3 weeks in a row causing outages. Just search Twitter for cloudflare DDOS or NTP or etc. etc. etc. At the end of the day there are currently so many slave machines out there we are all vulnerable. It's just the nature of things. At least outages are only temporary. It's much better than the early days were we'd be down for 12 hours at a time. https://twitter.com/search?q=cloudflare%20attack&src=typd https://twitter.com/search?q=cloudflare%20attack&src=typd
nc-customer 13y ago
I suspect the hackers are targeting one of namecheap's customers, not namecheap directly. Because that's usually the case, a good approach is to not give all customers the exact same nameservers.
- sparagi 13y ago
  I agree. We left Network Solutions b/c they were hit 3 times in less than a year. Maybe the website targets moved to Namecheap, so they were targeted also?

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.
13y ago