AwanCerahBGP
Home/China/AS140293
Autonomous System

CHINATELECOM Jiangsu province Changzhou 5G network

AS140293ChinaAPNIC · since 2020

CHINATELECOM-JIANGSU-CHANGZHOU-5G-NETWORK

A86/100Excellent

BGP report

Ranked 237 of 5,214 networks in China. World rank 17,186.

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

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

Score history

RPKI ROA

Good
30/30

1,138 of 1,138 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
18/20

1,015 prefixes have an exact route object, 0 are covered by a larger one, 123 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 (123)
49.80.7.0/2449.80.64.0/2449.80.65.0/2449.80.66.0/2449.80.67.0/2449.80.101.0/2449.80.102.0/2449.80.103.0/2449.80.104.0/2349.80.106.0/2349.80.108.0/2449.80.112.0/2449.80.113.0/2449.80.115.0/2449.80.116.0/2449.80.117.0/2449.80.118.0/2449.80.119.0/2449.80.122.0/2449.80.124.0/2449.80.125.0/2449.80.126.0/2449.80.127.0/24114.226.61.0/24117.63.42.0/23117.63.230.0/24121.231.2.0/24121.231.3.0/24121.231.8.0/22121.231.12.0/22121.231.19.0/24121.231.20.0/24121.231.22.0/24121.231.24.0/24121.231.25.0/24121.231.28.0/24121.231.32.0/24121.231.35.0/24121.231.36.0/22121.231.50.0/23121.231.53.0/24121.231.55.0/24121.231.56.0/22121.231.61.0/24121.231.62.0/24121.231.63.0/24121.231.64.0/21121.231.72.0/24121.231.73.0/24121.231.74.0/24121.231.76.0/22121.231.82.0/24121.231.85.0/24121.231.86.0/24121.231.90.0/24121.231.92.0/24121.231.94.0/24121.231.95.0/24121.231.97.0/24121.231.107.0/24121.231.116.0/24121.231.117.0/24121.231.119.0/24121.231.121.0/24121.231.132.0/24121.231.133.0/24121.231.134.0/24121.231.136.0/22121.231.140.0/22121.231.148.0/22121.231.152.0/24121.231.156.0/24121.231.159.0/24121.231.161.0/24121.231.162.0/24121.231.164.0/24121.231.165.0/24121.231.166.0/24121.231.168.0/24121.231.172.0/24121.231.173.0/24121.231.177.0/24121.231.178.0/24121.231.179.0/24121.231.180.0/24121.231.181.0/24121.231.182.0/24121.231.183.0/24121.231.184.0/24121.231.185.0/24121.231.186.0/24121.231.192.0/24121.231.193.0/24121.231.194.0/24121.231.195.0/24121.231.200.0/22121.231.206.0/24121.231.207.0/24121.231.208.0/24121.231.209.0/24121.231.210.0/24121.231.211.0/24121.231.213.0/24121.231.217.0/24121.231.218.0/24121.231.220.0/24121.231.221.0/24121.231.222.0/24121.231.224.0/24121.231.225.0/24121.231.227.0/24121.231.228.0/22121.231.234.0/24121.231.236.0/24121.231.237.0/24121.231.239.0/24121.231.240.0/24121.231.241.0/24121.231.242.0/24121.231.243.0/24121.231.244.0/24121.231.246.0/23121.231.251.0/24

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

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

Upstream (2)

Global visibility

Good
10/10

1,138 of 1,138 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

Good
10/10

10 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

Needs work
3/5

1,128 IPv4 prefixes could be summarized into 459.

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 AS140293The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS140293/rapor"><img src="https://bgp.awancerah.cloud/en/AS140293/rapor.svg" alt="BGP report AS140293"></a>
Markdown
[![BGP report AS140293](https://bgp.awancerah.cloud/en/AS140293/rapor.svg)](https://bgp.awancerah.cloud/en/AS140293/rapor)