AwanCerahBGP
Home/Brazil/AS61908
Autonomous System

Nova Net Telecomunicacoes Ltda

AS61908BrazilLACNIC · since 2014

AS61908

B74/100Good

BGP report

Ranked 3,523 of 8,802 networks in Brazil. World rank 36,074.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy7/15
  • Global visibility4/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Good
30/30

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

13 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

Problem
7/15

1 upstream, 0 peer, 0 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Problem
4/10

5 of 13 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 (8)

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Problem
0/10

No PeeringDB profile.

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

Needs work
3/5

12 IPv4 prefixes could be summarized into 4.

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