BGP report
Ranked 2,224 of 3,004 networks in Indonesia. World rank 44,460.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Needs work1 of 3 prefixes have a matching ROA (valid). 2 without a ROA.
Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.
- 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.
- 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.
Prefixes without a ROA (2)
IRR route objects
Good3 prefixes have an exact route object, 0 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.
Upstream redundancy
Good6 upstream, 2 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good3 of 3 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.
IPv6
ProblemNo IPv6 prefix is announced.
Most mobile users and large services already run on IPv6.
- Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.
PeeringDB
GoodProfile exists, listed at 3 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Good3 IPv4 prefixes could be summarized into 3.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS151995/rapor"><img src="https://bgp.awancerah.cloud/en/AS151995/rapor.svg" alt="BGP report AS151995"></a>
[](https://bgp.awancerah.cloud/en/AS151995/rapor)
