Network · data from 2026-11-12

AS274795 AS274795 - Verteron Datacenter LTDA

Registry name: AS274795 - Verteron Datacenter LTDA, BR · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object

3IPv6 routes 0.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS274795, seen from no peer

Announced routes

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


2804:93b4::/33	No ROA	Nonecovered by 2804:93b4::/32	631 99%	67
2804:93b4:8000::/33	No ROA	Nonecovered by 2804:93b4::/32	631 99%	67
2804:93b4::/32	No ROA	Other IRR onlyALTDB, RADB	630 99%	67
38.225.221.0/24	No ROA	RIR databaseARIN	671 100%	67
38.225.236.0/24	Valid	RIR databaseARIN	671 100%	67

AS-SET

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

ROA: none4
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:93b4::/33	No ROA covers it. Add a ROA for AS274795, maxLength 33.	631 of 636
Route object: none	2804:93b4::/33	No route object for it. A route object for 2804:93b4::/32 with origin AS274795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274795 in the RIR database for the space.	631 of 636
ROA: none	2804:93b4:8000::/33	No ROA covers it. Add a ROA for AS274795, maxLength 33.	631 of 636
Route object: none	2804:93b4:8000::/33	No route object for it. A route object for 2804:93b4::/32 with origin AS274795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274795 in the RIR database for the space.	631 of 636
ROA: none	2804:93b4::/32	No ROA covers it. Add a ROA for AS274795, maxLength 32.	630 of 636
Route object: RIR	2804:93b4::/32	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	630 of 636
ROA: none	38.225.221.0/24	No ROA covers it. Add a ROA for AS274795, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:93b4::/33

No ROA covers it. Add a ROA for AS274795, maxLength 33.

631 of 636

Route object: none

2804:93b4::/33

No route object for it. A route object for 2804:93b4::/32 with origin AS274795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274795 in the RIR database for the space.

631 of 636

ROA: none

2804:93b4:8000::/33

No ROA covers it. Add a ROA for AS274795, maxLength 33.

631 of 636

Route object: none

2804:93b4:8000::/33

631 of 636

ROA: none

2804:93b4::/32

No ROA covers it. Add a ROA for AS274795, maxLength 32.

630 of 636

Route object: RIR

2804:93b4::/32

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

630 of 636

ROA: none

38.225.221.0/24

No ROA covers it. Add a ROA for AS274795, maxLength 24.

671 of 673

Route objects not announced

Every route object with origin AS274795 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.