Network · data from 2026-11-12

AS268347 CLUUB INTERNET E SERVICOS

Registry name: AS268347 - CLUUB INTERNET E SERVICOS LTDA - ME, BR · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

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

Announced routes

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


45.238.161.0/24	Valid	Other IRR onlyRADB, TC	670 100%	67
45.238.163.0/24	Valid	Other IRR onlyTC	669 99%	67
45.238.160.0/22	Valid	Other IRR onlyRADB, TC	666 99%	67
45.238.162.0/23	Valid	Other IRR onlyRADB, TC	666 99%	67
45.238.160.0/23	Valid	Other IRR onlyRADB, TC	665 99%	67
2804:4fc0::/32	Valid	Other IRR onlyRADB, TC	633 100%	67
2804:4fc0:3000::/37	Valid	Other IRR onlyTC	633 100%	67
2804:4fc0:4000::/37	Valid	Other IRR onlyTC	633 100%	67

AS-SET

AS268347'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 8 are in fix.csv.

Route object: RIR8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.238.161.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.238.163.0/24	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	45.238.160.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	45.238.162.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	45.238.160.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	2804:4fc0::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	633 of 636
Route object: RIR	2804:4fc0:3000::/37	Route object only in TC. Add it in the RIR database for the space.	633 of 636
Route object: RIR	2804:4fc0:4000::/37	Route object only in TC. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.238.161.0/24

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

670 of 673

Route object: RIR

45.238.163.0/24

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

669 of 673

Route object: RIR

45.238.160.0/22

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

666 of 673

Route object: RIR

45.238.162.0/23

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

666 of 673

Route object: RIR

45.238.160.0/23

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

665 of 673

Route object: RIR

2804:4fc0::/32

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

633 of 636

Route object: RIR

2804:4fc0:3000::/37

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

633 of 636

Route object: RIR

2804:4fc0:4000::/37

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

633 of 636

Route objects not announced

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