Routing to VNPT, Viettel and FPT: what domestic peering actually changes

When you rent a VPS in Vietnam, you are not just choosing a datacenter location. You are also choosing which local internet service provider (ISP) the IP address belongs to. In Vietnam, the three dominant carriers, VNPT, Viettel, and FPT Telecom, each maintain their own backbone and their own peering policies at the domestic Internet exchange point, VNIX. This creates a distinct latency profile depending on whether your traffic stays within the same ISP or crosses to another carrier.

VNPT、Viettel、FPT之间的境内互联决定越南用户的实际体验。

Domestic peering between VNPT, Viettel and FPT decides what your Vietnamese users actually experience.

If you serve users inside Vietnam, the ISP your VPS sits on can make the difference between a 3 ms ping and a 45 ms ping. This post explains who these carriers are, how domestic peering works under the hood, and what it actually changes for your application.

Who Are VNPT, Viettel, and FPT Telecom?

These three companies are the backbone of Vietnam's internet. Between them, they control approximately 80, 90% of the country's fixed broadband and mobile data market. Understanding each one helps you make an informed decision when you select a VPS provider or a dedicated server in Vietnam.

VNPT (Vietnam Posts and Telecommunications Group)

VNPT is the state-owned incumbent, formerly the national telecom monopoly. It operates under the brand "VNPT Vinaphone" for its fixed and mobile services. VNPT has the widest physical reach, its fiber network extends into the most rural provinces. Many older government and enterprise systems are on VNPT lines. For datacenters, VNPT operates Tier 3 facilities in Hanoi and Ho Chi Minh City, including the Viettel IDC (which it partially shares via cross-connect).

VNPT's peering at VNIX tends to be the most neutral; it exchanges traffic with both Viettel and FPT. However, intra-ISP traffic (VNPT-to-VNPT) is generally faster than cross-carrier routes because it stays entirely on VNPT's backbone without touching the exchange.

Viettel (Viettel Group)

Viettel is the largest military-run telecom operator in Vietnam and the country's biggest ISP by subscriber count. It owns its own international cable systems (AAE-1, APG, etc.) and domestic fiber backbone. Viettel's datacenters are among the most connected in the country, and it operates its own cloud platform. Its domestic peering behavior is aggressive: Viettel often prefers to keep traffic within its own network rather than exchange at VNIX, which can create latency for users on other ISPs.

FPT Telecom

FPT Telecom is part of the FPT Corporation, the largest private technology conglomerate in Vietnam. FPT has the most aggressive consumer broadband pricing and the fastest reported international transit capacity per subscriber. Its domestic peering posture is similar to Viettel's: intra-ISP performance is excellent, but cross-carrier traffic may pass through the VNIX exchange with noticeable latency.

These three ISPs maintain their own autonomous system numbers (ASNs) and do not fully mesh peers. The VNIX exchange, where they interconnect, is the common bottleneck.

The Domestic Exchange: VNIX

VNIX (Vietnam National Internet Exchange) is the country's only public Layer 2 IXP. It is operated by the Vietnam Internet Network Information Center (VNNIC). Every major ISP must connect at VNIX to exchange domestic traffic. However, the arrangement is not a full mesh. Each carrier maintains its own routers at one or two VNIX points (Hanoi and Ho Chi Minh City), and they only exchange routes they choose.

What this means in practice: a packet leaving a VPS on a Viettel IP and destined for an end-user on FPT broadband has to exit Viettel's infrastructure, enter the VNIX switch, and then be picked up by FPT. Each hop adds latency. In many cases, the latency of this crossing is 10 to 40 ms, compared to 0.5 to 3 ms for intra-ISP traffic.

For applications where every millisecond matters, real-time collaboration, VOIP, online gaming, or database replication, you must consider this cost.

Cross-Carrier Routing: What Actually Changes

Let's run a concrete scenario. You have a web application served from a VPS that has a Viettel IP address. Your user is on a home broadband connection that also belongs to Viettel. The packet leaves your VPS, hits the Viettel gateway, stays within Viettel's ASN, and reaches the user at roughly 3 to 5 ms RTT within Ho Chi Minh City.

Now the same user switches to an FPT home connection. The packet leaves your Viettel VPS, is routed to the VNIX exchange (usually in Ho Chi Minh City), traverses the peering port, enters FPT's network, and reaches the user. This crossing adds 15 to 40 ms, depending on the exchange load and the distance between the VNIX point and the user's residential DSLAM.

What changes in practice:

• Latency: Cross-carrier RTT can be 5, 10× higher than intra-ISP.
• Jitter: More variable because the VNIX port is shared among many subscribers.
• Packet loss: Can increase during peak hours (7 PM, 11 PM local time) as the exchange port saturates.
• Routing asymmetry: In some cases, the forward path goes through VNIX but the return path is direct, or both paths go through different exchange points.

If your application handles database queries, API calls, or video streaming to a mixed audience of Vietnamese users on different ISPs, you will feel this asymmetry directly in your error budget.

The VNIX Bottleneck

VNIX has a total switching capacity that is modest compared to major global IXPs. In early 2026, VNIX in Ho Chi Minh City operates at roughly 80 Gbit/s peak while the Hanoi node is smaller. With three large ISPs connecting their entire user bases through this exchange, the ports are often congested during evening hours.

Because each carrier only buys enough peering bandwidth to handle average traffic, cross-carrier traffic can suffer during spikes. This is not a failure, it is an intentional design choice to keep peering costs minimal. For your VPS, it means that if you serve a user on a different carrier during peak time, you may see higher latency or brief packet drops.

There is no way to force an ISP to upgrade its peering port. The only mitigations are to either host your VPS on the same ISP as your majority user base, or use a CDN that has edge points inside each of the three carriers.

How to Mitigate Cross-Carrier Latency

If you cannot control which ISP your VPS uses (because the datacenter assigns you a specific block), you have a few workable options:

• Use a reverse proxy with multiple IPs: Rent an additional IP address from a second carrier and set up anycast or DNS-based routing. This is complex but common for large deployments.
• Deploy a CDN: Services like Cloudflare, BunnyCDN, or Viettel's own CDN can absorb the cross-carrier hop. The CDN node sits within each carrier's network, so the user always talks to a node on their own ISP.
• Choose a VPS with carrier-aware routing: Some providers, like thueVPS, offer IP addresses from specific carrier blocks (VNPT, Viettel, or FPT) depending on the datacenter location. Knowing your audience's ISP lets you pick the right block.

For small to medium applications, the CDN approach is simplest to implement and does not require architectural changes to your backend.

When It Matters Most

Cross-carrier routing is not a problem for every workload. If your application serves content that is heavily cached, or if your users are primarily on international connections, the domestic peering effect is minimal. The delay of crossing VNIX is still less than the delay of a transpacific round trip.

It matters most when:

• Your users are overwhelmingly Vietnamese residential broadband subscribers (who are split across VNPT, Viettel, and FPT).
• Your application requires real-time interactivity (chat, collaboration tools, gaming, live streaming).
• You run latency-sensitive database replicas between datacenters in Hanoi and Ho Chi Minh City (cross-DC traffic often crosses carriers).

If your budget allows, test from each carrier before committing. A simple ping and mtr from a Viettel, VNPT, and FPT connection to your VPS IP will tell you everything you need to know about the latency cost.

Practical Test: Check Your VPS ISP

You do not need to guess which carrier your VPS IP belongs to. Run a quick WHOIS lookup:

whois 103.141.x.x | grep -i 'descr\|org\|netname'

If your VPS provider gives you a Viettel block (AS7552), your intra-Viettel users will see <5 ms latency. Users on FPT or VNPT will see 15 to 40 ms.

If your VPS is on an FPT block, the same inversion applies: FPT users get the low latency, others pay the crossing cost.

If your VPS sits on a VNPT block, you are on the most neutral carrier: VNPT peers actively at VNIX, so cross-carrier latency is usually lower than the other two. However, VNPT's own domestic routing can sometimes be less predictable at the edge.

Summary: What to Choose

For a general-purpose VPS serving a mixed Vietnamese audience, a VNPT IP address is often the safest default because of its better peering posture. If you know your user base is dominated by one ISP (e.g., an e-commerce site serving mostly Viettel mobile users), choose the matching carrier block.

If you are running a latency-critical service (VPN, gaming, real-time API), you should strongly consider deploying a CDN or using multiple IPs from different carriers. The cost of the cross-carrier hop is not a theoretical concern, it is a measurable 20 ms penalty that accumulates with every network round trip.

When evaluating VPS pricing, factor in the ISP of the IP address, not just the hardware specification. A 4-core VPS on the wrong carrier will feel slower to your users than a 2-core VPS on the right one.

FAQ

Related articles

• Vietnam VPS vs Singapore VPS for serving Vietnamese users
• Why a Vietnam IPv4 matters when your users are in Vietnam
• 10 cheap VPS Vietnam: must-read before buying (2026 guide)