bgpreport

Network · data from 2026-11-12

AS263090 m.n. dos santos informatica

Registry name: AS263090 - m.n. dos santos informatica, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263090, 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.250.78.0/23 No ROA Nonecovered by 186.250.76.0/22 669 99% 67
201.150.90.0/23 No ROA Nonecovered by 201.150.88.0/22 669 99% 66
201.150.88.0/24 No ROA Nonecovered by 201.150.88.0/22 667 99% 67
186.250.76.0/23 No ROA Nonecovered by 186.250.76.0/22 666 99% 67
201.150.88.0/23 No ROA Nonecovered by 201.150.88.0/22 142 21% 49
186.250.72.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
186.250.76.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
201.150.88.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
186.250.72.0/23 No ROA Other IRR onlyRADB 668 99% 67
186.250.74.0/23 No ROA Other IRR onlyRADB 668 99% 66
2804:1974::/32 No ROA Other IRR onlyNTTCOM, RADB 632 99% 67

AS-SET

AS263090'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 22 are in fix.csv.

  • ROA: none11
  • Route object: none5
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none186.250.78.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.669 of 673
Route object: none186.250.78.0/23No route object for it. A route object for 186.250.76.0/22 with origin AS263090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263090 in the RIR database for the space.669 of 673
ROA: none201.150.90.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.669 of 673
Route object: none201.150.90.0/23No route object for it. A route object for 201.150.88.0/22 with origin AS263090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263090 in the RIR database for the space.669 of 673
ROA: none201.150.88.0/24No ROA covers it. Add a ROA for AS263090, maxLength 24.667 of 673
Route object: none201.150.88.0/24No route object for it. A route object for 201.150.88.0/22 with origin AS263090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263090 in the RIR database for the space.667 of 673
ROA: none186.250.76.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.666 of 673
Route object: none186.250.76.0/23No route object for it. A route object for 186.250.76.0/22 with origin AS263090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263090 in the RIR database for the space.666 of 673
ROA: none201.150.88.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.142 of 673
Route object: none201.150.88.0/23No route object for it. A route object for 201.150.88.0/22 with origin AS263090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263090 in the RIR database for the space.142 of 673
ROA: none186.250.72.0/22No ROA covers it. Add a ROA for AS263090, maxLength 22.671 of 673
Route object: RIR186.250.72.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.76.0/22No ROA covers it. Add a ROA for AS263090, maxLength 22.671 of 673
Route object: RIR186.250.76.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none201.150.88.0/22No ROA covers it. Add a ROA for AS263090, maxLength 22.671 of 673
Route object: RIR201.150.88.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.72.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.668 of 673
Route object: RIR186.250.72.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none186.250.74.0/23No ROA covers it. Add a ROA for AS263090, maxLength 23.668 of 673
Route object: RIR186.250.74.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:1974::/32No ROA covers it. Add a ROA for AS263090, maxLength 32.632 of 636
Route object: RIR2804:1974::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS263090 is announced.

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.