AwanCerahBGP
Home/Taiwan/AS17421
Autonomous System

Mobile Business Group

AS17421TaiwanAPNIC · since 2000

EMOME-NET

B70/100Good

BGP report

Ranked 240 of 297 networks in Taiwan. World rank 43,952.

  • RPKI ROA30/30
  • IRR route objects12/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Good
30/30

227 of 227 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

Needs work
12/20

0 prefixes have an exact route object, 179 are covered by a larger one, 34 only have objects with another origin, 14 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.
No route object (14)
Route object with another origin (34)
Covered by a larger object (179)
42.64.0.0/1642.66.0.0/1642.70.0.0/1842.70.64.0/1842.70.128.0/1842.70.192.0/1842.71.0.0/1842.71.64.0/1842.71.128.0/1842.71.192.0/1842.72.0.0/1842.72.64.0/1842.72.128.0/1842.72.192.0/1842.73.0.0/1742.73.128.0/1742.74.0.0/1642.75.0.0/1642.76.0.0/1842.76.64.0/1842.76.128.0/1842.76.192.0/1842.77.0.0/1842.77.64.0/1842.77.128.0/1842.77.192.0/1842.78.0.0/1842.78.64.0/1842.78.128.0/1842.78.192.0/1842.79.0.0/1742.79.0.0/1842.79.64.0/1842.79.128.0/1942.79.160.0/1942.79.192.0/1942.79.224.0/19111.70.0.0/18111.71.0.0/18111.71.64.0/18111.71.128.0/18111.71.193.0/24111.71.194.0/24111.71.195.0/24111.71.196.0/24111.71.197.0/24111.71.208.0/24111.71.209.0/24111.71.212.0/24111.71.213.0/24111.71.214.0/24111.71.215.0/24111.71.216.0/24111.71.217.0/24111.71.218.0/24111.71.220.0/24111.71.221.0/24111.71.222.0/24111.71.223.0/24111.71.225.0/24111.71.226.0/24111.71.227.0/24111.71.228.0/24111.71.229.0/24111.71.230.0/24111.71.240.0/24111.71.242.0/23111.71.248.0/24111.71.252.0/24111.71.253.0/24111.71.254.0/24111.80.0.0/16111.81.0.0/18111.81.64.0/18111.81.128.0/18111.81.192.0/18111.82.0.0/17111.82.128.0/17111.83.0.0/18111.83.64.0/18111.83.128.0/18111.83.192.0/18114.136.0.0/18114.136.64.0/18114.136.128.0/18114.136.192.0/18114.137.0.0/19114.137.32.0/19114.137.64.0/19114.137.96.0/19114.137.128.0/18114.137.192.0/18211.79.33.0/24211.79.34.0/24211.79.35.0/24211.79.36.0/24211.79.37.0/24211.79.38.0/24211.79.40.0/24211.79.41.0/24211.79.42.0/24211.79.47.0/24221.120.0.0/21221.120.8.0/22221.120.12.0/22221.120.19.0/24221.120.20.0/24221.120.21.0/24221.120.23.0/24221.120.30.0/24221.120.32.0/23221.120.34.0/24221.120.36.0/23221.120.38.0/24221.120.40.0/22221.120.40.0/24221.120.41.0/24221.120.42.0/23221.120.44.0/24221.120.45.0/24221.120.46.0/23221.120.48.0/23221.120.50.0/24221.120.51.0/24221.120.56.0/24221.120.57.0/24221.120.58.0/23221.120.72.0/24221.120.73.0/24221.120.74.0/24221.120.75.0/24221.120.76.0/22221.120.80.0/24221.120.81.0/24221.120.82.0/24221.120.83.0/24223.136.0.0/19223.136.32.0/19223.136.64.0/19223.136.96.0/19223.136.128.0/18223.136.192.0/18223.137.0.0/18223.137.64.0/18223.137.128.0/18223.137.192.0/18223.138.0.0/19223.138.32.0/19223.138.64.0/19223.138.96.0/19223.138.128.0/18223.138.192.0/18223.139.0.0/18223.139.64.0/18223.139.128.0/18223.139.192.0/18223.140.0.0/18223.140.64.0/18223.140.128.0/18223.140.192.0/18223.141.0.0/18223.141.64.0/18223.141.128.0/19223.141.160.0/19223.141.192.0/19223.141.224.0/19223.143.0.0/17223.143.128.0/19223.143.160.0/19223.143.192.0/21223.143.200.0/21223.143.208.0/21223.143.216.0/21223.143.224.0/21223.143.232.0/21223.143.240.0/23223.143.242.0/23223.143.244.0/23223.143.246.0/23

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Needs work
10/10

225 of 227 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.

How to fix
  1. 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 (2)

IPv6

Good
10/10

34 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
1/5

193 IPv4 prefixes could be summarized into 63.

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.

Put the badge on your website

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