SUBNET.IM

36.50.100.0/24

PT Parsaoran Global DatatransAS58495

At a glance

Addresses

256

/24 block

Visibility

30%

24 of 80 vantage points

RPKI

Invalid

Registry

APNICID

Allocated 13th December 2023

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 36.50.100.0/24, fanning out from AS58495 toward the vantage points that see it. Each path is written out in full beneath the graph.AS58495PT Parsaoran Glob…OriginAS138840PT Parsaoran Glob…AS6453TATA Communicatio…AS8529Zain Omantel Inte…AS4800PT Aplikanusa Lin…AS8966Etisalat (E&)AS132337Axclusive
  1. London, UK5849513884064538529This path
  2. Singapore5849548008966132337This 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

30%

Seen by 24 of 80 full-feed vantage points

Seen by few vantage points

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
Indonesia
Allocated
13th December 2023
Allocation block
36.50.100.0/23
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 36.50.100.0/24
ROA prefixAuthorised originMax length
36.50.100.0/23AS58495/23

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 36.50.100.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.36.50.100.0/23AS5849536.50.100.0/24AS58495This prefix36.50.101.0/24AS58495

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 36.50.100.0/24
PrefixAddressesOriginVisibility
36.50.100.0/23512AS58495PT Parsaoran Global Datatrans80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 36.50.100.0/24
PrefixAddressesOriginVisibility
36.50.101.0/24256AS58495PT Parsaoran Global Datatrans18/80

History

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

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