bgpreport

Network · data from 2026-11-12

AS262363 AS262363 - VITUAX BRASIL LTDA

Registry name: AS262363 - VITUAX BRASIL LTDA, BR · not in PeeringDB

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

Announced routes

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

177.126.240.0/21 No ROA Nonecovered by 177.126.240.0/20 671 100% 67
177.126.248.0/23 No ROA Nonecovered by 177.126.240.0/20 671 100% 67
177.126.252.0/22 No ROA Nonecovered by 177.126.240.0/20 670 100% 67
177.126.241.0/24 No ROA Nonecovered by 177.126.240.0/20 2 0%low visibility 2
177.126.246.0/24 No ROA Nonecovered by 177.126.240.0/20 2 0%low visibility 2
177.126.253.0/24 No ROA Nonecovered by 177.126.240.0/20 2 0%low visibility 2
177.126.254.0/24 No ROA Nonecovered by 177.126.240.0/20 2 0%low visibility 2
177.126.240.0/22 No ROA Nonecovered by 177.126.240.0/20 0 0%low visibility 1
177.126.244.0/22 No ROA Nonecovered by 177.126.240.0/20 0 0%low visibility 1
2804:84c::/32 No ROA Other IRR onlyRADB 636 100% 67
177.126.250.0/23 No ROA Other IRR onlyRADB 286 42% 61
177.126.240.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.242.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.244.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.245.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.247.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.252.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
177.126.255.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS262363 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 38 are in fix.csv.

  • ROA: none18
  • Route object: none9
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none177.126.240.0/21No ROA covers it. Add a ROA for AS262363, maxLength 21.671 of 673
Route object: none177.126.240.0/21No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.671 of 673
ROA: none177.126.248.0/23No ROA covers it. Add a ROA for AS262363, maxLength 23.671 of 673
Route object: none177.126.248.0/23No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.671 of 673
ROA: none177.126.252.0/22No ROA covers it. Add a ROA for AS262363, maxLength 22.670 of 673
Route object: none177.126.252.0/22No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.670 of 673
ROA: none177.126.241.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: none177.126.241.0/24No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.2 of 673
ROA: none177.126.246.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: none177.126.246.0/24No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.2 of 673
ROA: none177.126.253.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: none177.126.253.0/24No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.2 of 673
ROA: none177.126.254.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: none177.126.254.0/24No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.2 of 673
ROA: none177.126.240.0/22No ROA covers it. Add a ROA for AS262363, maxLength 22.0 of 673
Route object: none177.126.240.0/22No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.0 of 673
ROA: none177.126.244.0/22No ROA covers it. Add a ROA for AS262363, maxLength 22.0 of 673
Route object: none177.126.244.0/22No route object for it. A route object for 177.126.240.0/20 with origin AS262363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262363 in the RIR database for the space.0 of 673
ROA: none2804:84c::/32No ROA covers it. Add a ROA for AS262363, maxLength 32.636 of 636
Route object: RIR2804:84c::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none177.126.250.0/23No ROA covers it. Add a ROA for AS262363, maxLength 23.286 of 673
Route object: RIR177.126.250.0/23Route object only in RADB. Add it in the RIR database for the space.286 of 673
ROA: none177.126.240.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.240.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.242.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.242.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.244.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.244.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.245.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.245.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.247.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.247.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.252.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.252.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.126.255.0/24No ROA covers it. Add a ROA for AS262363, maxLength 24.2 of 673
Route object: RIR177.126.255.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

177.126.240.0/20BBOI, RADBNo ROA
177.126.243.0/24RADBNo 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.