AwanCerahBGP
Home/Brazil/AS53237
Autonomous System

TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS

AS53237BrazilLACNIC · since 2010NSPPeering: Selective

AS53237

telebras.com.br
TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS website
C58/100Fair

BGP report

Ranked 5,301 of 8,803 networks in Brazil, 1,940 of 2,502 ISPs and transit networks. World rank 57,134.

  • RPKI ROA0/30
  • IRR route objects17/20
  • Upstream redundancy15/15
  • Global visibility7/10
  • IPv610/10
  • PeeringDB8/10
  • Prefix aggregation1/5

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

Score history

Global visibility

Needs work
7/10

37 of 55 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 (18)

IPv6

Good
10/10

17 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
8/10

Profile exists, listed at 4 IX. Missing: IRR as-set.

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

38 IPv4 prefixes could be summarized into 8.

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)

Note

Seen passing on 1 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

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

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (1)

Put the badge on your website

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