bgpreport

Network · data from 2026-11-12

AS269271 AS269271 - SERGIO BATISTA CARDOZO ME

Registry name: AS269271 - SERGIO BATISTA CARDOZO ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269271, 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.180.118.0/23 No ROA Other IRR onlyALTDB 673 100% 67
45.180.116.0/23 No ROA Other IRR onlyALTDB 671 100% 66
45.180.116.0/24 No ROA Other IRR onlyALTDB 671 100% 66
45.180.117.0/24 No ROA Other IRR onlyALTDB 671 100% 66
45.180.118.0/24 No ROA Other IRR onlyALTDB 196 29% 54
45.180.119.0/24 No ROA Other IRR onlyALTDB 196 29% 54

AS-SET

AS269271 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 14 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.180.118.0/23No ROA covers it. Add a ROA for AS269271, maxLength 23.673 of 673
Route object: RIR45.180.118.0/23Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none45.180.116.0/23No ROA covers it. Add a ROA for AS269271, maxLength 23.671 of 673
Route object: RIR45.180.116.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none45.180.116.0/24No ROA covers it. Add a ROA for AS269271, maxLength 24.671 of 673
Route object: RIR45.180.116.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none45.180.117.0/24No ROA covers it. Add a ROA for AS269271, maxLength 24.671 of 673
Route object: RIR45.180.117.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none45.180.118.0/24No ROA covers it. Add a ROA for AS269271, maxLength 24.196 of 673
Route object: RIR45.180.118.0/24Route object only in ALTDB. Add it in the RIR database for the space.196 of 673
ROA: none45.180.119.0/24No ROA covers it. Add a ROA for AS269271, maxLength 24.196 of 673
Route object: RIR45.180.119.0/24Route object only in ALTDB. Add it in the RIR database for the space.196 of 673

Route objects not announced

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

45.180.116.0/22ALTDB, RADBNo ROA
2804:6204::/32ALTDB, 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.