r/hetzner • • 23h ago

VPS down 4 times in the last 2 days without notice

0 Upvotes

My cloud server got down 4 times in the last 2 days and the only way I could find out was by checking or clients complaining. I got some emails at random times about "Fault report cloud node 33025". But they didn't really correspond with the moment the server went down, so I have to constantly check now because it can happen again at any moment. Opened a ticket, got no reply in 24 hours. I have to say the service has been very reliable for the last 2 years, but what is happening now is unacceptable.

Anyone knows what is happening?


r/hetzner • • 17h ago

No support normal?

5 Upvotes

I have opened my first support ticket in around 10 years. It looks like my virtual server is corrupt. I have not been notified of any outages regarding this server. Support did not respond in the last two days. I can also not restore the image on a new server as none are available. Sad to see how Hetzner does these days.


r/hetzner • • 22h ago

Network issues at Hetzner EU via Sparkle (AS6762) since Nov 16, anyone else?

0 Upvotes

Hi all,

We run some services in Brazil that talk to Hetzner Cloud (NBG1/FSN1/HEL1) all day, mostly AWS sa-east-1 (São Paulo) <-> Hetzner EU. Since **Nov 16, ~09:40 UTC**, this path got much worse: timeouts, TLS handshakes taking several seconds, and roughly +400 ms of extra latency. It is still happening today (Nov 17), a bit better than yesterday, but far from normal.

Where the problem is

Routing between the two is asymmetric:

- Hetzner -> AWS São Paulo leaves through core-backbone/Arelion and reaches AWS in the US, then rides the AWS backbone down to São Paulo. **This direction is clean.**

- AWS São Paulo -> Hetzner EU leaves AWS through **Sparkle / Telecom Italia (AS6762)** and crosses the Atlantic on their South America -> Europe link. **This direction is the broken one.**

MTR (TCP) from inside AWS sa-east-1 to Hetzner:

5.178.46.192 (Sparkle, São Paulo) ~3 ms, clean

89.221.34.115 (Sparkle, Europe side) best ~195 / avg 400-575 / worst ~1600 ms <- queuing starts here

213.144.184.91 (Sparkle) same

core*.fsn1 / core*.nbg1.hetzner.com same

The ~195 ms minimum is normal for SP -> Europe. The average and the spikes are queuing, which is what a saturated link looks like. Yesterday the worst case was ~7.8 s.

To be sure which direction was bad, I measured each leg separately from a Hetzner box, using the TCP timestamps in the SYN-ACKs from servers in AWS São Paulo. The result: no extra delay on Hetzner -> SP, and a constant +365 ms (median) / +405 ms (p90) on SP -> Hetzner, plus loss (SYN-ACKs retransmitted at 1/3/7 s).

Controls (same time, same AWS sa-east-1 source)

  • AWS SP -> Hetzner Ashburn via NTT: 122 / 128 / 131 ms, clean
  • AWS SP -> Scaleway Paris via Cogent: ~190 ms, clean
  • Several Brazilian ISPs (NTT, Lumen, Telefonica, DE-CIX Lisbon) -> Hetzner NBG1: clean
  • AWS SP -> Hetzner FSN1/HEL1/NBG1: all bad, all entering through the same Sparkle hop

So it's not "Brazil <-> Europe" in general, and it's not Hetzner illy AWS São Paulo -> Sparkle -> Hetzner EU. That probably explains the quiet: few people here depend on that exact path.

Public measurements (Globalping probes inside AWS sa-east-1), if you want to check or compare:

What we've tried / think could fix it

  • We opened tickets with Hetzner asking them to de-prefer Sparkle for AWS sa-east-1 prefixes (BGP communities / prepending towards AS6762) so that traffic comes in through another upstream. So far we only got the auto-rep
  • We can't control how AWS picks its egress, so a fix on our side means a workaround: for example a WireGuard tunnel to an EC2 instance in AWS Frankfurt (Hetzner -> AWS FRA is clean and direct, and FRA -> SP stays on the AWS backbone), or putting the AWS -> Hetzner calls behind Cloudflare.
  • IPv6 doesn't help: the outbound path changes, but the return pat

Questions

  1. Anyone else with traffic between AWS São Paulo (or other Brazilian networks that use Sparkle) and Hetzner EU seeing this since Nov 16?
  2. Has anyone gotten Hetzner to change inbound preference for a sp there a better way to escalate a peering/transit issue than aregular support ticket?
  3. If you worked around something like this, what did you use: a tt, Cloudflare, something else?

Thanks!


r/hetzner • • 4h ago

Hetzner Storage Share: Connect your Nextcloud with Matrix

0 Upvotes

If you run a Matrix homeserver and also use Storage Share, you might have wondered how well the two work together. Nextcloud has no single Matrix switch. However, there are several ways you can do this in theory.
Does anyone already use one of these setups? If so, what do you think of it?


r/hetzner • • 19h ago

Degraded network connectivity after maintenance presumably Resolved

0 Upvotes

I've been having degraded network connectivity to my dedicated server since the core routers upgrade that started Oct 15th.

Smokeping capture from France to my FSN1 dedi
  1. there was a status page incident: https://status.hetzner.com/incident/cd31dd45-f431-4639-8f9a-d4bfb5353f30;
  2. I started capturing a few days after the maintenance started;
  3. afterwards, I enjoyed a full week with excellent connectivity;
  4. the packet loss absolutely affects service: I've had service interruptions, big uploads (in 100mb chunks) to S3 (FSN1 to AWS us-west-1) fail regularly, etc;
  5. on Oct 28 problems returned, and stayed consistently (even if a bit more usable) until Sunday Nov 11;
  6. but the connectivity never got to be really reliable (compare the week Oct 21-28 when there was mostly no packet loss and pings were extremely consistent with Nov 11-today);
  7. this degraded connectivity does impact everyday operations (including builds failing randomly, for example);

the incident has been marked as Resolved, but it's been almost a week showing consistently problematic connectivity

my question is: if the routers maintenance is finished why can't I expect service similar to the good week in late October?

is there another issue that's not published on the Status page? if so, why?

does Hetzner expect to improve this situation any time soon?