Skip to main content

ICANN57: A Real-Life Audio-Video Disaster Recovery Story

Very few people realize what it actually takes to make an ICANN meeting run smoothly from the Network Operations Center backroom, where the InfoTech team orchestrates its magic with high energy. You’ve probably experienced the excellent remote capabilities to encourage diverse participation, good wifi on site, and generally, things run smoothly so you can focus on the real issues and discussions at hand. And this is a good thing.

After Helsinki, we were starting to get prepared again...when we got the news that there was a fire aboard the ship which contained our equipment being transshipped from Helsinki to Hyderabad. (Spoiler alert: I’m pleased to confirm all equipment is now in Hyderabad, and the team is setting up for what will again likely be an excellent meeting.)

Let me share this remarkable disaster recovery story.

When we began preparing for ICANN57 months ago, it was all fairly routine. We packed and shipped all of our technical equipment in a 40-foot and 20-foot sea container which included: 80+ crates containing over five miles of network cables, over 400 microphones, 650 international power strips, 75 MacBooks. We were preparing to get 800 mbps of bandwidth, at least two Internet service providers with redundant paths, and more.

Within a week of the fire, we were told that the 40-foot container was in good shape, but the 20-foot container had possible damage from the fire and would be held for further inspection in Germany.

We were instantly struck by the unique dimensions of this extraordinary incident. A fire on-board a seafaring container cargo ship, while the ship is docked in Germany, en-route to India. We also discovered how complicated the whole situation was given the ship belongs to an international company, the contents belong to a US corporation, the forwarding-agent is based in the US with inspection-rights governed by (200+ year old) maritime laws and with Insurance brokers and adjusters involved from both sides of the Atlantic. The multi-national dimensions of this incident were quite remarkable.

We immediately made back up arrangements. Having catalogued exactly what was in each crate, we enacted two plans: a) a short-term plan to purchase replacement equipment so ICANN57 experiences no disruption; and b) a longer-term plan to work with insurance brokers (under maritime law) to recover the ‘stuck’ 20-foot container. This took a lot of work in a short amount of time, given the sophistication of our gear, which in total cost ICANN about $700,000 USD of unplanned expenses (the equipment itself plus shipping and other costs).

But the real story is that of the ICANN InfoTech team. The manner in which this fire incident was handled is just another example of the professionalism and dedication that the ICANN org team members take to ensure we support the community. I am so proud of our team for working days, nights and weekends to work with every supplier, replace all equipment as well as pack it (our office was a bit of a mess!) and make arrangements to have it air-lifted to India. This was all to ensure that equipment would arrive in Hyderabad in time so that there will be no disruption to our service we provide at ICANN57. Take a look at this time-lapse video from ICANN49 to see just how much goes into setting up an ICANN Meeting.

I wish everyone safe travels if you’re heading to India and hope to see many of you soon – either in person or online.



    Rajesh  00:22 UTC on 01 November 2016

    Happy to say that such a big event is going to be hosted in Hyderabad. Hope ICANN57 in Hyderabad will improve investments in Telangana in Internet sector.

    monmariageoriental  18:30 UTC on 01 November 2016

    Great !

    johntystr  22:38 UTC on 02 November 2016

    Hello There! Thanks For sharing. Its a great news to telangana people. I also read about this in Tamilmani.

    lily Lily  14:48 UTC on 03 November 2016

    It is so important in our time. Fi Fund is doing great things. We should help each other, because in our global world - it's a big family. Thanks for those posts. I appreciate it prayer times

    marklooper  23:11 UTC on 20 November 2016

    Clever work and exposure! Keep up the great works guys I’ve added you guys to blogroll. Roof repairs Townsville | Peugeot service Melbourne

    Melkior Magicien  03:22 UTC on 05 February 2017

    Thank you for the information

    blogdechollos  10:46 UTC on 20 February 2017


    jack  10:44 UTC on 18 May 2017

    We generally tend to rectangular degree the company offering you the best services concerning within a brief amount. 24 hour check cashing

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."