Hetzner support is generally reachable and often competent, but the experience varies sharply depending on the issue and the product line. Most routine problems meet fast, knowledgeable help; account verification and fraud checks are where the support relationship is most likely to become slow or adversarial. Your decision should therefore hinge less on "is support good?" and more on whether your workload and risk tolerance match what Hetzner's channels and terms actually deliver.
Support Channels and Hours at a Glance
Hetzner routes support through several paths rather than a single front door. Its support center offers a question-answering tool, an official forum, documentation, a status page, downloads, and telephone support. A support chat handles questions about its products and services.
Phone availability depends on the product:
- The general customer service line, +49 (0)9831 505-0, runs Monday to Friday, 8am to 6pm CET, for Web & Managed, Sales, Billing and Cloud requests.
- Data center technical lines covering dedicated servers and colocation in Nuremberg, Falkenstein and Helsinki run 24 hours a day, with the Helsinki line in English.
- Data center telephone support requires an activated telephone password or one-time password on dedicated servers.
- Ticket support for cloud products is available around the clock, 24/7/365.
That split matters for planning. Someone running cloud infrastructure cannot rely on a general phone line outside Central European business hours, but they can file a cloud ticket at any time. Someone with a dedicated server at a Hetzner data center has a genuine 24-hour phone escalation path, provided the telephone password is set up in advance.
What Users Praise
The most commonly reported positive is speed on straightforward technical issues. A LowEndTalk forum participant said their Hetzner ticket was resolved in less than an hour. That is a single anecdote, not a measured average, but it shows the fast end of what users report.
Competence on infrastructure questions is the second recurring theme. Hetzner's own documentation supports this to some degree: the company publishes 350+ tutorials with step-by-step instructions for common problems, and 24/7 cloud ticket coverage means a submitted request is at least queued immediately. Long-term customers who know their way around servers tend to get the most out of these channels, since they can describe a fault precisely and often resolve it themselves via documentation.
What Users Criticise
The criticism clusters around urgency and account issues rather than everyday technical help.
A DEV Community review described Hetzner support as slow for urgent issues, arguing that a 4-hour response time feels long if a production server is down at 3am, and suggested enterprise users look elsewhere. A Trustpilot reviewer reported waiting more than a month for an issue to be resolved and spending money on international phone calls without a resolution, concluding they could not recommend Hetzner to anyone who values responsive support.
These are self-selected, unverified accounts, and they contradict the fast-resolution anecdote. No supplied source provides a verified average or guaranteed ticket response time, and Hetzner's terms stop short of a meaningful service-level commitment: they state only that Hetzner will use commercially reasonable efforts to attempt to provide services 24 hours a day, seven days a week. Read that wording carefully. It is an effort commitment, not a response-time guarantee.
Self-Service Resources Worth Trying First
A large share of support contacts can be avoided entirely, which changes the practical value of response times.
The status page publishes planned maintenance and current fault reports for Hetzner products and services. If something is broken, check it before opening a ticket; it may already be a known incident, such as a resolved cloud resource creation delay or resolved fault reports for the Cloud DNS and reverse DNS APIs. Customers can also log into their administration interfaces to receive email notifications about status reports affecting specific products.
The documentation library and the 350+ tutorials cover common setup and troubleshooting tasks. For billing confusion, the FAQ answers many questions directly: most products renew automatically and are billed as long as they exist, even if powered off or idle, and Cloud servers must be deleted to stop charges. Annual or semi-annual billing is not possible; products are billed monthly, with many Cloud resources charged hourly within that monthly invoice. Because the status page has also carried a general notice about phishing emails stealing logins and credit card data, treat unexpected account messages with suspicion and verify through the official interfaces rather than reply to them.
Account Verification, Terms Enforcement and Risk
This is where Hetzner support most often disappoints, and where the terms matter more than the help desk's manner.
Hetzner uses one-time passwords as an extra security step when an account is accessed from a new device or unusual location. It limits how many Cloud resources each account can create to prevent abuse, and limit increase requests are processed manually during business hours, so they can take time. Hetzner explicitly advises customers with questions about an open limit request to reply to the ticket rather than call support. If you are waiting on a limit increase, phoning will not accelerate it.
The contractual picture is stricter than many customers expect:
- Hetzner may accept or reject an order within 5 working days of receiving it, and confirming receipt does not bind it to accept the order.
- It reserves the right to terminate the contractual relationship without notice for good cause, including payment failures or violations of important customer obligations.
- It may lock or terminate services or an account without notice if customer content impairs infrastructure operation or security, or violates specified terms paragraphs.
- Customers must provide correct and complete account data, notify changes in writing within no more than 14 days, and supply evidence of correctness on request.
- Transfer requests must be made in writing, and Hetzner is obligated to verify the legitimacy of the transferor and the identity of the third party.
Two further clauses shape what a support conversation can achieve. Employees and commissioned third parties are not authorized to make verbal agreements or provide verbal guarantees or commitments. And Hetzner reserves the right to change its terms, system policies and prices with prior notification via the customer account or the email address on file. In practice, a reassuring sentence from a support agent is not a contractual promise, and the notification channel in your account is the one that counts.
For customers who leave voluntarily, either party may terminate with 30 days' notice to the end of the month without giving reasons, subject to differing notice periods in individual service descriptions.
Practical Steps for a Faster Support Outcome
- Check the status page before contacting anyone; known incidents need no ticket.
- Search the documentation and tutorials first, since many common problems are already documented step by step.
- For cloud problems outside Central European business hours, file a ticket rather than calling the general line.
- If you run dedicated servers, activate the telephone password now, before you need the 24-hour data center line.
- Reply to open limit requests in the ticket instead of calling; Hetzner asks for this directly.
- Keep account data accurate and report changes in writing within the stated window to avoid verification friction later.
- Confirm billing assumptions in the FAQ before disputing a charge, particularly that powered-off Cloud servers still bill until deleted.
- Get any consequential commitment in writing, since verbal assurances are not authorized.
Who Hetzner Support Fits Best
Hetzner support fits developers and small teams who are comfortable with self-service documentation, mainly need help with cloud or dedicated infrastructure, and can absorb variable response times. That reader gets multiple official channels, round-the-clock cloud ticket coverage, 24-hour data center phone lines, and unusually extensive documentation and status reporting.
It fits less well in three situations. Businesses that need contractual response-time guarantees for production incidents will find only an effort commitment and anecdotal complaints about urgent-issue delays. Anyone whose account history includes verification difficulties, payment problems, or content that could be read as impairing infrastructure should weigh the without-notice termination clauses carefully. And anyone who values a fast, sympathetic resolution over a month-long dispute should take the Trustpilot complaint pattern seriously, even while treating it as a single unverified account.
Verdict
There is no overall winner to declare here, because the evidence is a mix of official policy and contradictory anecdotes rather than a comparable metric measured across channels. The honest verdict is conditional.
Choose Hetzner if you are technically self-sufficient, keep your account details accurate and your payment method current, and treat support as a backup to good documentation and a status page rather than a guaranteed safety net. Look elsewhere if your workload cannot tolerate unguaranteed response times during urgent incidents, or if the possibility of a without-notice account lock over billing or content issues is unacceptable to your business. For everyone in between, the channels are real, the documentation is substantial, and setting up the telephone password and ticket habits described above is the most reliable way to get a good outcome when you need help.


