bgpreport

Network · data from 2026-11-12

AS265902 AS265902 - VLZ TECNOLOGIAS EIRELI

Registry name: AS265902 - VLZ TECNOLOGIAS EIRELI, BR · not in PeeringDB

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

Announced routes

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

128.201.214.0/23 No ROA Nonecovered by 128.201.212.0/22 669 99% 66
2804:3f9c::/33 No ROA Nonecovered by 2804:3f9c::/32 635 100% 67
2804:3f9c:8000::/33 No ROA Nonecovered by 2804:3f9c::/32 635 100% 67
128.201.212.0/22 No ROA Other IRR onlyBBOI, RADB, TC 672 100% 66
128.201.212.0/23 No ROA Other IRR onlyRADB 669 99% 66
2804:3f9c::/32 No ROA Other IRR onlyBBOI, RADB, TC 634 100% 67

AS-SET

AS265902 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 23 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none128.201.214.0/23No ROA covers it. Add a ROA for AS265902, maxLength 23.669 of 673
Route object: none128.201.214.0/23No route object for it. A route object for 128.201.212.0/22 with origin AS265902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265902 in the RIR database for the space.669 of 673
ROA: none2804:3f9c::/33No ROA covers it. Add a ROA for AS265902, maxLength 33.635 of 636
Route object: none2804:3f9c::/33No route object for it. A route object for 2804:3f9c::/32 with origin AS265902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265902 in the RIR database for the space.635 of 636
ROA: none2804:3f9c:8000::/33No ROA covers it. Add a ROA for AS265902, maxLength 33.635 of 636
Route object: none2804:3f9c:8000::/33No route object for it. A route object for 2804:3f9c::/32 with origin AS265902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265902 in the RIR database for the space.635 of 636
ROA: none128.201.212.0/22No ROA covers it. Add a ROA for AS265902, maxLength 22.672 of 673
Route object: RIR128.201.212.0/22Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none128.201.212.0/23No ROA covers it. Add a ROA for AS265902, maxLength 23.669 of 673
Route object: RIR128.201.212.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:3f9c::/32No ROA covers it. Add a ROA for AS265902, maxLength 32.634 of 636
Route object: RIR2804:3f9c::/32Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

128.201.212.0/24BBOINo ROA
128.201.213.0/24BBOINo ROA
128.201.214.0/24BBOINo ROA
128.201.215.0/24BBOINo ROA
2804:3f9c::/44RADBNo ROA
2804:3f9c::/48BBOINo ROA
2804:3f9c:1::/48BBOINo ROA
2804:3f9c:10::/44RADBNo ROA
2804:3f9c:20::/44RADBNo ROA
2804:3f9c:f0::/44RADBNo ROA
2804:3f9c:100::/44RADBNo 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.