AwanCerahBGP
Autonomous System

Dimension Data

AS3741South AfricaAFRINIC · since 1994NSPPeering: Selective

Dimension Data

services.global.ntt
Dimension Data website
B83/100Good

BGP report

Ranked 256 of 669 networks in South Africa, 69 of 116 ISPs and transit networks. World rank 20,235.

  • RPKI ROA21/30
  • IRR route objects15/20
  • Upstream redundancy15/15
  • Global visibility9/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Needs work
21/30

382 of 543 prefixes have a matching ROA (valid). 161 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 (161)
45.149.227.0/2485.118.154.0/24139.53.0.0/16155.234.0.0/16155.237.0.0/16155.240.0.0/16155.240.0.0/17155.240.152.0/23156.8.0.0/16156.8.251.0/24156.8.252.0/24156.8.254.0/24160.48.233.0/24160.48.234.0/24160.123.0.0/16163.199.96.0/23163.199.98.0/24163.199.99.0/24163.199.101.0/24163.199.104.0/22163.199.108.0/22163.199.136.0/24163.203.0.0/16163.203.0.0/18163.203.64.0/18163.203.160.0/19163.203.192.0/19163.203.224.0/24168.89.0.0/16169.202.201.0/24169.202.202.0/24192.94.242.0/24192.96.1.0/24192.96.22.0/24192.96.38.0/24192.96.46.0/24192.96.57.0/24192.96.89.0/24192.96.90.0/23192.96.92.0/24192.96.120.0/21192.96.128.0/22192.96.132.0/24192.96.133.0/24192.96.134.0/24192.96.251.0/24196.1.115.0/24196.3.156.0/23196.3.159.0/24196.3.163.0/24196.4.71.0/24196.4.72.0/22196.4.76.0/24196.4.83.0/24196.4.97.0/24196.4.168.0/24196.4.172.0/24196.4.173.0/24196.4.174.0/23196.4.176.0/21196.4.184.0/22196.4.188.0/24196.4.212.0/22196.4.216.0/21196.4.224.0/21196.4.232.0/21196.6.133.0/24196.6.136.0/24196.6.137.0/24196.6.142.0/24196.6.147.0/24196.6.149.0/24196.6.150.0/24196.6.151.0/24196.6.153.0/24196.6.160.0/24196.6.161.0/24196.6.162.0/24196.6.165.0/24196.6.212.0/23196.6.212.0/24196.6.222.0/23196.6.237.0/24196.6.251.0/24196.10.104.0/24196.10.118.0/24196.10.124.0/22196.10.130.0/23196.10.132.0/22196.10.150.0/23196.10.152.0/21196.10.160.0/19196.10.192.0/21196.10.204.0/22196.10.208.0/22196.10.212.0/23196.10.229.0/24196.10.248.0/23196.10.249.0/24196.11.58.0/24196.11.69.0/24196.11.70.0/24196.11.72.0/24196.11.109.0/24196.11.110.0/23196.11.112.0/23196.11.114.0/24196.11.116.0/24196.11.122.0/24196.11.148.0/23196.11.170.0/23196.11.172.0/23196.11.174.0/24196.11.188.0/24196.11.205.0/24196.11.209.0/24196.13.93.0/24196.13.97.0/24196.13.132.0/24196.13.163.0/24196.13.164.0/24196.13.165.0/24196.13.213.0/24196.13.214.0/23196.13.216.0/23196.13.225.0/24196.13.226.0/23196.13.232.0/24196.13.251.0/24196.15.152.0/24196.22.0.0/22196.22.32.0/20196.208.0.0/13198.54.20.0/22198.54.24.0/21198.54.32.0/21198.54.40.0/23198.54.42.0/24198.54.64.0/24198.54.71.0/24198.54.72.0/22198.54.84.0/24198.54.149.0/24198.54.154.0/24198.54.156.0/22198.54.160.0/23198.54.163.0/24198.54.165.0/24198.54.170.0/24198.54.184.0/22198.54.188.0/23198.54.192.0/22198.54.196.0/24198.54.219.0/24198.54.228.0/24198.54.253.0/24204.235.32.0/21204.235.40.0/222001:43fe:a014::/482c0f:f400:10fe::/482c0f:f400:10ff::/48

IRR route objects

Needs work
15/20

221 prefixes have an exact route object, 237 are covered by a larger one, 71 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 (71)
Covered by a larger object (237)
41.86.100.0/2241.86.110.0/2441.86.111.0/2441.86.116.0/22152.111.1.0/24152.111.2.0/24152.111.3.0/24152.111.4.0/24152.111.5.0/24152.111.6.0/24152.111.8.0/24152.111.9.0/24152.111.10.0/24152.111.11.0/24152.111.12.0/24152.111.14.0/24152.111.15.0/24152.111.16.0/24152.111.17.0/24152.111.18.0/24152.111.19.0/24152.111.20.0/24152.111.21.0/24152.111.22.0/24152.111.23.0/24152.111.24.0/24152.111.25.0/24152.111.26.0/24152.111.27.0/24152.111.28.0/24152.111.29.0/24152.111.30.0/24152.111.31.0/24152.111.32.0/24152.111.33.0/24152.111.34.0/24152.111.35.0/24152.111.36.0/24152.111.37.0/24152.111.41.0/24152.111.43.0/24152.111.44.0/23152.111.44.0/24152.111.45.0/24152.111.46.0/24152.111.47.0/24152.111.51.0/24152.111.53.0/24152.111.54.0/24152.111.55.0/24152.111.56.0/24152.111.57.0/24152.111.59.0/24152.111.60.0/24152.111.61.0/24152.111.63.0/24152.111.66.0/24152.111.67.0/24152.111.68.0/24152.111.69.0/24152.111.70.0/24152.111.72.0/24152.111.73.0/24152.111.74.0/24152.111.77.0/24152.111.78.0/24152.111.79.0/24152.111.82.0/24152.111.83.0/24152.111.84.0/24152.111.85.0/24152.111.86.0/24152.111.87.0/24152.111.90.0/24152.111.91.0/24152.111.92.0/24152.111.94.0/24152.111.95.0/24152.111.96.0/24152.111.97.0/24152.111.99.0/24152.111.100.0/23152.111.101.0/24152.111.102.0/24152.111.103.0/24152.111.104.0/24152.111.105.0/24152.111.106.0/23152.111.106.0/24152.111.108.0/24152.111.109.0/24152.111.130.0/24152.111.131.0/24152.111.132.0/24152.111.133.0/24152.111.134.0/24152.111.135.0/24152.111.136.0/24152.111.137.0/24152.111.139.0/24152.111.142.0/24152.111.143.0/24152.111.144.0/24152.111.145.0/24152.111.146.0/24152.111.148.0/23152.111.151.0/24152.111.154.0/23152.111.159.0/24152.111.162.0/24152.111.163.0/24152.111.165.0/24152.111.166.0/24152.111.167.0/24152.111.168.0/24152.111.172.0/23152.111.174.0/23152.111.177.0/24152.111.180.0/24152.111.182.0/24152.111.183.0/24152.111.185.0/24152.111.186.0/24152.111.187.0/24152.111.188.0/24152.111.189.0/24152.111.190.0/24152.111.191.0/24152.111.192.0/24152.111.193.0/24152.111.194.0/24152.111.195.0/24152.111.196.0/24152.111.197.0/24152.111.198.0/24152.111.200.0/24152.111.203.0/24152.111.204.0/24152.111.205.0/24152.111.206.0/24152.111.207.0/24152.111.209.0/24152.111.210.0/24152.111.211.0/24152.111.212.0/24152.111.213.0/24152.111.214.0/24152.111.215.0/24152.111.216.0/24152.111.217.0/24152.111.219.0/24152.111.221.0/24152.111.223.0/24152.111.224.0/24152.111.225.0/24152.111.226.0/24152.111.229.0/24152.111.230.0/24152.111.231.0/24152.111.232.0/22152.111.232.0/24152.111.233.0/24152.111.234.0/24152.111.235.0/24152.111.238.0/24152.111.239.0/24152.111.240.0/24152.111.241.0/24152.111.242.0/24152.111.244.0/24152.111.245.0/24152.111.246.0/24152.111.247.0/24152.111.248.0/24152.111.250.0/24152.111.251.0/24152.111.252.0/24152.111.254.0/24155.240.0.0/17155.240.152.0/23156.8.251.0/24156.8.252.0/24156.8.254.0/24163.203.0.0/18163.203.64.0/18163.203.160.0/19163.203.192.0/19163.203.224.0/24168.209.97.0/24168.209.98.0/24168.209.106.0/24168.210.41.0/24168.210.128.0/17196.14.5.0/24196.14.54.0/24196.14.119.0/24196.14.144.0/24196.14.145.0/24196.14.146.0/24196.14.147.0/24

IPv6

Good
10/10

4 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 9 IX.

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

Prefix aggregation

Needs work
3/5

539 IPv4 prefixes could be summarized into 320.

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)

Note

Seen passing on 192 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 (4)

Put the badge on your website

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