AwanCerahBGP
Autonomous System

Zhilian Technology CO., LTD.

AS214432United KingdomRIPE NCC · since 2024Cable/DSL/ISPPeering: Open

NTT-Communications-Corporation

zlidc.net
Zhilian Technology CO., LTD. website
B76/100Good

BGP report

Ranked 1,153 of 2,318 networks in United Kingdom, 298 of 385 ISPs and transit networks. World rank 33,908.

  • RPKI ROA16/30
  • IRR route objects15/20
  • Upstream redundancy15/15
  • Global visibility7/10
  • IPv610/10
  • PeeringDB8/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Problem
16/30

141 of 191 prefixes have a matching ROA (valid). 36 invalid, 14 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 (36)
Prefixes without a ROA (14)

IRR route objects

Needs work
15/20

141 prefixes have an exact route object, 8 are covered by a larger one, 40 only have objects with another origin, 2 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 (2)
Route object with another origin (40)
Covered by a larger object (8)

Upstream redundancy

Good
15/15

13 upstream, 0 peer, 6 downstream.

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

Upstream (13)

IPv6

Good
10/10

6 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
8/10

Profile exists. Missing: IX connections.

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

Good
5/5

185 IPv4 prefixes could be summarized into 153.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

Dropping invalid routes (ROV)

Note

Seen passing on 3 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (3)

Put the badge on your website

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