>>>>>>Do you log unsuccessful login attempts?
>>>>>
>>>>>There is a lot of logs. I do not know why everyone seems to target the server infrastructure. A failure to reach a server is something that happens from time to time on the Internet. I face that on a daily basis actually with the tons of servers I am accessing. There are tons of reasons why a connection cannot be reached. As of this morning, I just have no idea what was the factor but it was out of my network.
>>>>
>>>>Yes, I understand that. I am just curious if you will be able to somehow detect that situation (not necessary address).
>>>
>>>If your server isn't being reached then it can't log anything :-}
>>
>>Well, with logs the *absence* of entries is itself information. If on a regular Monday morning the server sees X hits/hour, but today saw only 0.25X that can be useful information. I imagine that a lot of web sites that depend on traffic would flag something like that in their high-level dashboard monitoring systems.
>
>True - absence of expected traffic is obviously an indicator that something is wrong. I guess my point was that there will be no indication as to what the actual problem was.....

It could be argued it's important to automate this sort of thing. Michel was ( literally ) asleep at the time of this reported issue. When he became aware of it, the problem had apparently been resolved. Maybe an automated response could have run traceroutes or the like and zeroed in on a network outage somewhere. I don't know if Michel has SLAs with his providers but this sort of evidence is useful in making sure they live up to them.

ISTR there are 3rd parties that can provide uptime information, tested from multiple points on the web e.g. http://uptime.netcraft.com/ .