bgpreport

Network · data from 2026-11-12

AS264283 AS264283 - Net Triangulo Telecom Ltda - ME

Registry name: AS264283 - Net Triangulo Telecom Ltda - ME, BR · not in PeeringDB

7IPv4 routes 28.6% RPKI valid · 42.9% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS264283, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264283, 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.
138.118.240.0/24 No ROA Nonecovered by 138.118.240.0/22 206 31% 57
138.118.241.0/24 No ROA Nonecovered by 138.118.240.0/22 206 31% 57
138.118.242.0/24 No ROA Nonecovered by 138.118.240.0/22 206 31% 57
138.118.243.0/24 No ROA Nonecovered by 138.118.240.0/22 206 31% 57
138.118.240.0/22 No ROA Other IRR onlyRADB 669 99% 66
2804:2578::/32 No ROA Other IRR onlyRADB 630 99% 67
216.28.144.0/24 Valid RIR databaseARIN 670 100% 67
206.62.88.0/21 Valid RIR databaseARIN 669 99% 66

AS-SET

AS264283 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none138.118.240.0/24No ROA covers it. Add a ROA for AS264283, maxLength 24.206 of 673
Route object: none138.118.240.0/24No route object for it. A route object for 138.118.240.0/22 with origin AS264283 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264283 in the RIR database for the space.206 of 673
ROA: none138.118.241.0/24No ROA covers it. Add a ROA for AS264283, maxLength 24.206 of 673
Route object: none138.118.241.0/24No route object for it. A route object for 138.118.240.0/22 with origin AS264283 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264283 in the RIR database for the space.206 of 673
ROA: none138.118.242.0/24No ROA covers it. Add a ROA for AS264283, maxLength 24.206 of 673
Route object: none138.118.242.0/24No route object for it. A route object for 138.118.240.0/22 with origin AS264283 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264283 in the RIR database for the space.206 of 673
ROA: none138.118.243.0/24No ROA covers it. Add a ROA for AS264283, maxLength 24.206 of 673
Route object: none138.118.243.0/24No route object for it. A route object for 138.118.240.0/22 with origin AS264283 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264283 in the RIR database for the space.206 of 673
ROA: none138.118.240.0/22No ROA covers it. Add a ROA for AS264283, maxLength 22.669 of 673
Route object: RIR138.118.240.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:2578::/32No ROA covers it. Add a ROA for AS264283, maxLength 32.630 of 636
Route object: RIR2804:2578::/32Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

Every route object with origin AS264283 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.