Single IP
Address for a VPS, server, mail component, or RDNS.
- Block
- 1 IPv4
- 1 IPv4
- Reverse DNS
- Anti-DDoS included
IPv4 subnet lease from /24 to /18, LIR services, RDNS, GRE, ACL, and movable address resources.
Address for a VPS, server, mail component, or RDNS.
Small address block for multiple services and separation.
Network package for tunnels, edge scenarios, and traffic control.
Subnet lease for BGP, servers, proxy, VPN, and infrastructure workloads.
Subnet lease for projects that need a dedicated address pool.
Subnet lease for services with multiple network segments.
Subnet lease for larger network projects and distributed infrastructure.
Subnet lease for larger address capacity and BGP announcement.
Subnet lease for provider, proxy, VPN, and BGP scenarios.
Subnet lease for large network projects with individual approval.
ROA preparation, origin ASN checks, and baseline routing data for IPv4 prefix announcements.
Open ticketCreation and review of route objects, maintainer data, and announcement coordination.
Open ticketAnnouncement documents, LOA on request, ASN binding, and upstream data preparation.
Open ticketBlock history review, abuse contacts, basic paperwork, and network request support.
Open ticketRDNS and anti-DDoS for websites, APIs, VPN/proxy, and mail components.
Tunnels for connecting locations, traffic transfer, and integration with your network design.
Useful for DNS, edge services, and distributed network logic.
Graphs, alerts, and event control help detect traffic anomalies quickly.
For a location, request a test IP, speedtest file, and route check to your region before payment.
Request testBefore ordering, clarify the traffic profile: TCP/UDP, game ports, VPN/proxy, L3/L4, and application needs.
Network termsFor IPv4/BGP tasks, we verify origin ASN, ROA/RPKI, route objects, LOA, and abuse contacts.
IPv4 subnetsPlans show port and traffic terms clearly: unmetered VPS traffic or a stated server traffic package.
View serversRequest 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.