bgpreport

Network · data from 2026-11-12

AS10278 CWWI-AS - Cable & Wireless (Barbados) Limited

Registry name: CWWI-AS - Cable & Wireless (Barbados) Limited, BB · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
5No ROA 7 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS10278, seen from no peer

Announced routes

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

190.4.158.0/24 Invalid: origin None 9 1%low visibility 5
190.4.159.0/24 Invalid: origin None 9 1%low visibility 5
67.213.147.0/24 No ROA None 671 100% 67
67.213.148.0/24 No ROA None 671 100% 67
67.213.149.0/24 No ROA None 671 100% 67
67.213.150.0/24 No ROA None 671 100% 67
72.27.129.0/24 No ROA Other origin only 670 100% 67

AS-SET

AS10278 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • ROA: origin2
  • ROA: none5
  • Route object: none7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin190.4.158.0/24ROAs covering it name AS11081, not AS10278. If AS10278 should announce it, add a ROA for AS10278.9 of 673
Route object: none190.4.158.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.9 of 673
ROA: origin190.4.159.0/24ROAs covering it name AS11081, not AS10278. If AS10278 should announce it, add a ROA for AS10278.9 of 673
Route object: none190.4.159.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.9 of 673
ROA: none67.213.147.0/24No ROA covers it. Add a ROA for AS10278, maxLength 24.671 of 673
Route object: none67.213.147.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.671 of 673
ROA: none67.213.148.0/24No ROA covers it. Add a ROA for AS10278, maxLength 24.671 of 673
Route object: none67.213.148.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.671 of 673
ROA: none67.213.149.0/24No ROA covers it. Add a ROA for AS10278, maxLength 24.671 of 673
Route object: none67.213.149.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.671 of 673
ROA: none67.213.150.0/24No ROA covers it. Add a ROA for AS10278, maxLength 24.671 of 673
Route object: none67.213.150.0/24No route object for it. Add a route object with origin AS10278 in the RIR database for the space.671 of 673
ROA: none72.27.129.0/24No ROA covers it. Add a ROA for AS10278, maxLength 24.670 of 673
Route object: none72.27.129.0/24Route objects for it name AS10292. Add a route object with origin AS10278 in the RIR database for the space.670 of 673

Route objects not announced

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

196.1.142.0/24RADBNo ROA
196.3.95.0/24RADBNo ROA
216.110.116.0/24RADBNo 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.