bgpreport

Network · data from 2026-11-12

AS270323 AS270323 - TERA NETWORK TELECOMUNICACOES LTDA ME

Registry name: AS270323 - TERA NETWORK TELECOMUNICACOES LTDA ME, BR · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object
7IPv6 routes 100.0% RPKI valid · 14.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS270323, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270323, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2804:6a44::/33 Valid Nonecovered by 2804:6a44::/32 353 56% 65
2804:6a44:8000::/33 Valid Nonecovered by 2804:6a44::/32 353 56% 65
2804:6a44::/34 Valid Nonecovered by 2804:6a44::/32 335 53% 65
2804:6a44:4000::/34 Valid Nonecovered by 2804:6a44::/32 335 53% 65
2804:6a44:8000::/34 Valid Nonecovered by 2804:6a44::/32 335 53% 65
2804:6a44:c000::/34 Valid Nonecovered by 2804:6a44::/32 335 53% 65
190.83.16.0/23 Valid Nonecovered by 190.83.16.0/22 210 31% 56
190.83.18.0/23 Valid Nonecovered by 190.83.16.0/22 210 31% 56
190.83.16.0/22 Valid Other IRR onlyTC 668 99% 67
2804:6a44::/32 Valid Other IRR onlyTC 633 100% 67

AS-SET

AS270323 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2804:6a44::/33No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.353 of 636
Route object: none2804:6a44:8000::/33No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.353 of 636
Route object: none2804:6a44::/34No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.335 of 636
Route object: none2804:6a44:4000::/34No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.335 of 636
Route object: none2804:6a44:8000::/34No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.335 of 636
Route object: none2804:6a44:c000::/34No route object for it. A route object for 2804:6a44::/32 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.335 of 636
Route object: none190.83.16.0/23No route object for it. A route object for 190.83.16.0/22 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.210 of 673
Route object: none190.83.18.0/23No route object for it. A route object for 190.83.16.0/22 with origin AS270323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270323 in the RIR database for the space.210 of 673
Route object: RIR190.83.16.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:6a44::/32Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS270323 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.