AwanCerahBGP
Home/Brazil/AS61621
Autonomous System

Norte.Net Telecomunicacoes Ltda

AS61621BrazilLACNIC · since 2024NSPPeering: Restrictive

AS61621

A91/100Excellent

BGP report

Ranked 1,099 of 8,802 networks in Brazil, 526 of 2,502 ISPs and transit networks. World rank 9,249.

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

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

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

Upstream redundancy

Good
15/15

13 upstream, 1,627 peer, 244 downstream.

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

Upstream (13)

Global visibility

Needs work
5/10

29 of 56 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 (27)

IPv6

Good
10/10

31 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
1/5

25 IPv4 prefixes could be summarized into 5.

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)

Note

Seen passing on 18 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (4)

Put the badge on your website

BGP report AS61621The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS61621/rapor"><img src="https://bgp.awancerah.cloud/en/AS61621/rapor.svg" alt="BGP report AS61621"></a>
Markdown
[![BGP report AS61621](https://bgp.awancerah.cloud/en/AS61621/rapor.svg)](https://bgp.awancerah.cloud/en/AS61621/rapor)