+- Post4VPS Forum | Free VPS Provider (https://post4vps.com)
+-- Forum: Site Discussion (https://post4vps.com/Forum-Site-Discussion)
+--- Forum: Announcements (https://post4vps.com/Forum-Announcements)
+---- Forum: VPS Downtimes (https://post4vps.com/Forum-VPS-Downtimes)
+---- Thread: [SOLVED] VPS 16 Control Panel Down (/Thread-SOLVED-VPS-16-Control-Panel-Down)
[SOLVED] VPS 16 Control Panel Down - Pacific Spirit - 07-05-2019
Hello,
I am Gregory from HostLease Expert Team. We aware of a downtime of VPS 16 which was noted by Dean. We are currently working on this problem and we can guarantee that it will resolve today. We only asking the patience for Post4VPS but the VPS servers will working again today
This is a promise from us.Regards,
^Gregory J. C.
RE: VPS 16 Control Panel Down - chanalku91 - 07-05-2019
The thing that makes your patience the most tested!
Make sure to provide AQUA before testing the guts
RE: VPS 16 Control Panel Down - deanhills - 07-05-2019
Thanks for submitting this Gregory - @Pacific Spirit. It's 9:30 a.m. here in Canada and when I checked earlier on, hoping everything will be working, noticed the reseller panel URL is still not working. Hope for @chanalku91 you get it sorted out extra soon. Will also be nice, if it is possible, if you could explain to us what happened, and how Hostlease solved the problem. We're always curious about technical explanations like that here at post4vps.
RE: VPS 16 Control Panel Down - Pacific Spirit - 07-05-2019
Hello @deanhills and @chanalku91,
The issue have been resolved. There was a routing problem in the DC network. It have been fixed now. Please have a check it.
^Gregory J.C.
RE: VPS 16 Control Panel Down - deanhills - 07-05-2019
Fantastic, thanks very much for your assistance in sorting this out @Pacific Spirit. I guess it's when things like this happen that one really gets to know the host - we appreciate your effort in getting it up and running again. Thanks for keeping us up to date both in the support ticket and here in the Forum.
I'm going to close this thread now as "solved".