Skip to content

Hetzner: I fixed their network while waiting for reply

General Discussion by dadlime 6 replies 400 views
#1

So I opened a ticket with Hetzner at 2 AM. Their NOC was supposedly "investigating" a routing loop affecting my VPS in their Singapore PoP. Three hours later (like this) I got the automated "we are looking into this" ping. By 6 AM I'd traced the issue to a misconfigured VRRP priority on their edge router. Wrote a quick patch, tested it via their looking glass, and replied to my own ticket with the fix. They closed it "resolved" without crediting the month. (I kept the packet captures.)

Dry week. At least the downtime gave me time to audit my BGP sessions. Anyone else had to parent their own provider through basic layer-3 troubleshooting? I used https://bgp.he.net to verify the path.

#2

Oh wow, debran_dad very impressive you fix like a professional engineer very much

1. Hetzner not good support
2. You should get credit at least
3. Maybe they offer you job wahahaha

I have similar problem with GreenCloudVPS before, they take two day to fix simple routing. I do not understand why NOC so slow very much.

You consider change provider

#3

Hetzner Singapore scrubbing center: 400 Gbps capacity, anycast from 3 PoPs. Routing loops at edge suggest their filtering layer (likely L3 ACL-based, not flowspec) failed over incorrectly. VRRP misconfiguration indicates lack of automated config validation.

I've seen similar from budget providers running their own hardware without out-of-band management. 15-minute detection SLA becomes 3-hour reality.

mitigated 800Gbps before breakfast
#4

Dadlime, you are very smart bro. Made ticket with RackNerd last month, they fix in ten minute. Maybe you try them next time thank you very much.

Hetzner no good for serious project, I think.

traffic worse than my packet loss
#5

They closed it without crediting you? That's Hetzner for you

#6

Which looking glass did you test through, their own or external

#7

I had the same thing with GreenCloudVPS, two days no fix

8-char NTLM found in 4min 32sec

Post a reply

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

Post reply Preview Save draft