subnet.im

43.224.249.0/24

At a glance

Addresses

256

/24 block

Visibility

57%

46 of 80 vantage points

RPKI

No ROA

Registry

APNICTW

Allocated 28th November 2014

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. Singapore2454455933132337This path
  2. Amsterdam2454455933932291434549213151This path
  3. London, UK24544559333223335664538529This path
  4. Oregon, US245445593393229142335220130This 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

57%

Seen by 46 of 80 full-feed vantage points

Partially propagated

Observed at 5 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
Taiwan
Allocated
28th November 2014
Allocation block
43.224.248.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 43.224.249.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.224.248.0/23AS2454443.224.249.0/24AS24544This prefix43.224.248.0/24AS24544

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.224.249.0/24
PrefixAddressesOriginVisibility
43.224.248.0/23512AS24544Law's Cloud Infrastructure Limited79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 43.224.249.0/24
PrefixAddressesOriginVisibility
43.224.248.0/24256AS24544Law's Cloud Infrastructure Limited44/80

History

  1. AS2454412th August 2026 present
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.224.249.0/24 in the calculator/24 reference

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