bgpreport

Network · data from 2026-11-12

AS54038 CALLIDUS-SOFTWARE - Callidus Software Inc.

Registry name: CALLIDUS-SOFTWARE - Callidus Software Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54038, 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.
162.213.80.0/23 No ROA None 673 100% 67
162.213.82.0/24 No ROA Other origin only 673 100% 67
174.137.45.0/24 No ROA None 673 100% 67
204.44.60.0/24 No ROA Other origin only 673 100% 67
208.17.89.0/24 No ROA None 673 100% 67
204.44.62.0/24 No ROA Other IRR onlyRADB 673 100% 67
204.44.63.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.166.181.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
165.254.192.0/23 Valid None 673 100% 67
165.254.194.0/24 Valid None 673 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none7
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none162.213.80.0/23No ROA covers it. Add a ROA for AS54038, maxLength 23.673 of 673
Route object: none162.213.80.0/23No route object for it. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
ROA: none162.213.82.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: none162.213.82.0/24Route objects for it name AS19893. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
ROA: none174.137.45.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: none174.137.45.0/24No route object for it. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
ROA: none204.44.60.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: none204.44.60.0/24Route objects for it name AS19893. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
ROA: none208.17.89.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: none208.17.89.0/24No route object for it. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
ROA: none204.44.62.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: RIR204.44.62.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.44.63.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: RIR204.44.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.166.181.0/24No ROA covers it. Add a ROA for AS54038, maxLength 24.673 of 673
Route object: none165.254.192.0/23No route object for it. Add a route object with origin AS54038 in the RIR database for the space.673 of 673
Route object: none165.254.194.0/24No route object for it. Add a route object with origin AS54038 in the RIR database for the space.673 of 673

Route objects not announced

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