New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
DigiRDP so far
So I am trying out DigiRDP on their Cogent only network due to supposedly good uptime on their status page.
However today I was greeted with the vps being offline for exactly 2 hours.
The status page had nothing about it. Only 1 node showed an issue for 18 minutes. I have no idea if I am on this node or not but it was definitely not 18 minutes.
I asked support and they were unable to comment why it wasn't on the status page.
Sucks that you can never trust status pages.
Thanked by 1Caxen
Comments
Hello,
We sincerely apologize for the inconvenience caused by the recent downtime. While the status page accurately reflected the situation, the issue stemmed from the Virtualizor network. The bridge on that particular server malfunctioned, affecting only the VMs, not the server itself.
During our investigation, we identified the problem. However, while addressing it, the entire node's network went down due to a probable misconfiguration. Once the network was restored, we were able to locate and fix the underlying issue. This resulted in several instances of instability, and unfortunately, the VPSes were down for approximately 2 hours, as you noticed.
Please accept my apologies that you did not get a proper statement during this downtime from our support team.
We are truly sorry for any disruption this may have caused and appreciate your understanding.
The status tracker needs to be pointed at test VM instead of the node directly
I highly doubt any provider does that. You should be thankful that they have a public and detailed uptime status page that reflects historic downtime too. Not many providers nowadays are very happy at exposing that data since they're probably dog crap.
I only care about doing things the right way
Respect .... @balramm
Greatly appreciated
@balramm thank you for the statement. So this was just a virtualizor configuration error? The support agent told me it was caused by cogent.
Hello,
Yes, it was due to Virtualizor Bridge; I am really sorry that you did not get the correct information. could you please DM your email so I can investigate this internally?
Thanks.