SUBNET.IM

103.40.2.0/23

Kinahugan Bojol Communications, Inc.AS150450

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICPH

Allocated 17th November 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
AS path graph: 5 observed paths to 103.40.2.0/23, fanning out from AS150450 toward the vantage points that see it. Each path is written out in full beneath the graph.AS150450Kinahugan Bojol C…OriginAS4775Globe TelecomsAS132337AxclusiveAS6939Hurricane Electri…AS213151Christian ElsenAS4637Telstra Internati…AS8529Zain Omantel Inte…AS262355VSX NetworksAS266213PLANETCLICK TELEC…AS20130Depaul University
  1. Singapore1504504775132337This path
  2. Amsterdam15045047756939213151This path
  3. London, UK150450477546378529This path
  4. Sao Paulo1504504775262355266213This path
  5. Oregon, US1504504775693920130This 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

100%

Seen by 80 of 80 full-feed vantage points

Globally 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
Philippines
Allocated
17th November 2022
Allocation block
103.40.2.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.40.2.0/23
ROA prefixAuthorised originMax length
103.40.2.0/23AS150450/23

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 103.40.2.0/23: 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.40.2.0/23AS150450This prefix103.40.2.0/24AS150450103.40.3.0/24AS150450

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 103.40.2.0/23
PrefixAddressesOriginVisibility
103.40.2.0/24256AS150450Kinahugan Bojol Communications, Inc.80/80
103.40.3.0/24256AS150450Kinahugan Bojol Communications, Inc.80/80

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS15045012th 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 103.40.2.0/23 in the calculator/23 reference

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