They asked for permission to reboot in rescue mode, and I specifically agreed conditional to rebooting it in normal mode after the work is done. Apparently they interpreted "work" as "doing nothing for 13 hours".
-
-
Show this thread
-
They just responded to my ticket, and there is now an official incident for the IPv6 issue (which had nothing to do with my server, as expected). So they ignored my instructions to reboot the server back in normal mode, and in fact taking the server down at all was unnecessary.
Show this thread -
So let's recap: * They don't have monitoring for IPv6 connectivity/DHCP (their status dashboard showed no issues) * They immediately ask to mess with customer machines to diagnose *before* confirming that it isn't a wider-range problem on their end
Show this thread -
* Their internal incident management is dysfunctional, with no update to the customer after the issue was identified as generalized * On top of that they explicitly ignored customer instructions to restore service ASAP after work was done
Show this thread -
Open to suggestions for competitors in the ~€15/mo low performance dedicated server class in Europe. Specs are Avoton 8C/8T, 8GB RAM, 1TB HDD. I need IPv4 and IPv6. I can handle disaster recovery myself, as long as support aren't incompetent like this.
Show this thread -
-
Show this thread
End of conversation
New conversation -
-
-
@a_bermingham may I suggest you take a look at what went wrong here ?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yeah
@Scaleway did the same thing with my server last year when I opened a ticket about IPv6 connectivity issues. Just asked to put my server in recovery mode, then did nothing with it in recovery mode for hours until I turned it back on and the issue was unrelated to the server.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.