Network · data from 2026-11-12

AS274698 AS274698 - AMAZON TELECOM LTDA

Registry name: AS274698 - AMAZON TELECOM LTDA, BR · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

3No ROA 1 with no route object for this origin

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

1Route objects not announced registered with origin AS274698, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS274698, 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:923c::/33	No ROA	Nonecovered by 2804:923c::/32	636 100%	67
38.210.63.0/24	No ROA	Other IRR onlyRADB	673 100%	67
2804:923c:8000::/33	No ROA	Other IRR onlyRADB	632 99%	67

AS-SET

AS274698 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: none3
Route object: none1
Route object: RIR2
Route object: not announced1

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

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:923c::/33

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

636 of 636

Route object: none

2804:923c::/33

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

636 of 636

ROA: none

38.210.63.0/24

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

673 of 673

Route object: RIR

38.210.63.0/24

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

673 of 673

ROA: none

2804:923c:8000::/33

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

632 of 636

Route object: RIR

2804:923c:8000::/33

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

632 of 636

Route objects not announced

Route objects with origin AS274698 whose prefix no peer sees AS274698 announce. Many are kept on purpose (backup routes, space announced only in some places).


2804:923c::/32	RADB	No ROA

2804:923c::/32

RADB

No ROA

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.