After searched on HN, I found many people were not satisfied about the stability of .io domains.<p>https://hn.algolia.com/?q=.io+domain<p>So, should I use a .io domain for my site? Or I should use something else?
The DNS for .io is (now) operated by Afilias on their anycast network. It is the same network of servers that are operating .org, .info, and a few dozen other TLDs.<p>Despite any support or administrative issues you may encounter, the technical infrastructure is sound.
They’ve had multiple large DNS outages during the past couple of years.<p>Stable is relative, of course, it’s still going to be online more than 99.9% of the time, but compared to e.g. .com or the myriad of other ccTLDs they’ve been fairly unstable.<p>We ended up switching domain for our service, because they (.io) caused our only two outages during a one-year period.
I've been using it for years and never noticed anything. But I think it's a good idea as a precaution to leave only things like landing pages in the IO domain, and setup the API or dashboard app in a separate .com domain.<p>I remember reading in some comment here on HN I think that their support does not reply on weekends.
Good article on keeping DNS resolution more stable:
* Longer TTLs
* Secondary DNS<p><a href="https://medium.com/@brianarmstrong/youre-probably-doing-dns-wrong-like-we-were-6625efaed390" rel="nofollow">https://medium.com/@brianarmstrong/youre-probably-doing-dns-...</a>
The io cctld authoritative dns servers are not very competently run. There have also been security issues like <a href="https://thehackerblog.com/the-io-error-taking-control-of-all-io-domains-with-a-targeted-registration/" rel="nofollow">https://thehackerblog.com/the-io-error-taking-control-of-all...</a><p>'tptacek would add that a cctld that is under control of the five eyes governments is less secure because the registry can be interfered with more easily than .com, though I think that's kinda theoretical.