bgpreport

Network · data from 2026-11-12

AS23060 CGGV-HOU - CGGVeritas Services (US) Inc.

Registry name: CGGV-HOU - CGGVeritas Services (US) Inc., US · not in PeeringDB

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

Announced routes

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

192.159.106.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

AS23060 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 8 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none192.159.106.0/24No ROA covers it. Add a ROA for AS23060, maxLength 24.673 of 673
Route object: RIR192.159.106.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

12.5.201.0/24NTTCOMNo ROA
192.203.70.0/24NTTCOMNo ROA
198.3.38.0/24NTTCOMNo ROA
198.3.39.0/24NTTCOMNo ROA
198.3.64.0/20NTTCOMNo ROA
205.196.180.0/24NTTCOMNo 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.