Network · data from 2026-11-12

AS274677 AS274677 - IEZ! TELECOM LTDA

Registry name: AS274677 - IEZ! TELECOM LTDA, BR · not in PeeringDB

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

4IPv6 routes 100.0% RPKI valid · 25.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 4 with no route object for this origin

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

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

Announced routes

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


38.211.160.0/24	No ROA	Nonecovered by 38.211.160.0/19	671 100%	67
38.211.160.0/19	No ROA	Other IRR onlyRADB	672 100%	67
2804:91f0::/48	Valid	Nonecovered by 2804:91f0::/32	636 100%	67
2804:91f0:40::/42	Valid	Nonecovered by 2804:91f0::/32	636 100%	67
2804:91f0:80::/42	Valid	Nonecovered by 2804:91f0::/32	636 100%	67
2804:91f0::/32	Valid	Other IRR onlyRADB	636 100%	67

AS-SET

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

ROA: none2
Route object: none4
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.211.160.0/24	No ROA covers it. Add a ROA for AS274677, maxLength 24.	671 of 673
Route object: none	38.211.160.0/24	No route object for it. A route object for 38.211.160.0/19 with origin AS274677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274677 in the RIR database for the space.	671 of 673
ROA: none	38.211.160.0/19	No ROA covers it. Add a ROA for AS274677, maxLength 19.	672 of 673
Route object: RIR	38.211.160.0/19	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: none	2804:91f0::/48	No route object for it. A route object for 2804:91f0::/32 with origin AS274677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274677 in the RIR database for the space.	636 of 636
Route object: none	2804:91f0:40::/42	No route object for it. A route object for 2804:91f0::/32 with origin AS274677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274677 in the RIR database for the space.	636 of 636
Route object: none	2804:91f0:80::/42	No route object for it. A route object for 2804:91f0::/32 with origin AS274677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274677 in the RIR database for the space.	636 of 636
Route object: RIR	2804:91f0::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.211.160.0/24

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

671 of 673

Route object: none

38.211.160.0/24

No route object for it. A route object for 38.211.160.0/19 with origin AS274677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274677 in the RIR database for the space.

671 of 673

ROA: none

38.211.160.0/19

No ROA covers it. Add a ROA for AS274677, maxLength 19.

672 of 673

Route object: RIR

38.211.160.0/19

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

672 of 673

Route object: none

2804:91f0::/48

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

636 of 636

Route object: none

2804:91f0:40::/42

636 of 636

Route object: none

2804:91f0:80::/42

636 of 636

Route object: RIR

2804:91f0::/32

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

636 of 636

Route objects not announced

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