bgpreport

Network · data from 2026-11-12

AS22003 PT-ASN - PALANTIR TECHNOLOGIES INC.

Registry name: PT-ASN - PALANTIR TECHNOLOGIES INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22003, 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.
8.4.231.0/24 No ROA None 673 100% 67
198.97.14.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.97.15.0/24 No ROA Other IRR onlyRADB 672 100% 67
62.67.195.0/24 No ROA RIR databaseRIPE 673 100% 67
216.200.189.0/24 Valid RIR databaseAPNIC 671 100% 67
216.200.190.0/24 Valid RIR databaseAPNIC 668 99% 67

AS-SET

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

  • ROA: none4
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none8.4.231.0/24No ROA covers it. Add a ROA for AS22003, maxLength 24.673 of 673
Route object: none8.4.231.0/24No route object for it. Add a route object with origin AS22003 in the RIR database for the space.673 of 673
ROA: none198.97.14.0/24No ROA covers it. Add a ROA for AS22003, maxLength 24.672 of 673
Route object: RIR198.97.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.97.15.0/24No ROA covers it. Add a ROA for AS22003, maxLength 24.672 of 673
Route object: RIR198.97.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none62.67.195.0/24No ROA covers it. Add a ROA for AS22003, maxLength 24.673 of 673

Route objects not announced

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