Affected
We are currently investigating this incident.
This seems to be isolated with 1.1.1.1, and not 1.0.0.1 for nameservers