ns-a1.io timesout on every request
so do all the others
October 27, 2016: KSK rollover process begins as the new KSK is generated.
July 11, 2017: Publication of new KSK in DNS.
September 19, 2017: Size increase for DNSKEY response from root name servers.
October 11, 2017: New KSK begins to sign the root zone key set (the actual rollover event).
January 11, 2018: Revocation of old KSK.
March 22, 2018: Last day the old KSK appears in the root zone.
August 2018: Old key is deleted from equipment in both ICANN Key Management Facilities.
PS - thank you for mentioning this, I wasn't aware it was going to happen until reading your comment.
Not sure why that was taken of the front page suddenly.
Interestingly enough I found that only some of them were returning NXDOMAIN's, so resolution would sometimes work and sometimes it would fail completely.
"Some customers have reported intermittent resolution issues with .io domains. We can confirm that Route 53 DNS services are operating normally at this time and these issues seem to be related to the .io top-level domain provider."
My problem is that we have scripts all over customer websites hardcoded with api.gator.io
We're going to have to have them update the scripts and that is going to be a major pain.
I think the common practice of misusing TLDs (such as registering an .io domain if you are not from the British Indian Ocean territory, or having a Soviet Union domain... a country that no longer exist), is bad.
However, I acknowledge this is not the root problem. The root problem is the scarcity of domains under traditional TLDs, and that's in great part due to speculation (e.g: domain parking). It is hard to establish what constitutes
placeholder content, therefore rules preventing domain parking are hard if not unfeasible to forbid.