Annnnd we're back! Sorry for the inconvenience

[GizBeat]

Normally things go quite smooth when admin does maintenance. However, this time around there was a miscommunication between hosting and CPA and a transfer of servers was not scheduled properly.

This was the first time in 2 years we have had more than a few minutes downtime and we are very sorry for any inconvenience or frustration.

Regards,
Gizbeat and CPA Admin

[mirandam]

Are you using cloud based hosting? And I mean REAL cloud, not those hostings on a server just named cloud while in reality they only comprise of one physical server.

---

hmmm, just a small research indicates you're using cloudflare which indeed does real cloud services. Strange though, normally this should imply no downtime at all.... unless the cloud structure goes haywire....

[aus9]

and did you notice this?
[Only registered and activated users can see links Click here to register]

DNSSEC: unSigned

[Only registered and activated users can see links Click here to register]

I don't run a server BTW

[GizBeat]

We changed servers. As I said, there was a miscommunication regarding server transfer time between CPA and hosting. If hosting transfers the site, but CloudFlare point IP remains unchanged... Guess what happens.

[linr76]

umm - my guess would be 404 error?

[mirandam]

indeed I did, first thing I saw actually.
Doesn't make any difference though, doing a trace you can find the ip anyway (104.28.xx.xxx).


What I do is basically detach my dns service from the actual hosting by means of a dedicated dns service giving me full control of what and when it happens, change the ttl to 300 or even lower to have quick propagation and off you go...


Cloudflare has a truckload of resellers, one of which in fact is one of my hosting companies, not my mayor though.

---

umm - my guess would be 404 error?

which is easily solved doing a redirect on the 404 page to the new ip.
Same thing as when a site goes down and your redirected to an "information" page on a different server.

[GizBeat]

umm - my guess would be 404 error?

which is easily solved doing a redirect on the 404 page to the new ip.
Same thing as when a site goes down and your redirected to an "information" page on a different server.

For the 3rd time, there was a miscommunication regarding the timing of the transfer. Admin is fairly competent, but reading emails and repointing CloudFlare while sleeping isn't in the toolbox.