In reply to G3NYY:
It’s up every time I’ve tried but that doesn’t mean it’s not been down at some point. I’ve looked and I know which files are recreated when the code reboots and the timestamps on those says the webserver code has not been rebooted. So probably the database server has been at issue.
There are two “servers” involved for the database. A webserver running our custom code and a SQL server running the actual database. The webserver runs our code to display the raw database data. This is all in a hosting centre somewhere in the UK, Manchester I think.
What can happen is that connectivity between the webserver and database server can be impacted leading to errors. This maybe because the internal network is full or because switches are overloaded or the database server is rebooting. If you can get some of the database pages appearing but can’t log in or can’t add data then that suggests the database server is not talking to the webserver. If you can’t get anything then it could be webserver is rebooting/offline etc.
Normally things come back very quickly. The hosting company know that if stuff goes offline for more than a few minutes their switchboard will light up with people making fault reports etc. So they do work their hardest to minimise impact. It affects us by being a pain in the proverbial but for some of their clients they’ll be loosing money.
The good news is the code was written with faults like this in mind. Not by me but by Gary who created the original system. This means any partially entered data should still be around when you try to enter it again. Maybe you will have lost just the last line entered, but a partial log should be offered for completion when you try to enter it again.