Network · data from 2026-11-12

AS268678 CSI SOLUCOES TECNOLOGICAS

Registry name: AS268678 - CSI SOLUCOES TECNOLOGICAS LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 28.6% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 7 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268678, 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.165.148.0/24	Valid	Nonecovered by 45.165.148.0/23	671 100%	66
45.165.150.0/23	Valid	Nonecovered by 45.165.148.0/22	671 100%	67
45.165.149.0/24	Valid	Nonecovered by 45.165.148.0/23	670 100%	66
45.165.150.0/24	Valid	Nonecovered by 45.165.148.0/22	670 100%	66
45.165.151.0/24	Valid	Nonecovered by 45.165.148.0/22	668 99%	67
2804:54ec::/33	Valid	Nonecovered by 2804:54ec::/32	351 55%	64
2804:54ec:8000::/33	Valid	Nonecovered by 2804:54ec::/32	350 55%	64
45.165.148.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
45.165.148.0/23	Valid	Other IRR onlyRADB	671 100%	67
2804:54ec::/32	Valid	Other IRR onlyRADB, TC	630 99%	67

AS-SET

AS268678'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 10 are in fix.csv.

Route object: none7
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
Route object: none	45.165.148.0/24	No route object for it. A route object for 45.165.148.0/23 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	671 of 673
Route object: none	45.165.150.0/23	No route object for it. A route object for 45.165.148.0/22 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	671 of 673
Route object: none	45.165.149.0/24	No route object for it. A route object for 45.165.148.0/23 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	670 of 673
Route object: none	45.165.150.0/24	No route object for it. A route object for 45.165.148.0/22 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	670 of 673
Route object: none	45.165.151.0/24	No route object for it. A route object for 45.165.148.0/22 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	668 of 673
Route object: none	2804:54ec::/33	No route object for it. A route object for 2804:54ec::/32 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	351 of 636
Route object: none	2804:54ec:8000::/33	No route object for it. A route object for 2804:54ec::/32 with origin AS268678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268678 in the RIR database for the space.	350 of 636
Route object: RIR	45.165.148.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.165.148.0/23	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:54ec::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	630 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

45.165.148.0/24

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

671 of 673

Route object: none

45.165.150.0/23

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

671 of 673

Route object: none

45.165.149.0/24

670 of 673

Route object: none

45.165.150.0/24

670 of 673

Route object: none

45.165.151.0/24

668 of 673

Route object: none

2804:54ec::/33

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

351 of 636

Route object: none

2804:54ec:8000::/33

350 of 636

Route object: RIR

45.165.148.0/22

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

671 of 673

Route object: RIR

45.165.148.0/23

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

671 of 673

Route object: RIR

2804:54ec::/32

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

630 of 636

Route objects not announced

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