bgpreport

Network · data from 2026-11-12

AS269470 AS269470 - DS PROVEDOR DE ACESSO AS REDES DE COMUNIC. LTDA M

Registry name: AS269470 - DS PROVEDOR DE ACESSO AS REDES DE COMUNIC. LTDA M, BR · not in PeeringDB

4IPv4 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
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
31Route objects not announced registered with origin AS269470, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269470, 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.187.72.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
45.187.72.0/23 No ROA Other IRR onlyRADB, TC 671 100% 67
45.187.75.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
45.187.74.0/23 No ROA Other IRR onlyRADB, TC 664 99% 67
2804:6520::/32 No ROA Other IRR onlyRADB, TC 636 100% 67
2804:6520::/33 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:6520:8000::/33 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS269470 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 45 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none45.187.72.0/22No ROA covers it. Add a ROA for AS269470, maxLength 22.672 of 673
Route object: RIR45.187.72.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.187.72.0/23No ROA covers it. Add a ROA for AS269470, maxLength 23.671 of 673
Route object: RIR45.187.72.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.187.75.0/24No ROA covers it. Add a ROA for AS269470, maxLength 24.671 of 673
Route object: RIR45.187.75.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.187.74.0/23No ROA covers it. Add a ROA for AS269470, maxLength 23.664 of 673
Route object: RIR45.187.74.0/23Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
ROA: none2804:6520::/32No ROA covers it. Add a ROA for AS269470, maxLength 32.636 of 636
Route object: RIR2804:6520::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:6520::/33No ROA covers it. Add a ROA for AS269470, maxLength 33.631 of 636
Route object: RIR2804:6520::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:6520:8000::/33No ROA covers it. Add a ROA for AS269470, maxLength 33.631 of 636
Route object: RIR2804:6520:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

Route objects with origin AS269470 whose prefix no peer sees AS269470 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.187.72.0/24RADB, TCNo ROA
45.187.73.0/24RADB, TCNo ROA
45.187.74.0/24RADB, TCNo ROA
2804:6520::/34RADB, TCNo ROA
2804:6520::/35RADBNo ROA
2804:6520::/36RADBNo ROA
2804:6520:1000::/36RADBNo ROA
2804:6520:2000::/35RADBNo ROA
2804:6520:2000::/36RADBNo ROA
2804:6520:3000::/36RADBNo ROA
2804:6520:4000::/34RADB, TCNo ROA
2804:6520:4000::/35RADBNo ROA
2804:6520:4000::/36RADBNo ROA
2804:6520:5000::/36RADBNo ROA
2804:6520:6000::/35RADBNo ROA
2804:6520:6000::/36RADBNo ROA
2804:6520:7000::/36RADBNo ROA
2804:6520:8000::/34RADB, TCNo ROA
2804:6520:8000::/35RADBNo ROA
2804:6520:8000::/36RADBNo ROA
2804:6520:9000::/36RADBNo ROA
2804:6520:a000::/35RADBNo ROA
2804:6520:a000::/36RADBNo ROA
2804:6520:b000::/36RADBNo ROA
2804:6520:c000::/34RADB, TCNo ROA
2804:6520:c000::/35RADBNo ROA
2804:6520:c000::/36RADBNo ROA
2804:6520:d000::/36RADBNo ROA
2804:6520:e000::/35RADBNo ROA
2804:6520:e000::/36RADBNo ROA
2804:6520:f000::/36RADBNo ROA

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.