bgpreport

Network · data from 2026-11-12

AS263671 MINASINFO LTDA-ME

Registry name: AS263671 - MINAS INFO LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263671, 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.

143.208.140.0/22 No ROA Other IRR onlyRADB 668 99% 66
191.241.129.0/24 No ROA Other IRR onlyRADB 667 99% 66
191.241.132.0/24 No ROA Other IRR onlyRADB 667 99% 66
191.241.135.0/24 No ROA Other IRR onlyRADB 667 99% 66
191.241.128.0/21 No ROA Other IRR onlyRADB 666 99% 66

AS-SET

AS263671'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 19 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none143.208.140.0/22No ROA covers it. Add a ROA for AS263671, maxLength 22.668 of 673
Route object: RIR143.208.140.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none191.241.129.0/24No ROA covers it. Add a ROA for AS263671, maxLength 24.667 of 673
Route object: RIR191.241.129.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none191.241.132.0/24No ROA covers it. Add a ROA for AS263671, maxLength 24.667 of 673
Route object: RIR191.241.132.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none191.241.135.0/24No ROA covers it. Add a ROA for AS263671, maxLength 24.667 of 673
Route object: RIR191.241.135.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none191.241.128.0/21No ROA covers it. Add a ROA for AS263671, maxLength 21.666 of 673
Route object: RIR191.241.128.0/21Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

143.208.140.0/23RADBNo ROA
143.208.142.0/23RADBNo ROA
191.241.128.0/23RADBNo ROA
191.241.130.0/23RADBNo ROA
191.241.132.0/23RADBNo ROA
191.241.134.0/23RADBNo ROA
2804:1154::/32RADBNo ROA
2804:1154::/33RADBNo ROA
2804:1154:8000::/33RADBNo 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.