4 of 5 reboots left no crash dump — their "investigation" never explained that.
Paying trading-VPS customer. My server had 5 unexpected host-side reboots in two weeks — 4 of them with no crash dump at all. I proved the VM's dump config worked (the one reset that was a guest fault — a memory-management bugcheck, 0x1A — wrote a full dump), so 4 resets with no dump means the OS never got the chance to fault — the VM was reset below the OS, from the host. I sent the exact timestamps, event IDs and this reasoning. Their reply: a host "investigation" that declared no host fault, pinned everything on the single guest crash, never addressed the 4 dumpless resets, and offered me a fresh VPS on another node instead of an answer. The thread ended there, unresolved. Every one of those reboots also takes MT4/MT5 and any live EA down with it. Another time I messaged live support about an issue and, instead of asking my approval, they just restarted the server while my EAs were live and trading. Straight answers were the recurring problem: repeated "no anomaly" replies, and at one point I was told to stop "using AI" and keep my messages short — in a support ticket, which is exactly where the technical detail of a technical fault belongs. Execution was sloppy too. The VPS control panel itself errored out, so I had to message support to fix the tool I manage my own server with. New orders came back with specs I'd given ignored (two-drive storage, port 8080 for API), and the location was wrong on the invoice, so I had to message live support each time just to confirm I'd actually get the London server I ordered. The conduct matched. When running many MT5 instances froze the GUI — a Windows limitation, not their fault — live chat's reaction was to offer a retention discount rather than just tell me that; the straight answer only came later. When I asked for a refund, I was brushed off before I could explain, as raising it "over and over." The cancellation reply then claimed every ticket was "answered timely with proper explanation" (it wasn't) and leaned on my discounted rate as if that excused any of it. I didn't leave over hardware. I left over the support and the sloppy execution — and moved to a provider I expect to handle both better. re: FxSVPS's reply: I never claimed a host hardware fault. That's the question you keep answering. My claim was that the VM was reset below the OS — a host-level action, whatever its cause — and that is still unaddressed: 4 of the 5 resets produced no crash dump, and your reply doesn't explain them either. Your own investigation report also listed administrative stop/start tasks on my VM (qmstop:117 / qmstart:117) on 3 June — the same day as two of the resets — dismissed as "normal lifecycle operations," with no explanation of who triggered them or why. The discount has no bearing on whether those reboots were ever explained.