While I look forward to the root cause analysis, I’d appreciate an earlier communication containing at least:
* the length of the outage including start and end times
* the services which were unavailable
* observed symptoms from a user’s perspective
This ensures that we can account for any errors observed in our systems without assumptions regarding time and behaviour.
For future outages, I’d urge the sending of a notice informing TMCH service consumers (Registrars/Registries as relevant) of any issues immediately.
It is simply good operational practice to do so. The detail can always follow later, but we should not be left to guess whether there is in fact an outage, in this case for nearly 2 days.
--
Kal Feher
From:
gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org]
On Behalf Of Rubens Kuhl
Sent: Wednesday, 1 July 2015 9:06 AM
To: Aaron Hickmann
Cc: gtld-tech@icann.org
Subject: Re: [gtld-tech] TMCH - Service not available
Aaron,
At the last operational issue TMDB had, registries were denied information while industry press got details on what happened. I sure never received any further information on that one.
Let's hope that doesn't repeat itself and ICANN inform contracted parties at least at the same time.
Rubens