AwanCerahBGP
Home/Argentina/AS264607
Autonomous System

ASOCIACION CIVIL ALTERMUNDI

AS264607ArgentinaLACNIC · since 2015

AS264607

A87/100Excellent

BGP report

Ranked 198 of 1,098 networks in Argentina. World rank 16,485.

  • RPKI ROA30/30
  • IRR route objects17/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB4/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

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

Good
17/20

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

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

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

Upstream (2)

Global visibility

Good
10/10

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

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

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

Problem
1/5

4 IPv4 prefixes could be summarized into 1.

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