AwanCerahBGP
Home/Colombia/AS10620
Autonomous System

Telmex Colombia S.A.

AS10620ColombiaLACNIC · since 1997

AS10620

B74/100Good

BGP report

Ranked 259 of 440 networks in Colombia. World rank 36,015.

  • RPKI ROA30/30
  • IRR route objects16/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/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

3,587 of 3,587 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
16/20

550 prefixes have an exact route object, 3,037 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 (3037)
181.50.32.0/24181.50.33.0/24181.50.52.0/22181.50.64.0/24181.50.65.0/24181.50.66.0/24181.50.67.0/24181.50.68.0/24181.50.88.0/22181.50.93.0/24181.50.97.0/24181.50.98.0/24181.50.100.0/24181.50.101.0/24181.50.123.0/24181.50.136.0/22181.50.140.0/23181.50.142.0/23181.50.188.0/22181.50.224.0/22181.51.4.0/22181.51.8.0/24181.51.9.0/24181.51.14.0/23181.51.16.0/24181.51.19.0/24181.51.24.0/21181.51.36.0/24181.51.37.0/24181.51.38.0/24181.51.39.0/24181.51.44.0/23181.51.50.0/23181.51.58.0/24181.51.59.0/24181.51.60.0/24181.51.61.0/24181.51.62.0/24181.51.70.0/23181.51.80.0/22181.51.84.0/22181.51.88.0/24181.51.89.0/24181.51.90.0/24181.51.91.0/24181.51.100.0/22181.51.104.0/24181.51.105.0/24181.51.106.0/24181.51.107.0/24181.51.108.0/22181.51.122.0/23181.51.124.0/22181.51.144.0/22181.51.169.0/24181.51.170.0/24181.51.180.0/22181.51.184.0/24181.51.204.0/22181.51.212.0/24181.51.214.0/24181.51.215.0/24181.51.220.0/22181.51.240.0/22181.51.246.0/24181.51.250.0/24181.51.251.0/24181.51.252.0/24181.51.253.0/24181.52.0.0/23181.52.2.0/23181.52.5.0/24181.52.12.0/22181.52.24.0/22181.52.44.0/22181.52.48.0/22181.52.56.0/22181.52.76.0/22181.52.84.0/22181.52.117.0/24181.52.118.0/24181.52.122.0/24181.52.124.0/24181.52.132.0/22181.52.136.0/24181.52.137.0/24181.52.140.0/23181.52.144.0/22181.52.152.0/23181.52.160.0/22181.52.172.0/24181.52.216.0/24181.52.217.0/24181.52.224.0/22181.52.236.0/24181.52.239.0/24181.52.240.0/24181.52.241.0/24181.52.242.0/24181.52.248.0/24181.52.249.0/24181.52.255.0/24181.53.0.0/22181.53.16.0/24181.53.18.0/24181.53.19.0/24181.53.20.0/22181.53.24.0/24181.53.29.0/24181.53.31.0/24181.53.48.0/22181.53.63.0/24181.53.68.0/24181.53.96.0/24181.53.99.0/24181.53.128.0/22181.53.140.0/24181.53.141.0/24181.53.142.0/24181.53.156.0/22181.53.160.0/22181.53.172.0/22181.53.180.0/24181.53.181.0/24181.53.182.0/24181.53.183.0/24181.53.224.0/24181.53.225.0/24181.53.226.0/24181.53.227.0/24181.53.228.0/22181.53.251.0/24181.53.255.0/24181.54.4.0/23181.54.6.0/23181.54.28.0/22181.54.32.0/22181.54.36.0/22181.54.40.0/22181.54.44.0/22181.54.52.0/22181.54.56.0/22181.54.60.0/22181.54.64.0/22181.54.73.0/24181.54.92.0/22181.54.97.0/24181.54.98.0/24181.54.99.0/24181.54.100.0/22181.54.104.0/22181.54.135.0/24181.54.136.0/22181.54.140.0/22181.54.144.0/22181.54.167.0/24181.54.188.0/22181.54.196.0/22181.54.213.0/24181.54.214.0/24181.54.215.0/24181.54.252.0/24181.55.16.0/22181.55.28.0/22181.55.32.0/22181.55.40.0/22181.55.44.0/22181.55.48.0/22181.55.52.0/22181.55.57.0/24181.55.64.0/22181.55.72.0/24181.55.96.0/22181.55.101.0/24181.55.108.0/22181.55.116.0/22181.55.123.0/24181.55.156.0/22181.55.160.0/22181.55.164.0/22181.55.176.0/22181.55.180.0/22181.55.184.0/22181.55.188.0/24181.55.189.0/24181.55.190.0/24181.55.191.0/24181.55.232.0/24181.55.233.0/24181.55.235.0/24181.55.240.0/24181.55.243.0/24181.55.252.0/24181.55.253.0/24181.56.0.0/22181.56.4.0/22181.56.8.0/24181.56.9.0/24181.56.10.0/24181.56.11.0/24

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

IPv6

Good
10/10

150 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Problem
0/10

No PeeringDB profile.

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

3,437 IPv4 prefixes could be summarized into 1,110.

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