Network · data from 2026-11-12

AS274649 AS274649 - NOC T.I Informatica LTDA - ME

Registry name: AS274649 - NOC T.I Informatica LTDA - ME, BR · not in PeeringDB

0IPv4 routes

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

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274649, 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:9190::/33	No ROA	Nonecovered by 2804:9190::/32	8 1%low visibility	6
2804:9190:8000::/33	No ROA	Nonecovered by 2804:9190::/32	8 1%low visibility	6
2804:9190::/32	No ROA	Other IRR onlyRADB	633 100%	69

2804:9190::/33

No ROA

Nonecovered by 2804:9190::/32

8 1%low visibility

2804:9190:8000::/33

No ROA

Nonecovered by 2804:9190::/32

8 1%low visibility

2804:9190::/32

No ROA

Other IRR onlyRADB

633 100%

AS-SET

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

ROA: none3
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:9190::/33	No ROA covers it. Add a ROA for AS274649, maxLength 33.	8 of 636
Route object: none	2804:9190::/33	No route object for it. A route object for 2804:9190::/32 with origin AS274649 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274649 in the RIR database for the space.	8 of 636
ROA: none	2804:9190:8000::/33	No ROA covers it. Add a ROA for AS274649, maxLength 33.	8 of 636
Route object: none	2804:9190:8000::/33	No route object for it. A route object for 2804:9190::/32 with origin AS274649 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274649 in the RIR database for the space.	8 of 636
ROA: none	2804:9190::/32	No ROA covers it. Add a ROA for AS274649, maxLength 32.	633 of 636
Route object: RIR	2804:9190::/32	Route object only in RADB. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:9190::/33

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

8 of 636

Route object: none

2804:9190::/33

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

8 of 636

ROA: none

2804:9190:8000::/33

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

8 of 636

Route object: none

2804:9190:8000::/33

8 of 636

ROA: none

2804:9190::/32

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

633 of 636

Route object: RIR

2804:9190::/32

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

633 of 636

Route objects not announced

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