bgpreport

Network · data from 2026-11-12

AS270321 B Q LEITE - SERVICOS DE COMUNICACAO

Registry name: AS270321 - POP TELECOM SOLUCOES INTELIGENTES DE TELEC LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270321, 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.
201.216.112.0/23 No ROA Nonecovered by 201.216.112.0/22 672 100% 66
201.216.115.0/24 No ROA Nonecovered by 201.216.112.0/22 667 99% 67
201.216.114.0/24 No ROA Other IRR onlyRADB 670 100% 66
201.216.113.0/24 No ROA Other IRR onlyRADB 667 99% 67
201.216.112.0/24 No ROA Other IRR onlyRADB 660 98% 67
2804:6a3c::/32 No ROA Other IRR onlyRADB 628 99% 67

AS-SET

AS270321's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none201.216.112.0/23No ROA covers it. Add a ROA for AS270321, maxLength 23.672 of 673
Route object: none201.216.112.0/23No route object for it. A route object for 201.216.112.0/22 with origin AS270321 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270321 in the RIR database for the space.672 of 673
ROA: none201.216.115.0/24No ROA covers it. Add a ROA for AS270321, maxLength 24.667 of 673
Route object: none201.216.115.0/24No route object for it. A route object for 201.216.112.0/22 with origin AS270321 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270321 in the RIR database for the space.667 of 673
ROA: none201.216.114.0/24No ROA covers it. Add a ROA for AS270321, maxLength 24.670 of 673
Route object: RIR201.216.114.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none201.216.113.0/24No ROA covers it. Add a ROA for AS270321, maxLength 24.667 of 673
Route object: RIR201.216.113.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none201.216.112.0/24No ROA covers it. Add a ROA for AS270321, maxLength 24.660 of 673
Route object: RIR201.216.112.0/24Route object only in RADB. Add it in the RIR database for the space.660 of 673
ROA: none2804:6a3c::/32No ROA covers it. Add a ROA for AS270321, maxLength 32.628 of 636
Route object: RIR2804:6a3c::/32Route object only in RADB. Add it in the RIR database for the space.628 of 636

Route objects not announced

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

201.216.112.0/22RADBNo 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.