AwanCerahBGP
Home/Brazil/AS267621
Autonomous System

IFIBER TELECOM

AS267621BrazilLACNIC · since 2017Cable/DSL/ISPPeering: Open

AS267621

C59/100Fair

BGP report

Ranked 5,182 of 8,802 networks in Brazil, 1,907 of 2,502 ISPs and transit networks. World rank 56,748.

  • RPKI ROA0/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility4/10
  • IPv610/10
  • PeeringDB10/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 29 prefixes have a matching ROA (valid). 29 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 (29)

IRR route objects

Good
20/20

29 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

9 upstream, 38 peer, 2 downstream.

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

Upstream (9)

Global visibility

Problem
4/10

13 of 29 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 (16)

IPv6

Good
10/10

7 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 3 IX.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

Prefix aggregation

Problem
0/5

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

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