bgpreport

Network · data from 2026-11-12

AS140543 READYDEDIS-AS-AP - ReadyDedis, LLC

Registry name: READYDEDIS-AS-AP - ReadyDedis, LLC, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140543, 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.
151.243.168.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.142.174.0/24 No ROA RIR databaseAPNIC 673 100% 66
115.187.16.0/24 Valid RIR databaseAPNIC 673 100% 67
115.187.17.0/24 Valid RIR databaseAPNIC 673 100% 66
134.195.137.0/24 Valid RIR databaseARIN 673 100% 66
165.140.165.0/24 Valid RIR databaseARIN 673 100% 66
170.205.54.0/24 Valid RIR databaseARIN 673 100% 66
193.25.253.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
165.140.164.0/24 Valid RIR databaseARIN 672 100% 67
45.142.237.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2401:4ea0:1::/48 Valid RIR databaseAPNIC 636 100% 70
2401:4ea0::/48 Valid RIR databaseAPNIC 632 99% 68

AS-SET

AS140543 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 4 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin151.243.168.0/24ROAs covering it name AS402252, not AS140543. If AS140543 should announce it, add a ROA for AS140543.2 of 673
Route object: none151.243.168.0/24Route objects for it name AS402252. Add a route object with origin AS140543 in the RIR database for the space.2 of 673
ROA: none103.142.174.0/24No ROA covers it. Add a ROA for AS140543, maxLength 24.673 of 673

Route objects not announced

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

2405:f9c0::/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.