AwanCerahBGP
Home/Brazil/AS267321
Autonomous System

NTISP TELECOM

AS267321BrazilLACNIC · since 2018Peering: Open

AS267321

B83/100Good

BGP report

Ranked 2,748 of 8,802 networks in Brazil, 1,214 of 2,502 ISPs and transit networks. World rank 20,342.

  • RPKI ROA30/30
  • IRR route objects18/20
  • Upstream redundancy15/15
  • Global visibility3/10
  • IPv610/10
  • PeeringDB7/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

8 of 8 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
18/20

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

Upstream redundancy

Good
15/15

13 upstream, 38 peer, 2 downstream.

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

Upstream (13)

Global visibility

Problem
3/10

2 of 8 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

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
7/10

Profile exists. Missing: IX connections, 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
0/5

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