This is only one of several recent eNom problems. I was pushing a large list of domain names via list wizard from my main ETP account to a sub-account of mine. I accidentally included a name that I had sold a few months ago, which was no longer in my account. My mistake to include the name on the list, I admit. What do you think happened? Do you think I got an error saying the domain is not in my account to push? No, the domain was pushed from the account of the new owner to my subaccount! I asked eNom to return it to the owner and they told me such requests must come from the account the domain was pushed from. I told them the owner of that account did not do the push, and they told me that was impossible, that they had tested and retested their software and that could not happen. (In other words, I am a liar.) They said their records show that it was pushed from the new owner's account. I asked them to look at their logs to see if anyone was logged in to that account at the time. No answer. They absolutely refused to put the domain name back where it belonged at my request, even though I own both the ETP account and the account the name was pushed to - for "security" reasons. I had to get the new owner involved to correct the problem (very embarrassing for me).
Another problem - global edit. I decided I better move my domains to a safer place (see above) so I tried to use global edit to remove the registrar lock. It worked, at least in the eNom control panel. Unfortunately the registry did not agree that the domain names were unlocked, so I had to go back and unlock all the names again.
Another problem, eNom DNS. I didn't realize when I put 2000 names on eNom's DNS that there would be no way to ever get them off without shutting the names down for two days. When you take a name off eNom's DNS, eNom's DNS servers stop working immediately for that name, even though the name servers in the TLD zone won't be updated for 12-48+ hours. Lost traffic = lost money. This is partly a problem because of slow TLD zone updates for .com and .net, which will hopefully be rectified next month when they go to fast updates, but eNom could easily keep the zones alive in their servers for a couple of days.
I could go on with a few more personal examples of additional problems, but you get the idea. I want to like eNom, but lately they are scaring me.