subnet.im

114.134.189.0/24

cognetcloud INCAS401701

At a glance

Addresses

256

/24 block

Visibility

12%

9 of 76 vantage points

RPKI

No ROA

Registry

APNICHK

Allocated 7th March 2011

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
AS path graph: 2 observed paths to 114.134.189.0/24, fanning out from AS401701 toward the vantage points that see it. Each path is written out in full beneath the graph.AS401701cognetcloud INCOriginAS40779VoltNet incAS4635HKIX Route ServersAS9304HGC Global Commun…AS38623Metfone (Viettel …AS23673Cogetel Online, C…AS23764China Telecom Glo…AS7713PT Telkom Indones…AS35280F5 Networks SARL
  1. Singapore40170140779463593043862323673This 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

12%

Seen by 9 of 76 full-feed vantage points

Seen by few vantage points

Observed at 3 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
7th March 2011
Allocation block
114.134.188.0/23
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 114.134.189.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.114.134.188.0/23AS401696114.134.189.0/24AS401701This prefix114.134.188.0/24AS401701

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 114.134.189.0/24
PrefixAddressesOriginVisibility
114.134.188.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 114.134.189.0/24
PrefixAddressesOriginVisibility
114.134.188.0/24256AS401701cognetcloud INC7/76

History

  1. AS4017016th November 2026 — present
  2. AS4016964th November 2026 — 5th November 2026
  3. AS4017013rd November 2026 — 4th November 2026
  4. AS4016963rd November 2026 — 3rd November 2026
  5. AS4017012nd November 2026 — 3rd November 2026
  6. AS4017011st November 2026 — 1st November 2026
  7. AS40170131st October 2026 — 31st October 2026
  8. AS40170130th October 2026 — 30th 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 114.134.189.0/24 in the calculator/24 reference

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