bgpreport

Network · data from 2026-11-12

AS16789 YARDI

Registry name: YARDI - YARDI SYSTEMS, INC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16789, 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.
64.213.134.0/24 No ROA Other IRR onlyRADB 670 100% 67
94.127.116.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
103.170.76.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
104.156.160.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.156.163.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.156.167.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.156.168.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.156.170.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.156.174.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.156.178.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.156.184.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.156.188.0/23 Valid RIR databaseARIN, RADB 673 100% 67
137.66.122.0/23 Valid RIR databaseARIN, RADB 673 100% 67
137.66.124.0/24 Valid RIR databaseARIN, RADB 673 100% 67
137.66.126.0/24 Valid RIR databaseARIN, RADB 673 100% 67
94.127.118.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
104.156.190.0/24 Valid RIR databaseARIN, RADB 672 100% 66
104.156.180.0/24 Valid RIR databaseARIN, RADB 671 100% 68
104.156.191.0/24 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none64.213.134.0/24No ROA covers it. Add a ROA for AS16789, maxLength 24.670 of 673
Route object: RIR64.213.134.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

93.93.203.0/24RADB, RIPEValid
94.127.112.0/21RADB, RIPENo ROA
104.156.160.0/19RADBNo ROA
137.66.64.0/18RADBNo ROA
193.240.191.0/24NTTCOM, RADBNo 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.