subnet.im

103.127.88.0/23

Not announced at this prefix length

No announcement covering 103.127.88.0/23 was visible from any of our collectors at the last snapshot. That can mean the space is unrouted, or that it is announced only within a network we have no vantage point inside.

At a glance

Addresses

512

/23 block

Visibility

Unknown

RPKI

Unknown

Registry

APNICTH

Allocated 17th December 2018

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
Thailand
Allocated
17th December 2018
Allocation block
103.127.88.0/23
Status
allocated
Origin validation
Unknown

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

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

History

  1. AS13616828th October 2026 — 2nd November 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 103.127.88.0/23 in the calculator/23 reference

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