BGP report
Ranked 185 of 5,215 networks in China. World rank 13,593.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Problem7 of 8 prefixes have a matching ROA (valid). 1 invalid, 0 without a ROA.
Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.
- Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
- 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.
Invalid prefixes (1)
IRR route objects
Good6 prefixes have an exact route object, 2 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 (2)
Upstream redundancy
Good5 upstream, 4 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Needs work7 of 8 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.
- 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 (1)
IPv6
Good6 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 1 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Needs work2 IPv4 prefixes could be summarized into 1.
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.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS44421/rapor"><img src="https://bgp.awancerah.cloud/en/AS44421/rapor.svg" alt="BGP report AS44421"></a>
[](https://bgp.awancerah.cloud/en/AS44421/rapor)