Care
Basic operations for production VPS and small servers.
- Delivery
- same day
- 24/7 monitoring
- Security updates
- Response within 2 hours
Hostyrex engineers handle migrations, monitoring, updates, backups, security, and incident response.
Basic operations for production VPS and small servers.
Ongoing operations, migrations, and performance control.
Operations for critical services with faster SLA and DR planning.
We plan the move, test the environment, and switch services with minimal downtime.
We set up monitoring, alerts, baseline metrics, and clear incident response steps.
Updates, hardening, firewall, backup policies, and access control.
We inspect bottlenecks across storage, network, databases, and service configuration.
Request an invoice, company details, offer terms, and renewal rules before ordering if accounting needs them.
Billing termsOrders, invoices, tickets, and service history are managed through the client area; commercial questions go to sales.
ContactsFor torrents, VPN/proxy, blockchain nodes, mail, BGP, and IP pools, abuse conditions and documents are agreed in advance.
Abuse policyCritical incidents are handled through tickets with priority, service linkage, and clear response time.
SLAThe billing period depends on the plan: most services renew monthly, while selected plans have a minimum term. A 6–12 month prepayment, discount, or price lock applies only after confirmation in an invoice or ticket.
A ticket is opened, IPMI/SMART/logs are checked, then disk, RAM, node replacement, or migration is coordinated. Critical projects should use RAID, backup, and managed support from the start.
VPS upgrades are usually available by moving to a larger plan. Baremetal upgrades depend on chassis, slots, drives, and available hardware, so growth should be discussed before ordering.
By default, the customer is responsible for application data. Controlled backup/restore is available as a separate option or managed service.
Yes. Request a test IP, speedtest, and route check for the target location. DDoS-sensitive workloads should describe protocols and traffic profile in advance.