AwanCerahBGP
Home/Brazil/AS28233
Autonomous System

I-CONECTA REDES DE TELECOMUNICACAO EIRELI EPP

AS28233BrazilLACNIC · since 2008Cable/DSL/ISPPeering: Open

AS28233

entre.net.br
I-CONECTA REDES DE TELECOMUNICACAO EIRELI EPP website
A87/100Excellent

BGP report

Ranked 2,098 of 8,802 networks in Brazil. World rank 16,203.

  • RPKI ROA30/30
  • IRR route objects16/20
  • Upstream redundancy15/15
  • Global visibility8/10
  • IPv610/10
  • PeeringDB8/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Good
30/30

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

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

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

Upstream (2)

Global visibility

Needs work
8/10

33 of 39 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

9 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
8/10

Profile exists, listed at 1 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
0/5

30 IPv4 prefixes could be summarized into 2.

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