AwanCerahBGP
Home/Argentina/AS52321
Autonomous System

Fideicomiso de Administracion Datacenter Capitalinas

AS52321ArgentinaLACNIC · since 2011

AS52321

B71/100Good

BGP report

Ranked 727 of 1,098 networks in Argentina. World rank 43,624.

  • RPKI ROA30/30
  • IRR route objects9/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv60/10
  • PeeringDB4/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Good
30/30

7 of 7 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
9/20

3 prefixes have an exact route object, 0 are covered by a larger one, 4 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 (4)

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

Good
10/10

7 of 7 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.

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

Needs work
4/10

Profile exists. Missing: IRR as-set, IX connections, peering policy, prefix counts.

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

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Needs work
3/5

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