AwanCerahBGP
Home/Brazil/AS264993
Autonomous System

NETLIDERES - PROVEDOR DE INTERNET EIRELI

AS264993BrazilLACNIC · since 2016NSPPeering: Open

AS264993

netlideres.com.br
NETLIDERES - PROVEDOR DE INTERNET EIRELI website
A94/100Excellent

BGP report

Ranked 579 of 8,802 networks in Brazil, 315 of 2,507 ISPs and transit networks. World rank 6,798.

  • RPKI ROA30/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB9/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

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

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

Upstream redundancy

Good
15/15

8 upstream, 39 peer, 1 downstream.

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

Upstream (8)

Global visibility

Good
10/10

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

IPv6

Good
10/10

3 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
9/10

Profile exists, listed at 1 IX. Missing: prefix counts.

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.

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