This is the appropriate blog site to post comments relating to registerfly.
This is a further update for those affected by RegisterFly. The first occurred Friday on our main website
If you are a RegisterFly customer you will know from the extremely poor customer service you are getting, that RegisterFly is experiencing internal problems prohibiting them from acting on transaction requests from customers.
ICANN is doing everything within its power to ensure that harm to registrants is minimized during these failures by Registerfly, including collecting registrant data from RegisterFly’s backend service providers, arranging for the registry operators to prevent names from being deleted (”dropped”) by Registerfly, and taking legal action against Registerfly in federal court for copies of their databases containing customer data. In addition, we have notified RegisterFly (as we are required to do under the Registrar Accreditation Agreement) that they are in breach of their accreditation agreement and have demanded that they cure the breaches of the Agreement within 15 working days (also required under the agreement).
You can find more detailed information on our website.
ICANN is not a regulator. We rely mainly on contract law. We do not condone in any way whatsoever RegisterFly’s business practice and behaviour.
The options for customers to transfer their names to another registrar at this stage are limited. We will advise if we have more information on this point. Last Friday, ICANN convened a telephone conference among those needed to implement a plan that will help cease unintended deletions. This will prevent names from being deleted from the registry and becoming available for re-registration by others. RegisterFly has assured us (for what that is worth) that they will process such requests as soon as they are again technically operational. We will keep a close eye on this.
We do hope this information is helpful and provides some small level of comfort in what is clearly a stressful time for registrants and others affected by these events. Check in at both here and at our website www.icann.org where these issues (amongst others) are being discussed.
You addressed your note to the Chair of the Governmental Advisory Committee, Frank Fowlie (the Ombudsman), and me (chair of the Security and Stability Advisory Committee). I can assure you each of us is deeply concerned about the problem you and many others are having with Registerfly. I can also assure you the ICANN staff are working vigorously to resolve these problems. Let me also emphasize that none of us are part of the ICANN staff in the usual sense. The Governmental Advisory Committee and the Security and Stability Advisory Committee are external committees which provide advice to ICANN. The Ombudsman, as is usual with ombudsmen, sits outside the staff structure and provides an independent path for complaints about the behavior or performance of ICANN staff. The GAC chair and I are not ICANN employees and don’t have access or control of the registrar contracts. The people who do have that access and control are on the ICANN staff, and, as I indicated earlier, Mike Zupke is the primary person to coordinate with. (If you’re not getting any response from ICANN staff. I’ll be happy to intercede if you’re having trouble getting attention.)
Last week The Register had a story which relates to my previous blog on registerfly: http://www.theregister.co.uk/2007/02/19/registerfly_angry_customers/ Here is my reply to the author of that story, Burke Hansen:
I am responding to your article “Registerfly on the fly, ICANN on the run”, dated Monday, February 19, 2007. In your article you quote a recent entry in my blog, and then assert that I have washed my hands of the matter.
I’d like to clarify a few points. First, with respect to the jurisdiction of my Office; the ICANN Ombudsman is established in the ICANN Bylaws. It empowers the Ombudsman to look into matters of fairness concerning decisions, actions, or inactions taken by the ICANN Board, its staff, or supporting organizations. Therefore, the ICANN Ombudsman does not have any jurisdiction over the commercial relationships between registrants and registrars. To give an example that may be more understandable, you live in San Francisco; if the City of San Francisco had an Ombudsman, that Office would have jurisdiction the city government, its staff and services. The Ombudsman would not have jurisdiction over disputes between consumers and business owners, just because the business or the consumer is located in that fine city or because the city passes bylaws that may regulate those businesses. ICANN can no more empower its Ombudsman to investigate registrar – registrant disputes than the city Ombudsman can act to resolve disputes between a computer retailer and its customer.
To put it another way, General Motors can’t help you if you received poor service at the local gas station.
Just as with the City Ombudsman, I have to respect the fact that there are agencies that have jurisdiction to deal with these issues. The registerfly consumers may come from any of a multitude of city, state, or national jurisdictions, with different consumer protection laws and regulatory frameworks.
Secondly, with respect to the individual consumers who have contacted my Office, I can tell you that I have looked at each complaint individually, and have responded to each complainant personally. Our Registrar Liaison Manager, Mike Zupke has followed up on each complaint I have referred to him, and these have all been identified to senior management at registerfly.
My Office has done a trend analysis of the complaints regarding registerfly which have come to my attention, and these have been transmitted to our compliance manager, and the registrar for appropriate follow up.
I recognize that consumers are presently frustrated with registerfly. I have attempted to advise consumers and registerfly of my concerns by putting factual information about the role of my Office in this matter on the blog. I have also informed them of the limits of my jurisdiction so that we don’t falsely raise expectations about what we can do. I am sure that you will recognize that no one wants to be listed on the Ombudsman blog as being problematic, and perhaps putting this into the public forum will provide some moral suasion for registerfly to deal with these consumer concerns. United States Supreme Court Justice Louis Brandeis has said “Publicity is justly commended as a remedy for social and industrial diseases. Sunlight is said to be the best of disinfectants; electric light the most efficient policeman.”
In the past couple of weeks, over 70% of the non-jurisdictional contacts my Office has received have concerned registerfly.
The role of the Ombudsman is to review the fairness of actions, decisions, or inactions taken or not taken by the ICANN Board or Staff. In these cases, consumers have essentially asked me to look into a matter involving a dispute between them and registerfly, and this falls outside of the powers given to me under Bylaw V. http://www.icann.org/ombudsman/documents/ombuds-frmwrk-eng-20jun05.pdf
In most circumstances, the matter would be reffered to Mr. Mike Zupke, ICANN’s Registrar Manager, and he would in turn pass along consumer concerns to the registerfly contact, who can be found by entering your domain name in the following search engine: http://reports.internic.net/cgi/whois?whois_nic=&type=registrar If, however, Mr. Zupke determined that the matter you are complaining about is unrelated to the Registrar’s Accreditation Agreement, or any other ICANN policy, he will likely encourage you to work out the situation with the registrar. The contact details above may be of use to you in contacting registerfly.