NATIONAL INFORMATION RESOURCES SERVICE
NCIA-AS-KR-KR
BGP report
Ranked 621 of 939 networks in South Korea, 48 of 55 ISPs and transit networks. World rank 82,446.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Needs work0 of 721 prefixes have a matching ROA (valid). 721 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 (721)
IRR route objects
Needs work454 prefixes have an exact route object, 253 are covered by a larger one, 14 only have objects with another origin, 0 have none.
Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.
- Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
- Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (14)
Covered by a larger object (253)
Upstream redundancy
Good4 upstream, 0 peer, 3 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Needs work461 of 721 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 (260)
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
ProblemNo PeeringDB profile.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
- Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.
Prefix aggregation
Problem721 IPv4 prefixes could be summarized into 102.
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/AS17841/rapor"><img src="https://bgp.awancerah.cloud/en/AS17841/rapor.svg" alt="BGP report AS17841"></a>
[](https://bgp.awancerah.cloud/en/AS17841/rapor)