Network · data from 2026-11-12

AS263799 Datasur

Registry name: AS263799 - CARIBBEAN COMMUNICATION SERVICES, SR · PeeringDB

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

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

1RPKI invalid 0 origin · 1 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


2803:ff40:a000::/48	Invalid: maxLength	Nonecovered by 2803:ff40::/32	19 3%low visibility	10
168.195.216.0/24	Valid	Nonecovered by 168.195.216.0/22	671 100%	67
168.195.216.0/22	Valid	Other IRR onlyRADB	673 100%	67
168.195.218.0/24	Valid	Other IRR onlyRADB	671 100%	67
2803:ff40::/32	Valid	Other IRR onlyRADB	636 100%	67

2803:ff40:a000::/48

Invalid: maxLength

Nonecovered by 2803:ff40::/32

19 3%low visibility

168.195.216.0/24

Valid

Nonecovered by 168.195.216.0/22

671 100%

168.195.216.0/22

Valid

Other IRR onlyRADB

673 100%

168.195.218.0/24

Valid

Other IRR onlyRADB

671 100%

2803:ff40::/32

Valid

Other IRR onlyRADB

636 100%

AS-SET

AS263799'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.

ROA: maxLength1
Route object: none2
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2803:ff40:a000::/48	ROA 2803:ff40::/32 AS263799 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2803:ff40:a000::/48.	19 of 636
Route object: none	2803:ff40:a000::/48	No route object for it. A route object for 2803:ff40::/32 with origin AS263799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263799 in the RIR database for the space.	19 of 636
Route object: none	168.195.216.0/24	No route object for it. A route object for 168.195.216.0/22 with origin AS263799 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263799 in the RIR database for the space.	671 of 673
Route object: RIR	168.195.216.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	168.195.218.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2803:ff40::/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

ROA: maxLength

2803:ff40:a000::/48

ROA 2803:ff40::/32 AS263799 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2803:ff40:a000::/48.

19 of 636

Route object: none

2803:ff40:a000::/48

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

19 of 636

Route object: none

168.195.216.0/24

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

671 of 673

Route object: RIR

168.195.216.0/22

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

673 of 673

Route object: RIR

168.195.218.0/24

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

671 of 673

Route object: RIR

2803:ff40::/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 AS263799 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.