SUBNET.IM

128.53.0.0/16

NTT PC Communications, Inc.AS2514

At a glance

Addresses

65,536

/16 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICJP

Allocated 13th June 1983

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 128.53.0.0/16, fanning out from AS2514 toward the vantage points that see it. Each path is written out in full beneath the graph.AS2514NTT PC Communicat…OriginAS6453TATA Communicatio…AS8529Zain Omantel Inte…AS8966Etisalat (E&)AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS34549meerfarbig GmbH &…AS213151Christian ElsenAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK251464538529This path
  2. Singapore25148966132337This path
  3. Oregon, US2514693920130This path
  4. Amsterdam2514645334549213151This path
  5. Sao Paulo251464533356266213This 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
Japan
Allocated
13th June 1983
Allocation block
128.53.0.0/16
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 128.53.0.0/16
ROA prefixAuthorised originMax length
128.53.0.0/16AS2514/16
128.53.0.0/16AS2514/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 128.53.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.128.53.0.0/16AS2514This prefix128.53.96.0/19AS2514128.53.160.0/19AS2514128.53.192.0/19AS2514128.53.16.0/20AS2514128.53.80.0/20AS2514+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

No less specific announcement covers this prefix.

Sibling prefixes

Prefixes of the same length sharing a parent block with 128.53.0.0/16
PrefixAddressesOriginVisibility
128.52.0.0/1665.5kAS3Massachusetts Institute of Technology79/80

History

  1. AS251412th 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 128.53.0.0/16 in the calculator/16 reference

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