subnet.im

113.11.239.0/24

Lembaga Hasil Dalam Negeri MalaysiaAS55951

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

APNICMY

Allocated 23rd December 2010

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 113.11.239.0/24 as seen from Singapore, read outward from the origin: AS55951 → AS45630 → AS4788 → AS132337. Each hop is listed with its network name beneath the graph.AS55951Lembaga Hasil Dal…OriginAS45630Fibrecomm Network…AS4788TM Technology Ser…AS132337Axclusive

Seen from Singapore

  1. 1AS55951Lembaga Hasil Dalam Negeri MalaysiaMYOrigin
    Peer of AS55951seen on 282 paths from 80 vantage points
  2. 2AS45630Fibrecomm Network (M) Sdn. Bhd.MY
    Peer of AS45630seen on 140 paths from 85 vantage points
  3. 3AS4788TM Technology Services Sdn. Bhd.MY
    Peer of AS4788seen on 4,761 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. London, UK559514563012998529This path
  2. Singapore55951456304788132337Shown above
  3. Oregon, US5595145630693920130This path
  4. Sao Paulo559514563012993356266213This path
  5. Amsterdam5595145630563087473646134549213151This 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
Malaysia
Allocated
23rd December 2010
Allocation block
113.11.236.0/22
Status
assigned
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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 113.11.239.0/24
PrefixAddressesOriginVisibility
113.11.238.0/24256AS55951Lembaga Hasil Dalam Negeri Malaysia80/80

History

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

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