Network · data from 2026-11-12

AS269483 CN Telecom

Registry name: AS269483 - CYBER NET TELECOMUNICACOES EIRELI ME, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No 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 AS269483, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269483, 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:6554::/33	Valid	Nonecovered by 2804:6554::/32	351 55%	64
2804:6554:8000::/33	Valid	Nonecovered by 2804:6554::/32	351 55%	64
45.187.20.0/23	Valid	Nonecovered by 45.187.20.0/22	203 30%	54
45.187.22.0/23	Valid	Nonecovered by 45.187.20.0/22	203 30%	54
45.187.20.0/22	Valid	Other IRR onlyRADB	671 100%	66
2804:6554::/32	Valid	Other IRR onlyRADB	636 100%	67

AS-SET

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

Route object: none4
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:6554::/33	No route object for it. A route object for 2804:6554::/32 with origin AS269483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269483 in the RIR database for the space.	351 of 636
Route object: none	2804:6554:8000::/33	No route object for it. A route object for 2804:6554::/32 with origin AS269483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269483 in the RIR database for the space.	351 of 636
Route object: none	45.187.20.0/23	No route object for it. A route object for 45.187.20.0/22 with origin AS269483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269483 in the RIR database for the space.	203 of 673
Route object: none	45.187.22.0/23	No route object for it. A route object for 45.187.20.0/22 with origin AS269483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269483 in the RIR database for the space.	203 of 673
Route object: RIR	45.187.20.0/22	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:6554::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:6554::/33

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

351 of 636

Route object: none

2804:6554:8000::/33

351 of 636

Route object: none

45.187.20.0/23

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

203 of 673

Route object: none

45.187.22.0/23

203 of 673

Route object: RIR

45.187.20.0/22

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

671 of 673

Route object: RIR

2804:6554::/32

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

636 of 636

Route objects not announced

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