Network · data from 2026-11-12

AS264284 Transdados Telecom

Registry name: AS264284 - Transdados Telecom, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 40.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 8 with no route object for this origin

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

2Route objects not announced registered with origin AS264284, seen from no peer

Announced routes

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


138.121.2.0/24	Valid	Nonecovered by 138.121.0.0/22	671 100%	67
138.121.0.0/24	Valid	Nonecovered by 138.121.0.0/22	663 99%	67
2804:2580::/35	Valid	Nonecovered by 2804:2580::/32	632 99%	67
2804:2580:80::/48	Valid	Nonecovered by 2804:2580::/32	632 99%	67
2804:2580:e0::/43	Valid	Nonecovered by 2804:2580::/32	632 99%	67
2804:2580:4000::/35	Valid	Nonecovered by 2804:2580::/32	632 99%	67
2804:2580:c0::/43	Valid	Nonecovered by 2804:2580::/32	631 99%	67
138.121.0.0/23	Valid	Nonecovered by 138.121.0.0/22	105 16%	39
138.121.3.0/24	Valid	Other IRR onlyRADB	665 99%	67
138.121.1.0/24	Valid	Other IRR onlyRADB	663 99%	67

AS-SET

AS264284'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 12 are in fix.csv.

Route object: none8
Route object: RIR2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	138.121.2.0/24	No route object for it. A route object for 138.121.0.0/22 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	671 of 673
Route object: none	138.121.0.0/24	No route object for it. A route object for 138.121.0.0/22 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	663 of 673
Route object: none	2804:2580::/35	No route object for it. A route object for 2804:2580::/32 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	632 of 636
Route object: none	2804:2580:80::/48	No route object for it. A route object for 2804:2580::/32 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	632 of 636
Route object: none	2804:2580:e0::/43	No route object for it. A route object for 2804:2580::/32 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	632 of 636
Route object: none	2804:2580:4000::/35	No route object for it. A route object for 2804:2580::/32 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	632 of 636
Route object: none	2804:2580:c0::/43	No route object for it. A route object for 2804:2580::/32 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	631 of 636
Route object: none	138.121.0.0/23	No route object for it. A route object for 138.121.0.0/22 with origin AS264284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264284 in the RIR database for the space.	105 of 673
Route object: RIR	138.121.3.0/24	Route object only in RADB. Add it in the RIR database for the space.	665 of 673
Route object: RIR	138.121.1.0/24	Route object only in RADB. Add it in the RIR database for the space.	663 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

138.121.2.0/24

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

671 of 673

Route object: none

138.121.0.0/24

663 of 673

Route object: none

2804:2580::/35

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

632 of 636

Route object: none

2804:2580:80::/48

632 of 636

Route object: none

2804:2580:e0::/43

632 of 636

Route object: none

2804:2580:4000::/35

632 of 636

Route object: none

2804:2580:c0::/43

631 of 636

Route object: none

138.121.0.0/23

105 of 673

Route object: RIR

138.121.3.0/24

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

665 of 673

Route object: RIR

138.121.1.0/24

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

663 of 673

Route objects not announced

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


138.121.0.0/22	RADB, TC	No ROA
2804:2580::/32	RADB, TC	No ROA

138.121.0.0/22

RADB, TC

No ROA

2804:2580::/32

RADB, TC

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.