All method described are not working in case of fail.
If your network is down there are five(or more really) possibility:
1) The client request
http://www.google.com page which already are on your DNS, AND YOUR CLIENT USE YOUR DNS, and correctly the system display the maintenance page.
2) The client request
http://www.google.com page which already are on CLIENT DNS cache, and correctly the system display the maintenance page.
3) The client request
http://www.google.com page, but client use external DNS like 8.8.8.8.
The DNS are unable to resolve the address and the client browser display "server not found" instead a maintenance page.
4) The client request
http://www.google.com, but you do not have
http://www.google.com cached on your DNS.
The DNS are unable to resolve the address and the client browser display "server not found" instead a maintenance page.
5) The client request
http://www.google.com, the client use YOUR DNS, and you have the DNS configurable to answer all the time with fixed IP for not found DNS (like OpenDNS), and in this way the client display correctly the maintenance page.
*******************
For aacable only:
Hint: STOP using third party source for check....
Think if one time Google stop service for maintenance on 8.8.8.8
Have you one idea about how much system are considered faulty / reboot / wrong routing.....
*******************
/ip proxy access add action=deny disabled=no dst-port="" redirect-to=10.0.0.1/netdown.html
You will have to make a file on the mikrotik called netdown.html which will be called anytime the rule is enacted.
You virtually gain another -1 on Karma.
Have you tried this? "make a file on the mikrotik called netdown.html"
You can not put file inside mikrotik routerboard and make it visible directly. except when using hotspot or customization package (if you buy one stock of 1000 Level3 devices)
"redirect-to=10.0.0.1/netdown.html" are referred to another web server, not routerboard itself.