AwanCerahBGP
Home/Argentina/AS262189
Autonomous System

Cooperativa Regional de Servicios

AS262189ArgentinaLACNIC · since 2011Cable/DSL/ISPPeering: Open

AS262189

B73/100Good

BGP report

Ranked 614 of 1,098 networks in Argentina. World rank 36,507.

  • RPKI ROA30/30
  • IRR route objects15/20
  • Upstream redundancy15/15
  • Global visibility2/10
  • IPv60/10
  • PeeringDB10/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Good
30/30

16 of 16 prefixes have a matching ROA (valid). 0 without a ROA.

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

IRR route objects

Needs work
15/20

2 prefixes have an exact route object, 13 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 (13)

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

Problem
2/10

3 of 16 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 (13)

IPv6

Problem
0/10

No IPv6 prefix is announced.

Most mobile users and large services already run on IPv6.

How to fix
  1. Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.

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
1/5

16 IPv4 prefixes could be summarized into 3.

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