SUBNET.IM

124.240.192.0/24

Telikom PNG Satellite Tier 1 AS Internet ServiceAS38009

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

APNICPG

Allocated 7th November 2007

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 124.240.192.0/24, fanning out from AS38009 toward the vantage points that see it. Each path is written out in full beneath the graph.AS38009Telikom PNG Satel…OriginAS17828PNG DATACO LTDAS6939Hurricane Electri…AS213151Christian ElsenAS4637Telstra Internati…AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS4826Vocus Connect Int…AS132337AxclusiveAS20130Depaul University
  1. Amsterdam38009178286939213151This path
  2. London, UK380091782846378529This path
  3. Sao Paulo38009178286939266213This path
  4. Singapore38009178284826132337This path
  5. Oregon, US3800917828693920130This 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

99%

Seen by 79 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
Papua New Guinea
Allocated
7th November 2007
Allocation block
124.240.192.0/19
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 124.240.192.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.124.240.192.0/19AS38009124.240.192.0/24AS38009This prefix124.240.193.0/24AS38009

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 124.240.192.0/24
PrefixAddressesOriginVisibility
124.240.192.0/198.2kAS38009Telikom PNG Satellite Tier 1 AS Internet Service79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 124.240.192.0/24
PrefixAddressesOriginVisibility
124.240.193.0/24256AS38009Telikom PNG Satellite Tier 1 AS Internet Service79/80

History

  1. AS3800912th 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 124.240.192.0/24 in the calculator/24 reference

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