Status
Service status
If a service fails, check client-area notices, create a ticket for the affected service, and attach the event time, IP, MTR, or relevant logs.
Client-area notices
Service ticket
MTR and trace
Logs and time
Client areaservice notices
Ticketaccount-linked diagnostics
MTRroute and packet loss
Logsexact event time
Tickets and requests24/7
Tickets and ordersClient area
VPS · Servers · IPone stack
Procedure
Where to check and what to attach
Client-area notices
Check notices for your service, including planned work, network changes, and known events.
Client area
Service ticket
Include the service ID, affected IP, start time, and checks already completed so the request has the right context.
Service ID
Network diagnostics
For network issues, attach MTR or traceroute in both directions, source and destination, protocol, and port.
MTR / trace
Logs and time
For a VPS, server, or application issue, include the time zone, exact time, symptoms, and a log excerpt without passwords or keys.
Create ticketComponents
What to check during an incident
| Component | What to check | Next action |
|---|---|---|
| Location | whether the target site has a notice | check client-area notifications |
| Network | route, port, DDoS filtering | open a ticket with MTR/trace |
| Server | power, IPMI, disk, RAM | attach logs and event time |
| Application | CPU/RAM/IO and service logs | add managed support if needed |