bgpreport

Network · data from 2026-11-12

AS62550 INOVADATA

Registry name: INOVADATA - Inova Data Solutions, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62550, 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.111.128.0/23 No ROA None 673 100% 67
45.65.152.0/22 Valid RIR databaseLACNIC 673 100% 67
136.175.236.0/23 Valid RIR databaseARIN 673 100% 67
136.175.238.0/24 Valid RIR databaseARIN 673 100% 67
136.175.239.0/24 Valid RIR databaseARIN 673 100% 67
162.222.140.0/22 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS62550's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none38.111.128.0/23No ROA covers it. Add a ROA for AS62550, maxLength 23.673 of 673
Route object: none38.111.128.0/23No route object for it. Add a route object with origin AS62550 in the RIR database for the space.673 of 673

Route objects not announced

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

136.175.236.0/22ARINValid
136.175.236.0/24ARINValid
136.175.237.0/24ARINValid
136.175.238.0/23ARINValid
2607:a580::/32ARINNo ROA
2806:2e5::/32LACNICValid

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.