AwanCerahBGP
Home/Argentina/AS28073
Autonomous System

Cooperativa Electrica Trenque Lauquen

AS28073ArgentinaLACNIC · since 2009Cable/DSL/ISPPeering: Selective

AS28073

A89/100Excellent

BGP report

Ranked 147 of 1,098 networks in Argentina. World rank 13,403.

  • RPKI ROA30/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

Problem
30/30

136 of 137 prefixes have a matching ROA (valid). 1 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 (1)

IRR route objects

Good
17/20

61 prefixes have an exact route object, 76 are covered by a larger one, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

Covered by a larger object (76)

Upstream redundancy

Good
15/15

5 upstream, 0 peer, 0 downstream.

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

Upstream (5)

IPv6

Good
10/10

88 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 1 IX.

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

Prefix aggregation

Problem
0/5

49 IPv4 prefixes could be summarized into 4.

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