AwanCerahBGP
Autonomous System

Kcell JSC

AS29355KazakhstanRIPE NCC · since 2003NSPPeering: Selective

KCELL-AS

kcell.kz
Kcell JSC website
A94/100Excellent

BGP report

Ranked 15 of 231 networks in Kazakhstan. World rank 6,824.

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

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

Score history

RPKI ROA

Needs work
30/30

2,559 of 2,561 prefixes have a matching ROA (valid). 2 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

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

IRR route objects

Needs work
19/20

1,908 prefixes have an exact route object, 652 are covered by a larger one, 1 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 (1)
Covered by a larger object (652)
2.74.0.0/172.76.0.0/232.76.2.0/232.76.4.0/232.76.6.0/232.76.8.0/232.76.10.0/232.76.12.0/232.76.14.0/232.76.16.0/232.76.18.0/232.76.20.0/232.76.22.0/232.76.24.0/232.76.26.0/232.76.28.0/232.76.30.0/232.76.32.0/232.76.34.0/232.76.36.0/232.76.38.0/232.76.40.0/232.76.42.0/232.76.44.0/232.76.46.0/232.76.48.0/232.76.50.0/232.76.52.0/232.76.54.0/232.76.56.0/232.76.58.0/232.76.60.0/232.76.62.0/232.76.64.0/232.76.66.0/232.76.68.0/232.76.70.0/232.76.72.0/232.76.74.0/232.76.76.0/232.76.78.0/232.76.80.0/232.76.82.0/232.76.84.0/232.76.86.0/232.76.88.0/232.76.90.0/232.76.92.0/232.76.94.0/232.76.96.0/232.76.98.0/232.76.100.0/232.76.102.0/232.76.104.0/232.76.106.0/232.76.108.0/232.76.110.0/232.76.112.0/232.76.114.0/232.76.116.0/232.76.118.0/232.76.120.0/232.76.122.0/232.76.124.0/232.76.126.0/232.76.128.0/232.76.130.0/232.76.132.0/232.76.134.0/232.76.136.0/232.76.138.0/232.76.140.0/232.76.142.0/232.76.144.0/232.76.146.0/232.76.148.0/232.76.150.0/232.76.152.0/232.76.154.0/232.76.156.0/232.76.158.0/232.76.160.0/232.76.162.0/232.76.164.0/232.76.166.0/232.76.168.0/232.76.170.0/232.76.172.0/232.76.174.0/232.76.176.0/232.76.178.0/232.76.180.0/232.76.182.0/232.76.184.0/232.76.186.0/232.76.188.0/232.76.190.0/232.76.192.0/232.76.194.0/232.76.196.0/232.76.198.0/232.76.200.0/232.76.202.0/232.76.204.0/232.76.206.0/232.76.208.0/232.76.210.0/232.76.212.0/232.76.214.0/232.76.216.0/232.76.218.0/232.76.220.0/232.76.222.0/232.76.224.0/232.76.226.0/232.76.228.0/232.76.230.0/232.76.232.0/232.76.234.0/232.76.236.0/232.76.238.0/232.76.240.0/232.76.242.0/232.76.244.0/232.76.246.0/232.76.248.0/232.76.250.0/232.76.252.0/232.76.254.0/232.78.53.0/242.78.56.0/232.78.60.0/232.78.128.0/232.78.130.0/232.78.132.0/232.78.134.0/232.78.136.0/232.78.138.0/232.78.140.0/232.78.142.0/232.78.144.0/232.78.146.0/232.78.148.0/232.78.150.0/232.78.152.0/232.78.154.0/232.78.156.0/232.78.158.0/232.78.160.0/232.78.162.0/232.78.164.0/232.78.166.0/232.78.168.0/232.78.170.0/232.78.172.0/232.78.174.0/232.78.176.0/232.78.178.0/232.78.180.0/232.78.182.0/232.78.184.0/232.78.186.0/232.78.188.0/232.78.190.0/232.78.192.0/232.78.194.0/232.78.196.0/232.78.198.0/232.78.200.0/232.78.202.0/232.78.204.0/232.78.206.0/232.78.208.0/232.78.210.0/232.78.212.0/232.78.214.0/232.78.216.0/232.78.218.0/232.78.220.0/232.78.222.0/232.78.224.0/232.78.226.0/232.78.228.0/232.78.230.0/232.78.232.0/232.78.234.0/232.78.236.0/232.78.238.0/232.78.240.0/232.78.242.0/232.78.244.0/232.78.246.0/232.78.248.0/232.78.250.0/232.78.252.0/232.78.254.0/232.79.0.0/232.79.2.0/232.79.4.0/232.79.6.0/23

Upstream redundancy

Good
15/15

3 upstream, 0 peer, 0 downstream.

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

Upstream (3)

Global visibility

Needs work
10/10

2,533 of 2,561 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 (28)

IPv6

Good
10/10

8 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 3 IX.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

Prefix aggregation

Problem
0/5

2,553 IPv4 prefixes could be summarized into 24.

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