bgpreport

Network · data from 2026-11-12

AS137427 KIDC2-AS-AP - KIDC LIMITED

Registry name: KIDC2-AS-AP - KIDC LIMITED, HK · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
39Route objects not announced registered with origin AS137427, seen from no peer

Announced routes

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

193.239.151.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 576 86% 67
2.59.153.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 552 82% 67
45.91.227.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 551 82% 67
45.91.225.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 90 13% 37

AS-SET

AS137427 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 39 are in fix.csv.

  • Route object: not announced39

Route objects not announced

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

2.59.152.0/22RIPEValid
2.59.154.0/24RIPEInvalid: maxLength
45.91.224.0/22RIPEValid
45.91.226.0/24NTTCOM, RADB, RIPEValid
45.142.152.0/22RIPEValid
45.142.153.0/24RIPEValid
91.204.224.0/22RIPEValid
91.204.224.0/24RIPEValid
91.204.225.0/24RIPEValid
91.204.226.0/24RIPEValid
91.204.227.0/24RIPEValid
103.80.132.0/22APNICValid
103.80.132.0/24APNICValid
103.80.133.0/24APNICValid
103.80.134.0/24APNICValid
103.80.135.0/24APNICValid
103.91.217.0/24APNICValid
103.99.208.0/23APNICValid
103.99.208.0/24APNICValid
103.99.209.0/24APNICValid
103.99.210.0/24APNICValid
103.151.172.0/23APNICValid
103.151.172.0/24APNICValid
103.151.173.0/24APNICValid
103.254.72.0/22APNICValid
103.254.73.0/24APNICValid
182.161.66.0/24APNICValid
185.202.100.0/22RIPEValid
185.202.101.0/24RIPEValid
192.197.113.0/24APNICValid
193.239.150.0/23RIPEValid
193.239.150.0/24NTTCOM, RADB, RIPEValid
193.239.154.0/23RIPEValid
193.239.154.0/24NTTCOM, RADB, RIPEValid
194.126.202.0/24RIPEValid
194.126.215.0/24NTTCOM, RADB, RIPEValid
194.126.219.0/24RIPEValid
199.212.57.0/24APNICValid
204.52.191.0/24APNICValid

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.