bgpreport

Network · data from 2026-11-12

AS266927 BINARIO CLOUD

Registry name: AS266927 - BINARIO CLOUD SER DE COMPUTACAO E INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

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

185.238.30.0/24 No ROA Other origin only 672 100% 67
200.218.224.0/22 No ROA None 671 100% 67
200.218.224.0/24 No ROA None 671 100% 67
200.218.225.0/24 No ROA None 671 100% 67
200.218.226.0/24 No ROA None 671 100% 67
200.218.227.0/24 No ROA None 671 100% 67
2804:4574::/48 No ROA Nonecovered by 2804:4574::/32 354 56% 65
2804:4574:101::/48 No ROA Nonecovered by 2804:4574::/32 354 56% 65
45.225.24.0/22 No ROA Other IRR onlyTC 672 100% 67
45.225.24.0/24 No ROA Other IRR onlyTC 671 100% 67
45.225.25.0/24 No ROA Other IRR onlyTC 671 100% 67
45.225.26.0/24 No ROA Other IRR onlyTC 671 100% 67
45.225.27.0/24 No ROA Other IRR onlyTC 671 100% 67
2804:4574::/32 No ROA Other IRR onlyTC 635 100% 67

AS-SET

AS266927'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 30 are in fix.csv.

  • ROA: none14
  • Route object: none8
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.238.30.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.672 of 673
Route object: none185.238.30.0/24Route objects for it name AS271521. Add a route object with origin AS266927 in the RIR database for the space.672 of 673
ROA: none200.218.224.0/22No ROA covers it. Add a ROA for AS266927, maxLength 22.671 of 673
Route object: none200.218.224.0/22No route object for it. Add a route object with origin AS266927 in the RIR database for the space.671 of 673
ROA: none200.218.224.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: none200.218.224.0/24No route object for it. Add a route object with origin AS266927 in the RIR database for the space.671 of 673
ROA: none200.218.225.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: none200.218.225.0/24No route object for it. Add a route object with origin AS266927 in the RIR database for the space.671 of 673
ROA: none200.218.226.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: none200.218.226.0/24No route object for it. Add a route object with origin AS266927 in the RIR database for the space.671 of 673
ROA: none200.218.227.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: none200.218.227.0/24No route object for it. Add a route object with origin AS266927 in the RIR database for the space.671 of 673
ROA: none2804:4574::/48No ROA covers it. Add a ROA for AS266927, maxLength 48.354 of 636
Route object: none2804:4574::/48No route object for it. A route object for 2804:4574::/32 with origin AS266927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266927 in the RIR database for the space.354 of 636
ROA: none2804:4574:101::/48No ROA covers it. Add a ROA for AS266927, maxLength 48.354 of 636
Route object: none2804:4574:101::/48No route object for it. A route object for 2804:4574::/32 with origin AS266927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266927 in the RIR database for the space.354 of 636
ROA: none45.225.24.0/22No ROA covers it. Add a ROA for AS266927, maxLength 22.672 of 673
Route object: RIR45.225.24.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none45.225.24.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: RIR45.225.24.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.225.25.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: RIR45.225.25.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.225.26.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: RIR45.225.26.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.225.27.0/24No ROA covers it. Add a ROA for AS266927, maxLength 24.671 of 673
Route object: RIR45.225.27.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:4574::/32No ROA covers it. Add a ROA for AS266927, maxLength 32.635 of 636
Route object: RIR2804:4574::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.225.24.0/23TCNo ROA
45.225.26.0/23TCNo 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.