Skip to content

Hetzner remembered my ticket from two years ago

General Discussion by harbourops 16 replies 2.1K views
2 #11
olespete said:
May 2024 isn't two years ago

May 2024 to August 2026 is two years and three months. Close enough for a support thread, Pete.

jihoonred86 said:
Numbers dont lie. Ticket history is cope for bad hardware.

Numbers without context lie constantly. Your InterServer VPS is in Secaucus or LA. Hetzner's Singapore DC is newer, smaller pipe, different peering. Comparing iperf3 to a host ten thousand km away proves geography, not hardware.

You can check their actual routing at https://bgp.tools.

virsh list --all | wc -l: 47
#12
kate3 said:
Do they keep logs for all customers or just the vocal ones?

I asked myself the same thing after I posted. Twenty years and I still don't know if good support means good systems or good luck.

Contabo answered my last ticket in four hours but it was a copypaste about rebooting. No continuity, just speed.

IPv4, IRC, and irssi — fight me
#13

I have Hetzner in Falkenstein, Hostinger in Amsterdam, and InterServer in Secaucus. The only provider that ever referenced an old ticket was Hetzner, and it was for a billing question from 2023.

The other four don't even remember my name. Multi-cloud means multi-amnesia.

#14
kate3 said:
Comparing iperf3 to a host ten thousand km away proves geography

My benchmark is from Singapore to Singapore. Hetzner SG to local iperf3 server. Read the thread before you lecture.

Still not great numbers. Disk is fine, network is meh. Ticket history doesn't fix routing.

fio, iperf, geekbench. results or gtfo.
#15
speedasad said:
Which MySQL version was the legacy stack running?

5.7.44. I know, I know. Client requirement, not my choice. The ticket was about optimizing tmp_table_size and max_heap_table_size without breaking their ancient CRM plugin.

Hetzner support suggested values, noted them in my account, and when I reopened this month they saw the prior config and caught that the CRM vendor had since published a compatibility patch for 8.0. Saved me from tuning a dead end.

1 #16
harbourops said:
5.7.44

My condolences. I still have a client on 5.6 in some Romanian DC. At least yours is getting guidance toward 8.0.

Two years of notes for a LAMP stack is more documentation than most enterprise clients get from their own IT.

airgapped, encrypted, faraday'd, still worried
9 #17
SingaporeRep said:
My benchmark is from Singapore to Singapore

Then Hetzner SG is worse than I thought. InterServer LA to Seoul still gives me 600+ Mbits — https://www.speedtest.net. Their trans-Pacific routing is solid.

Ticket notes are nice for people who break things. I don't break things. I benchmark.

Post a reply

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

Post reply Preview Save draft