bgpreport

Network · data from 2026-11-12

AS63351 ASN-SCF-45 - Southern Caribbean Fiber

Registry name: ASN-SCF-45 - Southern Caribbean Fiber, GP · not in PeeringDB

8IPv4 routes 37.5% RPKI valid · 25.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS63351, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63351, 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.
38.86.162.0/23 No ROA None 673 100% 67
38.87.192.0/22 No ROA None 673 100% 67
199.91.162.0/24 No ROA None 673 100% 67
38.86.163.0/24 No ROA None 672 100% 67
38.86.161.0/24 No ROA Other IRR onlyRADB 672 100% 67
207.90.254.0/24 Valid Nonecovered by 207.90.254.0/23 673 100% 67
207.90.255.0/24 Valid Nonecovered by 207.90.254.0/23 673 100% 67
207.90.254.0/23 Valid RIR databaseARIN 673 100% 67
2606:3180::/32 Valid RIR databaseARIN 636 100% 67

AS-SET

AS63351 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 13 are in fix.csv.

  • ROA: none5
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.86.162.0/23No ROA covers it. Add a ROA for AS63351, maxLength 23.673 of 673
Route object: none38.86.162.0/23No route object for it. Add a route object with origin AS63351 in the RIR database for the space.673 of 673
ROA: none38.87.192.0/22No ROA covers it. Add a ROA for AS63351, maxLength 22.673 of 673
Route object: none38.87.192.0/22No route object for it. Add a route object with origin AS63351 in the RIR database for the space.673 of 673
ROA: none199.91.162.0/24No ROA covers it. Add a ROA for AS63351, maxLength 24.673 of 673
Route object: none199.91.162.0/24No route object for it. Add a route object with origin AS63351 in the RIR database for the space.673 of 673
ROA: none38.86.163.0/24No ROA covers it. Add a ROA for AS63351, maxLength 24.672 of 673
Route object: none38.86.163.0/24No route object for it. Add a route object with origin AS63351 in the RIR database for the space.672 of 673
ROA: none38.86.161.0/24No ROA covers it. Add a ROA for AS63351, maxLength 24.672 of 673
Route object: RIR38.86.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none207.90.254.0/24No route object for it. A route object for 207.90.254.0/23 with origin AS63351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63351 in the RIR database for the space.673 of 673
Route object: none207.90.255.0/24No route object for it. A route object for 207.90.254.0/23 with origin AS63351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63351 in the RIR database for the space.673 of 673

Route objects not announced

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

2001:470:657::/48ARINValid

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.