Before you buy,
ask the useful questions.

Not always. Loss, jitter, peak-hour routing, bandwidth and application caching all matter. Check latency, route and loss together before you buy.

Find the relevant test IP or Looking Glass on the DMIT site, then test from your real carrier at typical hours. Test results are observations, not permanent guarantees.

Per official docs, every instance gets a default /64 IPv6 prefix, viewable in the control panel. A very few legacy instances may lack IPv6; you can open a ticket and DMIT will assign one. When you serve traffic by IP, watch both the IPv4 and IPv6 egress paths.

No. They are guide bands for narrowing the search. Products, stock, promotions and prices can change, so use the current official page as the source of truth.

A light site can start with a 1–2 vCPU and 1–4 GB target. With a database, cache or higher concurrency, use 2–4 vCPU and 4–8 GB as a comparison baseline, then adjust from measured load.

Measure the bottleneck first. Databases, cache and builds often need memory; high-concurrency compute, compiling or request handling may need CPU. Let monitoring decide.

The official Pricing page lists plans at monthly rates. Billing cycles and renewals follow the official checkout and invoice pages; whether longer cycles are offered is up to the official site.

Invoice or receipt types follow what the official Billing page actually offers. Cross-border services usually provide electronic receipts — confirm the document type and billing header before ordering if you need reimbursement.

Some plans support in-place changes from the control panel; scope and proration follow the official panel. Where a plan cannot be changed directly, the common path is buying the target plan and migrating per the migration guide.

Under section 19 of the official Terms of Service: new orders within 3 days and under 30GB of transfer qualify for a full refund (minus the payment-gateway fee); within 30 days you can request a partial refund based on remaining service time or remaining transfer. See the official docs at docs.dmit.io.

The official terms state that refunds deduct the transaction fee charged by the payment gateway. Refunds can go back to account credit or the original payment method; settlement time and fees follow the official docs and refund flow.

Section 19.3 of the official terms lists non-refundable cases, including renewal invoices, payments made with account credit, three prior refunds on the same product series, DDoS-targeted services, claims of poor network or IP geolocation, losses from abuse, and disputes raised in violation of the TOS. The full list is governed by the official Terms of Service.

Not by itself. Instance failure, deletion, account issues or regional events can affect it. Keep off-site or separate-media copies and rehearse restoration for critical data.

Prepare a full backup and rollback plan, then check ports, DNS TTL, certificates, environment variables, persistent paths and monitoring. Keep the old instance during an observation window.

This page does not add a fee when you use the referral link. A purchase may earn the referrer a commission; DMIT controls product pricing and policy.

Overage handling (throttling or suspension) follows the official plan page and terms. For traffic-sensitive workloads, compare per-GB unit prices across series and keep a 20–30% buffer.

IP changes are requested via support ticket; fees and limits follow the official reply. If the goal is fixing access from a specific region, validate routes with the official test IPs before buying.

No. This is an independent bilingual buying guide. All terms, prices, stock, support and service commitments are governed by the official DMIT website.

Chinese and English versions live at different URLs: /zh/ serves Chinese and /en/ serves English. The version you visit is the language you see.

Establish a performance baseline, then tune by layer: system (kernel params), Nginx (worker/gzip/cache), database (buffer pool/connections) and application (multi-core). See Performance Tuning Guide.

Use SSH key authentication, disable passwords, change the default port, disable root login, configure a firewall and install fail2ban. Full steps in SSH Hardening.

Yes. DMIT supports Docker and Docker Compose for containerised web apps, databases and more. Setup in Docker Deployment Guide.

Check if the backend service is running (systemctl status), the port is listening (ss -tlnp), and Nginx error logs (tail /var/log/nginx/error.log). Full troubleshooting in Troubleshooting Guide.

Choose the right network series (Tier 1 if no China routing needed), monitor and downgrade if underutilised, consolidate light services, use swap for occasional peaks. See Cost Optimisation.

Plan 3 days ahead: buy & configure → 2 days before, migrate data → 1 day before, verify → migration day, DNS cutover. Keep the old server for 1 week as fallback. See Migration Guide.