bgpreport

Network · data from 2026-11-12

AS4237 CSC-IGN-FTW-AS4237 - DXC US Latin America Corporation

Registry name: CSC-IGN-FTW-AS4237 - DXC US Latin America Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4237, 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.
20.137.184.0/21 Invalid: maxLength Other origin onlycovered by 20.137.176.0/20 1 0%low visibility 1
20.137.0.0/21 Valid RIR databaseARIN, RADB 672 100% 67
20.137.12.0/22 Valid RIR databaseARIN, RADB 672 100% 67
20.137.14.0/23 Valid RIR databaseARIN, RADB 672 100% 67
20.137.176.0/20 Valid RIR databaseARIN, RADB 672 100% 67
20.137.176.0/21 Valid RIR databaseARIN, RADB 672 100% 67
20.137.216.0/24 Valid RIR databaseARIN, RADB 672 100% 67
20.137.240.0/20 Valid RIR databaseARIN, RADB 672 100% 67
20.148.32.0/19 Valid RIR databaseARIN, RADB 672 100% 67
20.148.96.0/19 Valid RIR databaseARIN, RADB 672 100% 67
20.148.128.0/19 Valid RIR databaseARIN, RADB 672 100% 67
20.148.160.0/19 Valid RIR databaseARIN, RADB 672 100% 67
20.148.240.0/20 Valid RIR databaseARIN, RADB 672 100% 67
20.156.169.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength20.137.184.0/21ROA 20.137.176.0/20 AS4237 has maxLength 20; the route is a /21. Raise the maxLength, or add a ROA for 20.137.184.0/21.1 of 673
Route object: none20.137.184.0/21Route objects for it name AS3360. A route object for 20.137.176.0/20 with origin AS4237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4237 in the RIR database for the space.1 of 673

Route objects not announced

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

20.137.160.0/20ARIN, RADBNo ROA
20.139.6.0/24ARIN, RADBValid
20.139.8.0/22RADBNo ROA
20.139.121.0/24RADBNo ROA
20.139.144.0/21NTTCOM, RADBNo ROA
20.139.217.0/24RADBNo ROA
20.148.64.0/20ARIN, RADBNo ROA
20.148.192.0/20ARIN, RADBNo 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.