I was working late on Friday when I was hit with the feeling/realization that Afrihost kills services early. That realization did not come from nowhere. This had to be prior experience. Between signing up everyone I know for Afrihost's R29/gb service 10 years ago, or signing up everyone for the free mifi stint, or signing up everyone for the uncapped stint, I recall instances where the services were killed before the "sensible" cutoff time, from a consumer perspective.
(man, I made some good cash during these stints - needed it, as I was going through difficult times - would recommend Afrihost to one person, they would struggle with the setup or something, I'd quickly help via remote desktop, earn a R100 and they would then recommend a friend and it snowballed a few times)
This in turn bit me in the ass over the years, as the "
you touch it you own it" principle kicked in. Any small issue landed on my doorstep and I felt obligated to help etc or even help with an alternative service.
Correct me if I am wrong, but this has been going on for ... since forever? Aka this is the norm, with termination scripts run before midnight?
While I understand that, if it was programmed to do X, it can be programmed to do X properly, can't it? Of course I am saying this from the viewpoint of a consumer, without having in-depth knowledge of the underlying systems. While I am familiar with WHM, it was always in a manual capacity and never programmatically.
I left Afrihost aeons ago, by the way. This was simply me trying to help someone, as they were having issues and they were being charged for all changes (by a 3rd party) to make changes to their own website. I imported a copy of the site to Absolute Hosting (sorry, Afrihost simply does not have the best track record service-wise anymore) and left them to to play around in wordpress to their hearts content. This way they could figure it all out for themselves, without the danger of breaking their own site.
I did not suspect any ill intent.
In any case. I rushed back home on Friday, and managed to download a fresh copy of the database/emails and a full account backup. Then, while I was busy doing a remote server import of their wordpress via softaculous on the backup server, the transfer failed. It took me a while to figure out what was going on. A ping finally revealed that the Afrihost DNS had stopped serving the domain, well before midnight, and thus the errors. So while this issue did not really cause the client any inconvenience, it caused me a lot of inconvenience since I then had to faff around to sort things out in the end.
What you could check/explain to me, if you have a moment, is the dedicated IP the client was billed for since 2019-04-24 though. I am interested to check what dedicated IP were assigned to them for the duration that it was billed for. Was it 154.0.171.xx?