bgpreport

Network · data from 2026-11-12

AS398019 DYNU - Dynu Systems Incorporated

Registry name: DYNU - Dynu Systems Incorporated, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS398019, 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.
2602:ff23:50::/48 No ROA None 636 100% 67
2602:ff23::/48 No ROA Other IRR onlyRADB 636 100% 67
140.235.16.0/24 Valid RIR databaseARIN 672 100% 67
140.235.17.0/24 Valid RIR databaseARIN 672 100% 67
140.235.18.0/24 Valid RIR databaseARIN 672 100% 67
140.235.19.0/24 Valid RIR databaseARIN 672 100% 67
142.202.188.0/24 Valid RIR databaseARIN, RADB 672 100% 67
142.202.189.0/24 Valid RIR databaseARIN, RADB 672 100% 67
142.202.190.0/24 Valid RIR databaseARIN, RADB 672 100% 67
142.202.191.0/24 Valid RIR databaseARIN, RADB 672 100% 67
155.103.40.0/24 Valid RIR databaseARIN 672 100% 67
155.103.41.0/24 Valid RIR databaseARIN 672 100% 67
155.103.42.0/24 Valid RIR databaseARIN 672 100% 67
155.103.43.0/24 Valid RIR databaseARIN 672 100% 67
162.216.240.0/24 Valid RIR databaseARIN, RADB 672 100% 67
162.216.241.0/24 Valid RIR databaseARIN, RADB 672 100% 67
162.216.242.0/24 Valid RIR databaseARIN, RADB 672 100% 67
162.216.243.0/24 Valid RIR databaseARIN, RADB 672 100% 67
172.81.60.0/24 Valid RIR databaseARIN, RADB 672 100% 67
172.81.61.0/24 Valid RIR databaseARIN, RADB 672 100% 67
172.81.62.0/24 Valid RIR databaseARIN, RADB 672 100% 67
172.81.63.0/24 Valid RIR databaseARIN, RADB 672 100% 67
207.174.0.0/24 Valid RIR databaseARIN 672 100% 67
207.174.1.0/24 Valid RIR databaseARIN 672 100% 67
207.174.2.0/24 Valid RIR databaseARIN 672 100% 67
207.174.3.0/24 Valid RIR databaseARIN 672 100% 67
72.51.56.0/24 Valid RIR databaseARIN 671 100% 67
72.51.57.0/24 Valid RIR databaseARIN 671 100% 67
72.51.58.0/24 Valid RIR databaseARIN 671 100% 67
72.51.59.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2602:ff23:50::/48No ROA covers it. Add a ROA for AS398019, maxLength 48.636 of 636
Route object: none2602:ff23:50::/48No route object for it. Add a route object with origin AS398019 in the RIR database for the space.636 of 636
ROA: none2602:ff23::/48No ROA covers it. Add a ROA for AS398019, maxLength 48.636 of 636
Route object: RIR2602:ff23::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2600:c05:3010::/48RADBNo 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.