AwanCerahBGP
Home/Andorra/AS6752
Autonomous System

ANDORRA TELECOM, S.A.U.

AS6752AndorraRIPE NCC · since 1996NSPPeering: Open

ANDORRA

A90/100Excellent

BGP report

Ranked 2 of 3 networks in Andorra. World rank 10,463.

  • RPKI ROA29/30
  • IRR route objects19/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

Problem
29/30

161 of 163 prefixes have a matching ROA (valid). 2 invalid, 0 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 (2)

IRR route objects

Needs work
19/20

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

Upstream redundancy

Good
15/15

12 upstream, 3 peer, 0 downstream.

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

Upstream (12)

IPv6

Good
10/10

2 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

161 IPv4 prefixes could be summarized into 23.

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