bgpreport

Network · data from 2026-11-12

AS18608 PALADYNE-SYSTEMS-INC - PALADYNE SYSTEMS, LLC

Registry name: PALADYNE-SYSTEMS-INC - PALADYNE SYSTEMS, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18608, 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.
38.103.44.0/24 No ROA Other IRR onlyRADB 672 100% 66
38.101.185.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 66
74.119.34.0/23 No ROA RIR databaseARIN 673 100% 67
74.119.36.0/23 No ROA RIR databaseARIN, RADB 673 100% 67
74.119.33.0/24 No ROA RIR databaseARIN 672 100% 66
74.119.36.0/24 No ROA RIR databaseARIN, RADB 672 100% 66
74.119.32.0/24 No ROA RIR databaseARIN, RADB 671 100% 66
74.119.34.0/24 No ROA RIR databaseARIN 670 100% 67

AS-SET

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

  • ROA: none8
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none38.103.44.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.672 of 673
Route object: RIR38.103.44.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.101.185.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.671 of 673
Route object: RIR38.101.185.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none74.119.34.0/23No ROA covers it. Add a ROA for AS18608, maxLength 23.673 of 673
ROA: none74.119.36.0/23No ROA covers it. Add a ROA for AS18608, maxLength 23.673 of 673
ROA: none74.119.33.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.672 of 673
ROA: none74.119.36.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.672 of 673
ROA: none74.119.32.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.671 of 673
ROA: none74.119.34.0/24No ROA covers it. Add a ROA for AS18608, maxLength 24.670 of 673

Route objects not announced

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

74.119.32.0/23ARINNo ROA
74.119.36.0/22ARINNo ROA
74.119.38.0/24ARINNo 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.