AwanCerahBGP
Home/Brazil/AS52688
Autonomous System

FATIMA VIDEO ELETRONICA LTDA ME

AS52688BrazilLACNIC · since 2012Cable/DSL/ISPPeering: Open

AS52688

C56/100Fair

BGP report

Ranked 5,770 of 8,802 networks in Brazil, 2,066 of 2,502 ISPs and transit networks. World rank 58,839.

  • RPKI ROA0/30
  • IRR route objects18/20
  • Upstream redundancy15/15
  • Global visibility7/10
  • IPv610/10
  • PeeringDB6/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Needs work
0/30

0 of 12 prefixes have a matching ROA (valid). 12 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. 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.
  2. 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.
Prefixes without a ROA (12)

IRR route objects

Good
18/20

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

Upstream redundancy

Good
15/15

7 upstream, 3 peer, 7 downstream.

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

Upstream (7)

Global visibility

Needs work
7/10

8 of 12 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 (4)

IPv6

Good
10/10

5 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
6/10

Profile exists. Missing: IRR as-set, IX connections.

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
0/5

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

Dropping invalid routes (ROV)

Note

Seen passing on 6 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 (4)

Put the badge on your website

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