bgpreport

Network · data from 2026-11-12

AS270572 AS270572 - ADRIANO ROSA DOS SANTOS

Registry name: AS270572 - ADRIANO ROSA DOS SANTOS, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270572, 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.
186.233.136.0/24 No ROA Nonecovered by 186.233.136.0/22 671 100% 67
186.233.137.0/24 No ROA Nonecovered by 186.233.136.0/22 670 100% 67
186.233.136.0/23 No ROA Nonecovered by 186.233.136.0/22 667 99% 67
186.233.138.0/23 No ROA Nonecovered by 186.233.136.0/22 667 99% 67
2804:6e0c::/32 No ROA Other IRR onlyALTDB, NTTCOM, RADB 633 100% 67

AS-SET

AS270572 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none186.233.136.0/24No ROA covers it. Add a ROA for AS270572, maxLength 24.671 of 673
Route object: none186.233.136.0/24No route object for it. A route object for 186.233.136.0/22 with origin AS270572 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270572 in the RIR database for the space.671 of 673
ROA: none186.233.137.0/24No ROA covers it. Add a ROA for AS270572, maxLength 24.670 of 673
Route object: none186.233.137.0/24No route object for it. A route object for 186.233.136.0/22 with origin AS270572 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270572 in the RIR database for the space.670 of 673
ROA: none186.233.136.0/23No ROA covers it. Add a ROA for AS270572, maxLength 23.667 of 673
Route object: none186.233.136.0/23No route object for it. A route object for 186.233.136.0/22 with origin AS270572 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270572 in the RIR database for the space.667 of 673
ROA: none186.233.138.0/23No ROA covers it. Add a ROA for AS270572, maxLength 23.667 of 673
Route object: none186.233.138.0/23No route object for it. A route object for 186.233.136.0/22 with origin AS270572 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270572 in the RIR database for the space.667 of 673
ROA: none2804:6e0c::/32No ROA covers it. Add a ROA for AS270572, maxLength 32.633 of 636
Route object: RIR2804:6e0c::/32Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

186.233.136.0/22ALTDB, RADBNo 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.