bgpreport

Network · data from 2026-11-12

AS141681 ONDO

Registry name: IMNL-AS-AP - ONDO LLC, MN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141681, 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.
103.41.92.0/24 Valid RIR databaseAPNIC 671 100% 67
103.41.93.0/24 Valid RIR databaseAPNIC 671 100% 67
103.161.242.0/24 Valid RIR databaseAPNIC 671 100% 67
103.170.17.0/24 Valid RIR databaseAPNIC 671 100% 67
103.212.162.0/24 Valid RIR databaseAPNIC 671 100% 67
103.212.163.0/24 Valid RIR databaseAPNIC 671 100% 67
103.254.120.0/24 Valid RIR databaseAPNIC 671 100% 67
103.254.121.0/24 Valid RIR databaseAPNIC 671 100% 67
2400:bde0::/32 Valid RIR databaseAPNIC 635 100% 67
2400:bde0::/48 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:2::/48 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:3000::/46 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:4000::/46 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:4004::/46 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:6000::/46 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:6004::/46 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8000::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8002::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8004::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8006::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8008::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8010::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8012::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8014::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8016::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8018::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8020::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8022::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8024::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8026::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8028::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8030::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8032::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8034::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8036::/47 Valid RIR databaseAPNIC 635 100% 67
2400:bde0:8038::/47 Valid RIR databaseAPNIC 635 100% 67
2401:ae0::/32 Valid RIR databaseAPNIC 635 100% 67
2401:ae0::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:1::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:2::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:aa::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:bb::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6000::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6100::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6200::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6300::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6400::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6500::/48 Valid RIR databaseAPNIC 635 100% 67
2401:ae0:6600::/48 Valid RIR databaseAPNIC 635 100% 67

AS-SET

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

  • Route object: not announced38

Route objects not announced

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

2001:df2:87c0::/48APNICValid
2400:bde0:0:100::/56APNICValid
2400:bde0:0:100::/60APNICValid
2400:bde0:0:108::/64APNICValid
2400:bde0:1::/48APNICValid
2400:bde0:1:150::/64APNICValid
2400:bde0:100::/46APNICValid
2400:bde0:100::/48APNICValid
2400:bde0:3000::/48APNICValid
2400:bde0:4000::/44APNICValid
2400:bde0:4000::/45APNICValid
2400:bde0:8000::/44APNICValid
2400:bde0:8000::/45APNICValid
2400:bde0:8000::/46APNICValid
2400:bde0:8004::/46APNICValid
2400:bde0:8008::/45APNICValid
2400:bde0:8008::/46APNICValid
2400:bde0:8010::/44APNICValid
2400:bde0:8010::/45APNICValid
2400:bde0:8010::/46APNICValid
2400:bde0:8014::/46APNICValid
2400:bde0:8018::/45APNICValid
2400:bde0:8018::/46APNICValid
2400:bde0:8020::/44APNICValid
2400:bde0:8020::/45APNICValid
2400:bde0:8020::/46APNICValid
2400:bde0:8024::/46APNICValid
2400:bde0:8028::/45APNICValid
2400:bde0:8028::/46APNICValid
2400:bde0:8030::/44APNICValid
2400:bde0:8030::/45APNICValid
2400:bde0:8030::/46APNICValid
2400:bde0:8034::/46APNICValid
2400:bde0:8038::/45APNICValid
2400:bde0:8038::/46APNICValid
2401:ae0:cc::/48APNICValid
2401:ae0:6000::/36APNICValid
2401:ae0:6700::/48APNICValid

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.