Summary

The question that motivates this article is simple to state and harder to answer: why does a company whose product is other people's software run its own autonomous system at all? The answer visible in public routing and registry data is not a hidden ISP business. It is a small corporate network, plugged into Vietnam's two dominant carriers, that exists because of how address allocation and route publication work — and whose maintenance is largely delegated to the carriers themselves.

A network hidden in plain sight

AS131402 sits inside the APNIC 32-bit ASN block (AS131072–AS132095) administered in Vietnam through VNNIC, the Vietnamese national internet registry https://www.cidr-report.org/cgi-bin/as-report?as=AS131402&view=6447. Its aut-num object, named FPTSOFTWARE-AS-VN, carries the descriptive text "FPT Software Company limited, FPT Cau Giay Tower, Duy Tan, Dich Vong Hau, Cau Giay, Hanoi" and a country field of VN http://iad.robtex.com/as/AS131402.html. The record was last modified on 30 October 2019 — a date that matters later in this article, because so little about this network has changed since.

What has not changed in the registry has, however, been moving in the routing system continuously. Independent trackers — Hurricane Electric's bgp.he.net, BGP.Tools, CIDR Report, Qrator Radar and IPinfo — all show AS131402 actively originating IPv4 prefixes https://ipinfo.io/AS131402 https://bgp.he.net/AS131402 https://bgp.tools/as/131402 https://www.cidr-report.org/cgi-bin/as-report?as=AS131402&view=6447. The counts differ by one or two between trackers (nine originated versus eight announced on some), which is normal measurement variance for a network this small, but the substance is consistent: two /22 blocks, 103.71.180.0/22 and 103.227.216.0/22, announced both as aggregates and as /24 more-specifics https://bgp.he.net/AS131402 https://radar.qrator.net/as/131402/connectivity/prefixes. CIDR Report measures the announced footprint at roughly 3,584 addresses — about /20.19 — with eight total advertisements https://www.cidr-report.org/cgi-bin/as-report?as=AS131402&view=6447.

That is a very small network. For comparison, a mid-sized regional ISP announces orders of magnitude more address space. AS131402's footprint is the size of a large corporate campus plus a handful of sites: 2,048 addresses per /22 block, subdivided into /24s, with per-prefix descriptions naming "FPT Software Ha Noi" on the 103.71.180.x block and "FPT Software Company limited" on the 103.227.216.x block https://bgp.he.net/AS131402 https://ipgeolocation.io/browse/asn/AS131402.

The upstream structure tells the story

AS131402 does not peer directly with the world. Its two upstreams are AS18403 (FPT Telecom Company) and AS45899 (VNPT Corp) https://ipinfo.io/AS131402 https://bgp.tools/as/131402. Both are major Vietnamese carriers. One — FPT Telecom — sits inside the same corporate family as FPT Software, under the FPT Corporation group. The other is a national incumbent with no ownership relationship to FPT.

The dual-carrier design is textbook enterprise redundancy: two independent providers, so that a single carrier failure does not disconnect the company's routed addresses. This is the classic posture of an organisation that runs its own network for its own purposes and buys transit from whoever serves its offices best. It is not the posture of a service provider selling connectivity, which would typically need broader peering, an open peering policy visible in route registries, and customer cone growth over time. None of that is present: CIDR Report measures AS131402's transit business at zero https://www.cidr-report.org/cgi-bin/as-report?as=AS131402&view=6447.

The import/export policy recorded in the aut-num object is correspondingly minimal: accept ANY from AS7643 (VNPT) and AS18403 (FPT Telecom), and announce AS131402 to both http://iad.robtex.com/as/AS131402.html. Two provider relationships, no transit customers, no peering fabric membership recorded in the public registries inspected for this article.

Registry maintenance lives with the carriers

Here is where the record becomes genuinely informative about how Vietnam's number-resource ecosystem works in practice. The aut-num object belongs to FPT Software and is maintained under MAINT-VN-VNNIC, with administrative and technical contact handles registered in APNIC's database http://iad.robtex.com/as/AS131402.html https://radar.qrator.net/as/131402/whois. But the route objects — the statements that tell other operators these prefixes may legitimately be announced — are maintained by the carriers: 103.71.180.0/22 is registered under RADB with mnt-by MAINT-AS18403 (FPT Telecom), last modified 13 November 2023, and a 103.71.180.0/24 route object is maintained under MAINT-AS45899 (VNPT), last modified 31 December 2025 http://iad.robtex.com/as/AS131402.html.

The pattern repeats at the AS-set level. AS131402 appears as a member of AS-FPT (FPT Telecom's customer set), AS-VNPT, AS7643:AS-CUSTOMERS and AS-45899CUST http://iad.robtex.com/as/AS131402.html. The AS-45899 set — VNPT Net's customer list — was changed by VNPT's registry contact on 15 June 2026, and AS131402 is among its listed members https://ipv4.bgp.he.net/irr/as-set/AS-45899. In other words, the operational attestations that make this network routable are being kept current by the carriers that carry its traffic, while the company's own registry object has sat untouched since 2019.

This division of labour is common in markets where enterprise ASes are small and carrier relationships dominate: the upstream does the route registry work because it is the upstream's route filters that depend on it. It also means that an outside observer's picture of FPT Software's network posture is assembled as much from FPT Telecom's and VNPT's maintenance activity as from anything FPT Software itself has recorded.

Security posture: mostly valid, partly opaque

RPKI validation — cryptographic signing of route origin authorisations — is the current baseline expectation for originated space. On AS131402 the picture is good but not complete. CIDR Report records seven of the originated prefixes as RPKI-valid https://bgp.he.net/AS131402. Qrator Radar's prefix view shows route-object and ROA states marked valid for most prefixes, with some of the 103.71.180.x more-specifics showing unknown ROA status https://radar.qrator.net/as/131402/connectivity/prefixes.

There is also a visibility asymmetry worth noting. Qrator's propagation measurements show the 103.227.216.0/22 aggregate and its /24s propagating at essentially full visibility (around 446–448 of measured ASes), and 103.71.180.0/22 at 100% — but two of the 103.71.180.x /24s propagate at only about 1.28% (5 of measured ASes) https://radar.qrator.net/as/131402/connectivity/prefixes. More-specifics with near-zero visibility are usually either filtered upstream or announced only to a narrow set of neighbours; for an internal network, the aggregate /22 is what matters, and it is fully visible. This is a measurement footnote rather than a routing health problem, but it is exactly the kind of detail that distinguishes reading a routing table from understanding one.

One further operational signal: IPinfo's page records a live response measurement to an address inside the block (103.71.180.151) at roughly 9.78 ms from Hanoi https://ipinfo.io/AS131402. Latency figures from aggregator tooling should be treated as indicative rather than definitive, but they are consistent with an internally reachable network inside Vietnam rather than dark space.

What the network is for

Nothing in the public record indicates that AS131402 sells anything. It has no transit customers, no hosting or ISP service branding, and no market presence as a connectivity provider. What it has is: two /22 blocks registered to the company, prefix descriptions naming specific FPT Software locations in Hanoi, two carrier upstreams, and registry maintenance delegated to those carriers.

The most economical explanation is that this is FPT Software's internal corporate and campus network — the routed addresses of offices and development sites in and around Hanoi — published as an autonomous system because that is how the company's address space and multi-carrier connectivity are organised.

Why an autonomous system rather than address space inside FPT Telecom's own allocations? The practical reasons are ordinary ones: independent routing policy, direct control over announcements, multi-homing with failover between two carriers, and the administrative autonomy of holding your own ASN. The 2019 creation date of the aut-num object also fits a period when Vietnamese enterprises, supported by VNNIC's APNIC membership channel, increasingly took direct resource holdings.

But the deeper point for BTW's readers is structural: the number-resource layer records relationships — company-to-carrier, carrier-to-registry, registry-to-country — that never appear in company communications, and that can be read by anyone with a routing table.

The business context: an AI story without a network story

BTW's earlier coverage of FPT Software examined its AI-assisted delivery strategy https://btw.media/en/after-the-man-month-fpt-softwares-ai-accountability-test: the May 2026 launch of Flezi Foundry, an AI-augmented delivery platform built on the company's AI Factory infrastructure, combining autonomous agents with human oversight and outcome-based delivery https://fptsoftware.com/newsroom/news-and-press-releases/press-release/fpt-launches-flezi-foundry-advancing-ai-augmented-delivery-for-global-enterprises. Vietnamese business press reported FPT's AI and data-analytics revenue exceeding VND1.84 trillion (about USD 71 million) in the first half of 2026, up 54% year on year, alongside USD 1.02 billion in newly signed overseas IT services contracts https://theinvestor.vn/vietnam-tech-giant-fpts-ai-equation-from-selling-labor-to-selling-outcomes-d19983.html.

None of that business narrative touches AS131402. That absence is itself informative. FPT Software's growth story is about selling engineering capacity and outcomes; its network is not a product, not a selling point, and not part of the AI Factories being marketed. The autonomous system is plumbing.

Reading the two stories together — the high-growth AI delivery narrative and the static, carrier-maintained small network — gives a more complete picture of the company than either alone: a services organisation whose visible infrastructure ambition sits in compute and delivery platforms, while its own network layer is deliberately modest and outsourced in operation to the national carriers.

What would change the reading

This article's interpretation — internal infrastructure, not a service offering — rests on observable evidence and could be revised by observable evidence. Three signals would change it: first, sustained growth in announced prefixes or customer cone, which would suggest a services posture emerging; second, route-object maintenance migrating from the carriers back to a FPT Software-controlled maintainer, which would suggest the company taking direct operational control; third, any public commercial offering of connectivity or hosting under FPT Software branding using this space. None of these is present in the data as of late September 2026. The most recent registry activity tied to this network remains carrier-side: VNPT's June 2026 AS-set update and a VNNIC IRT object refresh in April 2026 http://iad.robtex.com/as/AS131402.html https://ipv4.bgp.he.net/irr/as-set/AS-45899.