AwanCerahBGP
Home/Cyprus/AS8544
Autonomous System

Primetel PLC

AS8544CyprusRIPE NCC · since 1997Cable/DSL/ISPPeering: Selective

NSP-INTL

primetel.com.cy
Primetel PLC website
C64/100Fair

BGP report

Ranked 107 of 142 networks in Cyprus, 14 of 17 ISPs and transit networks. World rank 48,740.

  • RPKI ROA5/30
  • IRR route objects17/20
  • Upstream redundancy15/15
  • Global visibility7/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
5/30

28 of 184 prefixes have a matching ROA (valid). 156 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 (156)
46.21.48.0/2046.21.52.0/2446.28.176.0/2162.12.64.0/1962.12.84.0/2462.12.86.0/2462.12.89.0/2462.12.94.0/2462.152.0.0/1962.152.1.0/2462.152.2.0/2462.152.4.0/2462.152.5.0/2462.152.6.0/2462.152.7.0/2462.152.9.0/2462.152.11.0/2462.152.14.0/2462.152.15.0/2462.152.16.0/2462.152.17.0/2462.152.20.0/2462.152.21.0/2462.152.22.0/2462.152.23.0/2462.152.24.0/2462.152.27.0/2462.152.28.0/2462.152.29.0/2462.152.30.0/2462.152.31.0/2478.158.128.0/1978.158.128.0/2478.158.133.0/2478.158.134.0/2478.158.141.0/2478.158.143.0/2478.158.146.0/2478.158.148.0/2478.158.150.0/2478.158.151.0/2478.158.156.0/2481.21.32.0/2081.21.38.0/2481.21.41.0/2481.21.46.0/2482.102.64.0/1882.102.65.0/2482.102.68.0/2482.102.69.0/2482.102.71.0/2482.102.75.0/2482.102.81.0/2482.102.82.0/2482.102.83.0/2482.102.84.0/2482.102.85.0/2482.102.86.0/2482.102.87.0/2482.102.89.0/2482.102.90.0/2482.102.91.0/2482.102.92.0/2482.102.94.0/2482.102.97.0/2482.102.99.0/2482.102.100.0/2482.102.104.0/2482.102.105.0/2482.102.106.0/2482.102.107.0/2482.102.109.0/2482.102.110.0/2482.102.111.0/2482.102.114.0/2482.102.115.0/2482.102.116.0/2482.102.118.0/2482.102.119.0/2482.102.120.0/2482.102.121.0/2482.102.122.0/2482.102.125.0/2482.102.126.0/2482.102.127.0/24109.105.224.0/19109.105.224.0/24109.105.229.0/24109.105.230.0/24109.105.237.0/24109.105.238.0/24109.105.241.0/24109.105.242.0/24109.105.246.0/24109.105.247.0/24109.105.248.0/24109.105.249.0/24109.105.251.0/24109.105.252.0/24109.105.255.0/24185.78.128.0/22185.78.131.0/24185.166.116.0/22185.166.116.0/24185.166.117.0/24185.166.118.0/24185.166.119.0/24185.175.40.0/22185.175.40.0/24185.175.41.0/24185.175.42.0/24185.175.43.0/24194.42.128.0/19194.42.139.0/24194.42.146.0/24194.42.148.0/24194.42.153.0/24194.42.156.0/24194.42.158.0/24194.154.142.0/24194.154.143.0/24194.154.144.0/24194.154.147.0/24194.154.156.0/24194.154.158.0/24217.16.224.0/20217.16.226.0/24217.16.232.0/24217.16.234.0/24217.27.32.0/19217.27.32.0/21217.27.44.0/22217.27.45.0/24217.27.46.0/24217.27.48.0/20217.175.208.0/20217.175.208.0/24217.175.210.0/24217.175.211.0/24217.175.212.0/24217.175.214.0/24217.175.215.0/24217.175.216.0/24217.175.217.0/24217.175.218.0/24217.175.219.0/24217.175.220.0/24217.175.221.0/24217.175.222.0/24217.175.223.0/242a00:1ec0::/322a00:1ec0::/482a00:1ec0::/562a00:1ec0:3000::/362a00:1ec0:3002::/482a00:1ec0:3003::/48

IRR route objects

Needs work
17/20

98 prefixes have an exact route object, 77 are covered by a larger one, 9 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 (9)
Covered by a larger object (77)

IPv6

Good
10/10

6 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 4 IX.

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

Prefix aggregation

Problem
0/5

178 IPv4 prefixes could be summarized into 22.

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)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

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

Put the badge on your website

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