Thanks, Kim, for the information. I share Brett's sentiment that you seem to have followed procedure without undue delay, so at this stage in the process I see no cause for concern. I guess someone will eventually produce a report of what actually happened that originally caused the "outage". That would make an interesting read for us DNS nerds, and possibly good input to others to help them avoid the same problem. Best regards, /Liman icann-csc@icann.org 2022-03-09 16:44 [+0000]:

Dear colleagues,

I wanted to provide you some insight into an issue with .fj, that the operators have summarized at https://www.domains.fj/index.php/announcements/3/.fj-Domains-Outage.html and has been re-reported at https://domainincite.com/27628-dnssec-claims-another-victim-as-entire-tld-di...

Of particular interest to us is the implication that this request had to wait for our normal business hours to be processed.

We operate a 24x7 emergency line, and it was used in this instance. The .fj manager called this number at approximately 3am our local time, and our team started processing their ticket just a few minutes after that. There wasn’t any delay caused by a need to wait for our regular working hours.

Please let us know if you have any questions.

kim -- Kim Davies VP, IANA Services, ICANN President, PTI _______________________________________________ ICANN-CSC mailing list ICANN-CSC@icann.org https://mm.icann.org/mailman/listinfo/icann-csc

_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.