Indeed, it is an issue we see as well. The only solution we have is to: a) send the FOA to both registrant and Admin-C b) advise the customer clearly and plainly of the steps needed to complete the transfer c) do more b) as part of the process to transfer The statistics you quoted are interesting though. As most of our transfer request are provided to us by our resellers, we are unable to do the same with regard to verification of the customer details, and therefore cannot differentiate between authorized and unauthorized transfer requests beyond doing the FOA and verifying the Auth-code. Volker Am 12.05.2014 18:19, schrieb Rob Golding:

...

actually, there is no need for any action with regard to the FoA from the losing registrar. The only FOA requiring registrant action is the FOA sent by the gaining registrar. Typo :)

...

...

1131 transfers failed at least once due to FOA issues 986 either didnt get, didnt understand or didnt realise they needed to follow the FOA from the losing registrar s/be

986 either didnt get, didnt understand or didnt realise they needed to follow the FOA as well as instructions from the losing registrar

Rob