Skip to content
Register

OVHcloud support ticket: 47 days and counting

General Discussion by LichunLars 3 replies 120 views
LichunLars

Member OP

#1

Day 0: Opened ticket #892341 — OVHcloud VPS unreachable after "maintenance window"
Day 3: Auto-reply: "escalated to senior team"
Day 7: Human reply: "checking with network ops"
Day 14: My reply: any update?
Day 21: Auto-reply: "ticket marked resolved" — VPS still down
Day 22: Reopened. New ticket #892442 "related to previous"
Day 30: Human: "apologies for delay, investigating"
Day 35: My traceroute:

traceroute to 203.0.113.47, 30 hops max
 1  192.168.1.1    0.5 ms
 2  10.0.0.1       1.2 ms
 3  * * *
 4  * * *

Route via OVHcloud core adds infinity ms. Server gone.

Day 47: No reply to ticket. Posted on forum. This forum.

Who else waiting? Let's compare.

1ms or I don't want it
SingaporeRep

Member

Benchmark Addict

#2 
Fio test: (mixed r/w 50/50)
  read:  IOPS=0      BW=0 KiB/s
  write: IOPS=0      BW=0 KiB/s
  latency: N/A (host unreachable)

iperf3: connection failed
yabs.sh: "are you sure this server exists?"

Disk's decent, network's meh — wait, no network meh everything.

My ticket #892105, day 39. Same "maintenance window." OVHcloud is a black hole.

fio, iperf, geekbench. results or gtfo.
reykjavik_doc

Member

container skeptic

#3

Actually docker is just chroot with marketing but thats not the point

systemd could have restarted your VPS but OVHcloud probably uses sysvinit or something worse

Þey should self-host using þis guide I wrote at 3am: "escape cloud providers using spare thinkpads"

Anyway 47 days is impressive. Almost art.

AL

Member

#4

47 days and they still have not checked traceroute

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft