AwanCerahBGP
Home/Brazil/AS270721
Autonomous System

3COMNECT TELECOM LTDA

AS270721BrazilLACNIC · since 2020Peering: Open

AS270721

A88/100Excellent

BGP report

Ranked 1,912 of 8,802 networks in Brazil. World rank 14,387.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility6/10
  • IPv610/10
  • PeeringDB6/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

14 of 14 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
20/20

14 prefixes have an exact route object, 0 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.

Upstream redundancy

Good
15/15

4 upstream, 1 peer, 0 downstream.

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

Upstream (4)

Global visibility

Needs work
6/10

8 of 14 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 (6)

IPv6

Good
10/10

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