BGP report
Ranked 359 of 3,004 networks in Indonesia, 173 of 482 ISPs and transit networks. World rank 7,616.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good312 of 312 prefixes have a matching ROA (valid). 0 without a ROA.
Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.
IRR route objects
Good9 prefixes have an exact route object, 303 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 (303)
Upstream redundancy
Good7 upstream, 3 peer, 8 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good312 of 312 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
Good304 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 6 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Needs work8 IPv4 prefixes could be summarized into 3.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
- Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.
Dropping invalid routes (ROV)
GoodNot seen passing on RPKI-invalid routes of other networks in sampled paths.
Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS140481/rapor"><img src="https://bgp.awancerah.cloud/en/AS140481/rapor.svg" alt="BGP report AS140481"></a>
[](https://bgp.awancerah.cloud/en/AS140481/rapor)
