SUBNET.IM

1.54.60.0/23

FPT Telecom CompanyAS18403

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICVN

Allocated 26th May 2010

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 1.54.60.0/23, fanning out from AS18403 toward the vantage points that see it. Each path is written out in full beneath the graph.AS18403FPT Telecom Compa…OriginAS213151Christian ElsenAS132337AxclusiveAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam18403213151This path
  2. Singapore18403132337This path
  3. London, UK1840333568529This path
  4. Sao Paulo184033356266213This path
  5. Oregon, US18403693920130This 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
26th May 2010
Allocation block
1.52.0.0/14
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 1.54.60.0/23
ROA prefixAuthorised originMax length
1.52.0.0/14AS18403/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 1.54.60.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.1.54.48.0/20AS184031.54.0.0/18AS184031.52.0.0/14AS184031.54.60.0/23AS18403This prefix1.54.60.0/24AS184031.54.61.0/24AS18403

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 1.54.60.0/23
PrefixAddressesOriginVisibility
1.54.48.0/204.1kAS18403FPT Telecom Company31/80
1.54.0.0/1816.4kAS18403FPT Telecom Company80/80
1.52.0.0/14262kAS18403FPT Telecom Company80/80

More specific announcements

Announcements contained within 1.54.60.0/23
PrefixAddressesOriginVisibility
1.54.60.0/24256AS18403FPT Telecom Company80/80
1.54.61.0/24256AS18403FPT Telecom Company80/80

Sibling prefixes

No prefix of the same length in the same parent block is announced.

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 1.54.60.0/23 in the calculator/23 reference

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