AwanCerahBGP
Home/Taiwan/AS9919
Autonomous System

New Century InfoComm Tech Co., Ltd.

AS9919TaiwanAPNIC · since 2000

NCIC-TW

A85/100Excellent

BGP report

Ranked 125 of 297 networks in Taiwan, 46 of 72 ISPs and transit networks. World rank 18,494.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Problem
30/30

853 of 856 prefixes have a matching ROA (valid). 1 invalid, 2 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 (1)
Prefixes without a ROA (2)

IRR route objects

Needs work
20/20

840 prefixes have an exact route object, 13 are covered by a larger one, 3 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.

How to fix
  1. 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.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (3)
Covered by a larger object (13)

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 1 downstream.

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

Upstream (2)

IPv6

Good
10/10

16 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Problem
0/10

No PeeringDB profile.

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

840 IPv4 prefixes could be summarized into 67.

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.

Dropping invalid routes (ROV)

Good

Not 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

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