Emergency Linux Support When Production Is Down
A production outage is a bad moment to start comparing agencies. The useful question is narrower: can someone competent get on the box, find the failing service, and restore the site without making the damage worse?
Emergency Linux support is for that window. It covers a server that is offline, a website that will not answer, a database that has crashed, a mail system that has stopped delivering, a filesystem that is full, an extreme load spike, a failed update, or a host that looks compromised.
What this is, and what it is not
Response is best-effort and depends on an engineer being available. It is not an automated 24/7 SLA. The rate is €95 per hour in standard emergency windows and €125 per hour after hours and on holidays, excluding VAT where it applies. Confirm the current rate on the pricing page before you send the request.
What to send before anyone logs in
- Provider, server IP or hostname, and whether console access still works
- What stopped, and when
- The last change, update or deploy
- Any error from the browser, mail client or panel
- Whether the problem is the site, the database, mail, or the whole machine
Do not restart everything in sequence before anyone looks at the logs. A reboot can clear the evidence and, on a full disk or a half-applied update, can leave the machine unable to boot. Console access from the provider panel is often the difference between a remote fix and a reinstall.
If the server looks compromised
The first goal is containment: stop the obvious process, preserve logs, rotate exposed credentials, then recover. Cleanup without that sequence tends to miss the persistence mechanism. A later security review is the right follow-up once the service is back.
Service page: Emergency Linux support
Tell us the provider, distribution and what is broken before any work starts. Request support or email help@direktsupport.eu.