bgpreport

Network · data from 2026-11-12

AS19631 TRAVELPORT - Travelport Operations, Inc.

Registry name: TRAVELPORT - Travelport Operations, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19631, 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.108.19.0/24 No ROA None 673 100% 67
198.151.50.0/24 No ROA None 673 100% 67
198.151.56.0/23 No ROA None 673 100% 67
199.4.205.0/24 No ROA None 673 100% 67
204.126.84.0/23 No ROA None 673 100% 67
216.113.128.0/19 No ROA None 673 100% 67
198.151.32.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS19631 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none192.108.19.0/24No ROA covers it. Add a ROA for AS19631, maxLength 24.673 of 673
Route object: none192.108.19.0/24No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none198.151.50.0/24No ROA covers it. Add a ROA for AS19631, maxLength 24.673 of 673
Route object: none198.151.50.0/24No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none198.151.56.0/23No ROA covers it. Add a ROA for AS19631, maxLength 23.673 of 673
Route object: none198.151.56.0/23No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none199.4.205.0/24No ROA covers it. Add a ROA for AS19631, maxLength 24.673 of 673
Route object: none199.4.205.0/24No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none204.126.84.0/23No ROA covers it. Add a ROA for AS19631, maxLength 23.673 of 673
Route object: none204.126.84.0/23No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none216.113.128.0/19No ROA covers it. Add a ROA for AS19631, maxLength 19.673 of 673
Route object: none216.113.128.0/19No route object for it. Add a route object with origin AS19631 in the RIR database for the space.673 of 673
ROA: none198.151.32.0/24No ROA covers it. Add a ROA for AS19631, maxLength 24.673 of 673
Route object: RIR198.151.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS19631 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.