subnet.im

103.165.109.0/24

Not announced at this prefix length

No announcement covering 103.165.109.0/24 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

256

/24 block

Visibility

Unknown

RPKI

Unknown

Registry

APNICIN

Allocated 31st March 2021

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
India
Allocated
31st March 2021
Allocation block
103.165.108.0/23
Status
assigned
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 103.165.109.0/24
ROA prefixAuthorised originMax length
103.165.108.0/23AS136695/24

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

Prefixes of the same length sharing a parent block with 103.165.109.0/24
PrefixAddressesOriginVisibility
103.165.108.0/24256AS136695Zeroshell Networks Private Limited76/76

History

  1. AS1366957th November 2026 — 9th 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.165.109.0/24 in the calculator/24 reference

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