subnet.im

43.242.200.0/24

cognetcloud INCAS401701

At a glance

Addresses

256

/24 block

Visibility

3%

2 of 76 vantage points

RPKI

No ROA

Registry

APNICHK

Allocated 4th September 2014

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 43.242.200.0/24 as seen from Sao Paulo, read outward from the origin: AS401701 → AS40779 → AS4635 → AS9304 → AS23764 → AS7713 → AS35280. Each hop is listed with its network name beneath the graph.AS401701cognetcloud INCOriginAS40779VoltNet incAS4635HKIX Route ServersAS9304HGC Global Commun…AS23764China Telecom Glo…AS7713PT Telkom Indones…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. 1AS401701cognetcloud INCUSOrigin
    Peer of AS401701seen on 4,606 paths from 76 vantage points
  2. 2AS40779VoltNet incUS
    Peer of AS40779seen on 490 paths from 9 vantage points
  3. 3AS4635HKIX Route ServersHK
    Peer of AS4635seen on 2,155 paths from 20 vantage points
  4. 4AS9304HGC Global Communications LimitedHK
    Peer of AS9304seen on 1,823 paths from 17 vantage points
  5. 5AS23764China Telecom GlobalHK
    Peer of AS23764seen on 101,214 paths from 70 vantage points
  6. 6AS7713PT Telkom Indonesia TbkID
    Peer of AS7713seen on 102,261 paths from 6 vantage points
  7. 7AS35280F5 Networks SARLFRVantage 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. Sao Paulo401701407794635930423764771335280Shown 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

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
4th September 2014
Allocation block
43.242.200.0/22
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 43.242.200.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.242.200.0/23AS40169643.242.200.0/22AS40169643.242.200.0/24AS401701This prefix43.242.201.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 43.242.200.0/24
PrefixAddressesOriginVisibility
43.242.200.0/23512AS401696cognetcloud INC1/76
43.242.200.0/221kAS401696cognetcloud INC76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 43.242.200.0/24
PrefixAddressesOriginVisibility
43.242.201.0/24256AS401701cognetcloud INC2/76

History

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

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