We are happy to receive reports about problems, no matter the source. However, if you report a technical problem with someone else's services, you may get a frustrating response.
From time to time, we get reports like, "I went to www.example.com and it was down! Fix it! You people suck! Your servers suck!" While we can generally say "Yes, the site is down," we do not go into why or when it might be back in response to such a report, which sometimes means the person goes away believing that not only do we suck, but we suck on purpose!
There are many reasons a website might be offline. Maybe the person couldn't pay. Would you want us to discuss your billing status with anybody who asks if it was your site? Probably not. But if we respond to all "site down" complaints but only stonewall the ones where billing is involved, stonewalling becomes a substitute for saying that it's a billing problem. So, to protect our members' privacy, we must treat everything as a private matter even if it makes us look like we're unwilling or unable to fix a problem.
(Those who are paying attention may have noticed the similarity to the old philosophical problem of encryption: if you only encrypt things when you have something to hide, using encryption is a clear sign that you have something to hide. For encryption to be maximally effective, you have to encrypt as much as possible. Others may have had similar experiences trying to find out the condition of their hospitalized friend.)
Of course, if you're having a problem with your NearlyFreeSpeech.NET services, you can always expect full disclosure regarding any issues and our full support in helping to resolve the problem.