subnet.im

103.186.214.0/24

cognetcloud INCAS401701

cognetcloud INCAS401696

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

3%

2 of 76 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 28th April 2022

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
  1. Singapore401696407794635100995532923673This path
  2. Sao Paulo401701407794635930423764771335280This 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

3%

Seen by 2 of 76 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Hong Kong SAR China
Allocated
28th April 2022
Allocation block
103.186.214.0/23
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 103.186.214.0/24
ROA prefixAuthorised originMax length
103.186.214.0/23AS137899/24
103.186.214.0/23AS142032/24
103.186.214.0/23AS35876/24
103.186.214.0/23AS36652/24
103.186.214.0/23AS401696/24
103.186.214.0/23AS401701/24
103.186.214.0/23AS40779/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 103.186.214.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.103.186.214.0/23AS401696103.186.214.0/24AS401701This prefix103.186.215.0/24AS401696

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 103.186.214.0/24
PrefixAddressesOriginVisibility
103.186.214.0/23512AS401696cognetcloud INC76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 103.186.214.0/24
PrefixAddressesOriginVisibility
103.186.215.0/24256AS401696cognetcloud INC1/76

History

  1. AS40170111th November 2026 — present
  2. AS4016966th November 2026 — present
  3. AS4017019th November 2026 — 10th November 2026
  4. AS4017019th November 2026 — 9th November 2026
  5. AS4017018th November 2026 — 8th November 2026
  6. AS4017015th November 2026 — 6th November 2026
  7. AS4016965th November 2026 — 5th November 2026
  8. AS4017014th November 2026 — 5th 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.186.214.0/24 in the calculator/24 reference

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