subnet.im

43.239.221.0/24

At a glance

Addresses

256

/24 block

Visibility

20%

16 of 80 vantage points

RPKI

Invalid

Registry

APNICVN

Allocated 18th August 2015

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 43.239.221.0/24 as seen from Singapore, read outward from the origin: AS7643 → AS45899 → AS132337. Each hop is listed with its network name beneath the graph.AS7643Vietnam Posts and…OriginAS45899VNPT CorpAS132337Axclusive

Seen from Singapore

  1. Peer of AS7643seen on 5,480 paths from 80 vantage points
  2. Peer of AS45899seen on 4,952 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Singapore764345899132337Shown above

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.

Route visibility

20%

Seen by 16 of 80 full-feed vantage points

Seen by few vantage points

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
18th August 2015
Allocation block
43.239.220.0/22
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 43.239.221.0/24
ROA prefixAuthorised originMax length
43.239.220.0/23AS45899/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 43.239.221.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.43.239.220.0/23AS4589943.239.221.0/24AS7643This prefix43.239.220.0/24AS7643

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 43.239.221.0/24
PrefixAddressesOriginVisibility
43.239.220.0/23512AS45899VNPT Corp80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 43.239.221.0/24
PrefixAddressesOriginVisibility
43.239.220.0/24256AS7643Vietnam Posts and Telecommunications (VNPT)16/80

History

  1. AS764312th 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 43.239.221.0/24 in the calculator/24 reference

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