subnet.im

101.53.47.0/24

At a glance

Addresses

256

/24 block

Visibility

24%

18 of 76 vantage points

RPKI

Valid

Registry

APNICVN

Allocated 14th February 2011

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 101.53.47.0/24 as seen from London, UK, read outward from the origin: AS24173 → AS140951 → AS10135 → AS10133 → AS6939 → AS8529. Each hop is listed with its network name beneath the graph.AS24173Netnam CompanyOriginAS140951IPTP NetworksAS10135EASPNET Inc.AS10133Chief Telecom Inc.AS6939Hurricane Electri…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS24173seen on 607 paths from 24 vantage points
  2. Peer of AS140951seen on 19 paths from 18 vantage points
  3. Peer of AS10135seen on 9 paths from 9 vantage points
  4. Peer of AS10133seen on 1,896 paths from 24 vantage points
  5. Peer of AS6939seen on 234,677 paths from 8 vantage points

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. Sao Paulo2417314095110135771335280This path
  2. London, UK24173140951101351013369398529Shown above
  3. Singapore2417314095110135244823862323673This 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

24%

Seen by 18 of 76 full-feed vantage points

Seen by few vantage points

Observed at 4 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
14th February 2011
Allocation block
101.53.0.0/18
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 101.53.47.0/24
ROA prefixAuthorised originMax length
101.53.0.0/18AS24173/24
101.53.0.0/18AS24176/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 101.53.47.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.101.53.0.0/18AS24176101.53.47.0/24AS24173This prefix101.53.46.0/24AS24173

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 101.53.47.0/24
PrefixAddressesOriginVisibility
101.53.0.0/1816.4kAS24176Branch of Netnam Company in Ho Chi Minh City76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 101.53.47.0/24
PrefixAddressesOriginVisibility
101.53.46.0/24256AS24173Netnam Company76/76

History

  1. AS2417322nd October 2026 — present
  2. AS241736th October 2026 — 20th October 2026
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 101.53.47.0/24 in the calculator/24 reference

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