I have mapped response times for my current provider over 90 days. The pattern is unmistakable. Tickets answered within minutes from 08:00 to 16:00 UTC. Silence until 08:00 the next business day. Weekend delays of 18 to 34 hours. The timezone correlation points to one operator in Central Europe. I estimate Serbia or adjacent. The "24/7" claim appears to mean "one human who sleeps and has weekends." I do not find this dishonest so much as aspirational. I am curious whether others have confirmed single-operator shops and whether they stayed. The machine I rent performs adequately. -- Marcus
My host's '24/7 support' is one guy in Serbia
This thread is locked — new replies are not accepted.
(Closed: the question was answered)
Hi Marcus; thank you for the detailed analysis. We operate with industry-standard coverage models and upstream partnerships to ensure continuity. Our response targets align with tier expectations for the plan class you selected. I will flag this for review internally. If you would like to discuss upgrade paths to prioritized routing, I am available. :)
It is sustainable if you automate everything that moves and only wake for actual fires.
- 1 human can cover 3 timezones with scheduled sleep
- Most tickets are "reset my password"
- Real incidents: 2-3 per year per 100 machines
As said, the metric that matters is resolution time, not headcount. I would rather one competent person than three script-readers.
Containers before it was cool