bgpreport

Network · data from 2026-11-12

AS269707 AS269707 - Prata Telecom

Registry name: AS269707 - Prata Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269707, 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.
45.191.160.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
45.191.160.0/23 No ROA Other IRR onlyTC 670 100% 67
45.191.162.0/23 No ROA Other IRR onlyTC 670 100% 67
2804:68a8::/32 No ROA Other IRR onlyTC 636 100% 67
2804:68a8::/33 No ROA Other IRR onlyTC 636 100% 67
2804:68a8:8000::/33 No ROA Other IRR onlyTC 636 100% 67
45.191.160.0/24 No ROA Other IRR onlyTC 6 1%low visibility 4
45.191.161.0/24 No ROA Other IRR onlyTC 6 1%low visibility 4
45.191.162.0/24 No ROA Other IRR onlyTC 6 1%low visibility 4
45.191.163.0/24 No ROA Other IRR onlyTC 6 1%low visibility 4

AS-SET

AS269707 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 20 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none45.191.160.0/22No ROA covers it. Add a ROA for AS269707, maxLength 22.671 of 673
Route object: RIR45.191.160.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.191.160.0/23No ROA covers it. Add a ROA for AS269707, maxLength 23.670 of 673
Route object: RIR45.191.160.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none45.191.162.0/23No ROA covers it. Add a ROA for AS269707, maxLength 23.670 of 673
Route object: RIR45.191.162.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:68a8::/32No ROA covers it. Add a ROA for AS269707, maxLength 32.636 of 636
Route object: RIR2804:68a8::/32Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:68a8::/33No ROA covers it. Add a ROA for AS269707, maxLength 33.636 of 636
Route object: RIR2804:68a8::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:68a8:8000::/33No ROA covers it. Add a ROA for AS269707, maxLength 33.636 of 636
Route object: RIR2804:68a8:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none45.191.160.0/24No ROA covers it. Add a ROA for AS269707, maxLength 24.6 of 673
Route object: RIR45.191.160.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
ROA: none45.191.161.0/24No ROA covers it. Add a ROA for AS269707, maxLength 24.6 of 673
Route object: RIR45.191.161.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
ROA: none45.191.162.0/24No ROA covers it. Add a ROA for AS269707, maxLength 24.6 of 673
Route object: RIR45.191.162.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673
ROA: none45.191.163.0/24No ROA covers it. Add a ROA for AS269707, maxLength 24.6 of 673
Route object: RIR45.191.163.0/24Route object only in TC. Add it in the RIR database for the space.6 of 673

Route objects not announced

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