AwanCerahBGP
Home/Malaysia/AS154321
Autonomous System

CORENET CLOUD SDN. BHD.

AS154321MalaysiaAPNIC · since 2025

CCSB-AS-AP

B77/100Good

BGP report

Ranked 137 of 266 networks in Malaysia. World rank 33,141.

  • RPKI ROA22/30
  • IRR route objects17/20
  • Upstream redundancy15/15
  • Global visibility9/10
  • IPv610/10
  • PeeringDB4/10
  • Prefix aggregation0/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Problem
22/30

131 of 153 prefixes have a matching ROA (valid). 17 invalid, 5 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
  2. Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
  3. The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Invalid prefixes (17)
Prefixes without a ROA (5)

IRR route objects

Good
17/20

71 prefixes have an exact route object, 82 are covered by a larger one, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

Covered by a larger object (82)

Upstream redundancy

Good
15/15

8 upstream, 7 peer, 0 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

Upstream (8)

Global visibility

Needs work
9/10

136 of 153 prefixes are seen by at least half of the full-table feeds worldwide.

Prefixes seen only partly are usually caught by filters (no ROA or route object), too specific, or announced to domestic IXPs only.

How to fix
  1. Check the ROA and route object of those prefixes, and keep them no longer than /24 for IPv4 or /48 for IPv6.
Prefixes with low visibility (17)

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
4/10

Profile exists. Missing: IRR as-set, IX connections, peering policy, prefix counts.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Problem
0/5

152 IPv4 prefixes could be summarized into 16.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

How to fix
  1. Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.

Put the badge on your website

BGP report AS154321The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS154321/rapor"><img src="https://bgp.awancerah.cloud/en/AS154321/rapor.svg" alt="BGP report AS154321"></a>
Markdown
[![BGP report AS154321](https://bgp.awancerah.cloud/en/AS154321/rapor.svg)](https://bgp.awancerah.cloud/en/AS154321/rapor)