bgpreport

Network · data from 2026-11-12

AS11298 KLD-ATX - Renew Data Corp.

Registry name: KLD-ATX - Renew Data Corp., US · not in PeeringDB

2IPv4 routes 50.0% 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
12Route objects not announced registered with origin AS11298, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11298, 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.

74.119.58.0/24 No ROA RIR databaseARIN 671 100% 70
71.42.190.0/24 Valid Other IRR onlyRADB 672 100% 70

AS-SET

AS11298 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none74.119.58.0/24No ROA covers it. Add a ROA for AS11298, maxLength 24.671 of 673
Route object: RIR71.42.190.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

162.221.88.0/21RADBNo ROA
162.255.16.0/22RADBNo ROA
198.206.132.0/22RADBNo ROA
199.38.80.0/21RADBNo ROA
199.195.144.0/22RADBNo ROA
204.130.199.0/24NTTCOMNo ROA
206.54.254.0/23RADBNo ROA
207.7.20.0/22RADBNo ROA
207.112.136.0/22RADBNo ROA
208.192.4.0/23NTTCOMNo ROA
208.215.194.0/23NTTCOMNo ROA
216.54.224.0/24RADBNo 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.