Network · data from 2026-11-12

AS274796 ONENET TELECOMUNICACOES LTDA

Registry name: AS274796 - ONENET TELECOMUNICACOES LTDA, BR · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274796, 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:93b8::/32	No ROA	Other IRR onlyBBOI, NTTCOM, RADB	633 100%	70
38.19.51.0/24	Valid	RIR databaseARIN	668 99%	67

AS-SET

AS274796's PeeringDB record names no 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 2 are in fix.csv.

ROA: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:93b8::/32	No ROA covers it. Add a ROA for AS274796, maxLength 32.	633 of 636
Route object: RIR	2804:93b8::/32	Route object only in BBOI, NTTCOM, RADB. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:93b8::/32

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

633 of 636

Route object: RIR

2804:93b8::/32

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

633 of 636

Route objects not announced

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