Network · data from 2026-11-12

AS274711 AS274711 - IB TELECOM FIBRA LTDA

Registry name: AS274711 - IB TELECOM FIBRA LTDA, BR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 0.0% with a route object

1IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

5No 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 AS274711, seen from no peer

Announced routes

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


45.164.41.0/24	No ROA	Other origin only	666 99%	67
45.164.42.0/23	No ROA	Other origin only	666 99%	67
45.164.43.0/24	No ROA	Other origin only	663 99%	67
45.164.42.0/24	No ROA	Other origin only	131 19%	44
2804:9270::/32	No ROA	Other IRR onlyBBOI, NTTCOM, TC	636 100%	67

AS-SET

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

ROA: none5
Route object: none4
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.164.41.0/24	No ROA covers it. Add a ROA for AS274711, maxLength 24.	666 of 673
Route object: none	45.164.41.0/24	Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.	666 of 673
ROA: none	45.164.42.0/23	No ROA covers it. Add a ROA for AS274711, maxLength 23.	666 of 673
Route object: none	45.164.42.0/23	Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.	666 of 673
ROA: none	45.164.43.0/24	No ROA covers it. Add a ROA for AS274711, maxLength 24.	663 of 673
Route object: none	45.164.43.0/24	Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.	663 of 673
ROA: none	45.164.42.0/24	No ROA covers it. Add a ROA for AS274711, maxLength 24.	131 of 673
Route object: none	45.164.42.0/24	Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.	131 of 673
ROA: none	2804:9270::/32	No ROA covers it. Add a ROA for AS274711, maxLength 32.	636 of 636
Route object: RIR	2804:9270::/32	Route object only in BBOI, NTTCOM, TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.164.41.0/24

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

666 of 673

Route object: none

45.164.41.0/24

Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.

666 of 673

ROA: none

45.164.42.0/23

No ROA covers it. Add a ROA for AS274711, maxLength 23.

666 of 673

Route object: none

45.164.42.0/23

Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.

666 of 673

ROA: none

45.164.43.0/24

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

663 of 673

Route object: none

45.164.43.0/24

Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.

663 of 673

ROA: none

45.164.42.0/24

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

131 of 673

Route object: none

45.164.42.0/24

Route objects for it name AS268596. Add a route object with origin AS274711 in the RIR database for the space.

131 of 673

ROA: none

2804:9270::/32

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

636 of 636

Route object: RIR

2804:9270::/32

Route object only in BBOI, NTTCOM, TC. Add it in the RIR database for the space.

636 of 636

Route objects not announced

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