IPv4 addresses and subnets
IPv4 subnet lease from /24 to /18, LIR services, RDNS, GRE, ACL, and movable address resources.
IPv4 addresses and subnets
LIR services
ROA/RPKI
ROA preparation, origin ASN checks, and baseline routing data for IPv4 prefix announcements.
Open ticketRoute objects
Creation and review of route objects, maintainer data, and announcement coordination.
Open ticketLOA and BGP
Announcement documents, LOA on request, ASN binding, and upstream data preparation.
Open ticketAbuse and documents
Block history review, abuse contacts, basic paperwork, and network request support.
Open ticketIPv4 tariffs in billing
What you can build
Public services
RDNS and anti-DDoS for websites, APIs, VPN/proxy, and mail components.
GRE and L2
Tunnels for connecting locations, traffic transfer, and integration with your network design.
Anycast on request
Useful for DNS, edge services, and distributed network logic.
Monitoring
Graphs, alerts, and event control help detect traffic anomalies quickly.
What to verify before ordering
Test IP and speedtest
For a location, request a test IP, speedtest file, and route check to your region before payment.
Request testDDoS and filtering
Before ordering, clarify the traffic profile: TCP/UDP, game ports, VPN/proxy, L3/L4, and application needs.
Network termsASN, BGP, ROA
For IPv4/BGP tasks, we verify origin ASN, ROA/RPKI, route objects, LOA, and abuse contacts.
IPv4 subnetsTraffic and port
Plans show port and traffic terms clearly: unmetered VPS traffic or a stated server traffic package.
View serversLegal, billing, and support
Documents before payment
Request an invoice, company details, offer terms, and renewal rules before ordering if accounting needs them.
Billing termsPayments and invoices
Orders, invoices, tickets, and service history are managed through the client area; commercial questions go to sales.
ContactsAbuse and allowed use
For torrents, VPN/proxy, blockchain nodes, mail, BGP, and IP pools, abuse conditions and documents are agreed in advance.
Abuse policyEscalation
Critical incidents are handled through tickets with priority, service linkage, and clear response time.
SLALong-term IP lease
Can the price be fixed for 6-12 months?
Yes. Monthly payment is available by default, and 6-12 month prepayment, discounts, and price-lock terms can be agreed in an invoice or ticket.
What happens if hardware fails?
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.
Can resources be upgraded without migration?
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.
Who is responsible for backups?
By default, the customer is responsible for application data. Controlled backup/restore is available as a separate option or managed service.
Can the network be checked before payment?
Yes. Request a test IP, speedtest, and route check for the target location. DDoS-sensitive workloads should describe protocols and traffic profile in advance.