Emergency

Questions about service interruptions, outages and incident reporting.

Questions

What should I do if a service seems unreachable?
What if the emergency is a hacked website?
What should I do if my dedicated server is unreachable?

What should I do if a service seems unreachable?

Temporary interruptions can come from local access problems, routing issues, maintenance or server incidents.

First checks

Before contacting support, try to determine whether the issue is local or external:

test from another connection
test from another device
reload DNS if relevant
run ping or traceroute if possible

A local access issue can look very similar to a server outage.

Monitoring

all2all monitors critical infrastructure continuously. Technical alerts are generated automatically when important services fail, often before users report the incident.

Contacting support

If the service still appears unreachable, contact support with:

affected domain or server
affected service (web, mail, DNS, SSH, etc.)
approximate start time
observed error message
ping, traceroute, mail error or browser error if available

Precise symptoms usually allow faster diagnosis than a general outage report.

Major incidents

When a wider outage or maintenance event is already identified, information may be published through the usual all2all communication channels.

What if the emergency is a hacked website?

If the service is reachable but the website redirects visitors, sends spam, shows phishing pages or contains suspicious files, treat it as a compromised website rather than as a general outage.

Contact support quickly and avoid deleting files before a first assessment has been made. We may need to place the site in protective mode, preserve a snapshot or inspect logs before cleanup.

What should I do if my dedicated server is unreachable?

Dedicated servers require a distinction between full server outage, network reachability, individual service failure and overload.

First checks

Try to determine whether:

the full server is unreachable
only one service is unavailable (web, mail, SSH, database)
the server still replies to ping
traceroute reaches the datacenter

A machine can be powered and reachable while one service has failed, or while load makes logins impossible.

Managed dedicated servers

If the server is managed by all2all, we perform an initial diagnosis, may attempt reboot procedures, analyse suspected hardware faults and apply emergency contract procedures where relevant.

If hardware intervention is needed, on-site datacenter action may be required.

Colocated servers

For colocated systems, available options depend on hardware and setup:

remote power control via switched PDU
serial console access when connected
IPMI or hardware management interface
remote hands intervention on request

IPMI can allow remote reboot, BIOS access and hardware diagnosis without physical intervention.

Before forcing a reboot

A remote reboot should only be done after excluding temporary overload, a blocked service, firewall misconfiguration or a stalled application. A hard reboot on a loaded production system may complicate recovery.

Useful information

When contacting support, include:

server name
IP address
traceroute output
last known access time
recent technical changes

If credentials must exceptionally be sent for emergency intervention, use encrypted communication.

For self-managed dedicated servers, local service monitoring remains strongly recommended. Typical tools include Webmin monitoring, service watchdogs and Nagios-compatible checks.