SUBNET.IM

42.116.0.0/16

FPT Telecom CompanyAS18403

At a glance

Addresses

65,536

/16 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICVN

Allocated 10th February 2011

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 42.116.0.0/16 as seen from Singapore, read outward from the origin: AS18403 → AS132337. Each hop is listed with its network name beneath the graph.AS18403FPT Telecom Compa…OriginAS132337Axclusive

Seen from Singapore

  1. 1AS18403FPT Telecom CompanyVNOrigin
    Peer of AS18403seen on 9,629 paths from 2 vantage points
  2. 2AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Singapore18403132337Shown above
  2. London, UK1840312998529This path
  3. Sao Paulo184033356266213This path
  4. Oregon, US18403693920130This path
  5. Amsterdam18403129934549213151This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
Vietnam
Allocated
10th February 2011
Allocation block
42.112.0.0/13
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 42.116.0.0/16
ROA prefixAuthorised originMax length
42.112.0.0/13AS18403/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 42.116.0.0/16: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.42.112.0.0/13AS1840342.116.0.0/16AS18403This prefix42.117.0.0/16AS1840342.116.0.0/18AS1840342.116.64.0/18AS1840342.116.128.0/18AS1840342.116.192.0/18AS1840342.116.0.0/20AS18403+19 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 42.116.0.0/16
PrefixAddressesOriginVisibility
42.112.0.0/13524kAS18403FPT Telecom Company79/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 42.116.0.0/16
PrefixAddressesOriginVisibility
42.117.0.0/1665.5kAS18403FPT Telecom Company80/80

History

  1. AS1840312th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 42.116.0.0/16 in the calculator/16 reference

Routing data derived from RouteViews MRT archives and public registry data.