AwanCerahBGP
Home/Mexico/AS28512
Autonomous System

Cablemas Telecomunicaciones SA de CV

AS28512MexicoLACNIC · since 2005

AS28512

C60/100Fair

BGP report

Ranked 308 of 562 networks in Mexico, 73 of 97 ISPs and transit networks. World rank 55,181.

  • RPKI ROA14/30
  • IRR route objects17/20
  • Upstream redundancy7/15
  • Global visibility9/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Problem
14/30

72 of 118 prefixes have a matching ROA (valid). 15 invalid, 31 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 (15)
Prefixes without a ROA (31)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 1 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)

Global visibility

Needs work
9/10

103 of 118 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 (15)

IPv6

Good
10/10

46 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

Needs work
3/5

72 IPv4 prefixes could be summarized into 36.

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.

Dropping invalid routes (ROV)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

Put the badge on your website

BGP report AS28512The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS28512/rapor"><img src="https://bgp.awancerah.cloud/en/AS28512/rapor.svg" alt="BGP report AS28512"></a>
Markdown
[![BGP report AS28512](https://bgp.awancerah.cloud/en/AS28512/rapor.svg)](https://bgp.awancerah.cloud/en/AS28512/rapor)