bgpreport

Network · data from 2026-11-12

AS134829 PPIP-AS-AP - PPIP Associated Communication Limited

Registry name: PPIP-AS-AP - PPIP Associated Communication Limited, HK · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
1Low visibility seen by under 10% of full-table peers
49Route objects not announced registered with origin AS134829, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134829, 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.92.137.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.92.138.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.135.104.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.135.105.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.186.86.0/24 Valid RIR databaseAPNIC 673 100% 67
103.186.87.0/24 Valid RIR databaseAPNIC 673 100% 67
2404:7b40::/32 Valid RIR databaseAPNIC 635 100% 68
103.92.139.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2

AS-SET

AS134829 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 49 are in fix.csv.

  • Route object: not announced49

Route objects not announced

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

43.255.112.0/22RADBNo ROA
103.56.174.0/24RADBNo ROA
103.92.138.0/23RADBNo ROA
103.121.188.0/22RADBNo ROA
103.121.188.0/23RADBNo ROA
103.121.190.0/23RADBNo ROA
103.135.104.0/23RADBNo ROA
103.138.225.0/24RADBNo ROA
103.197.104.0/22RADBNo ROA
103.197.104.0/23RADBNo ROA
103.246.144.0/22RADBNo ROA
103.246.144.0/23RADBNo ROA
103.246.146.0/23RADBNo ROA
103.246.228.0/22RADBNo ROA
103.246.228.0/23RADBNo ROA
103.246.228.0/24RADBNo ROA
103.246.229.0/24RADBNo ROA
103.246.230.0/23RADBNo ROA
103.246.230.0/24RADBNo ROA
103.246.231.0/24RADBNo ROA
111.67.96.0/20RADBNo ROA
111.67.96.0/21RADBNo ROA
111.67.104.0/21RADBNo ROA
111.67.104.0/22RADBNo ROA
111.67.104.0/23RADBNo ROA
111.67.104.0/24RADBNo ROA
111.67.105.0/24RADBNo ROA
111.67.106.0/23RADBNo ROA
111.67.106.0/24RADBNo ROA
111.67.107.0/24RADBNo ROA
111.67.108.0/22RADBNo ROA
111.67.108.0/23RADBNo ROA
111.67.108.0/24RADBNo ROA
111.67.109.0/24RADBNo ROA
111.67.110.0/23RADBNo ROA
111.67.110.0/24RADBNo ROA
111.67.111.0/24RADBNo ROA
116.214.24.0/21RADBNo ROA
116.214.24.0/22RADBNo ROA
116.214.28.0/22RADBNo ROA
117.55.248.0/21RADBNo ROA
117.55.252.0/22RADBNo ROA
117.55.254.0/23RADBNo ROA
146.88.200.0/21RADBNo ROA
146.88.200.0/22RADBNo ROA
146.88.204.0/22RADBNo ROA
154.85.2.0/23RADBNo ROA
202.58.16.0/22RADBNo ROA
220.158.148.0/22RADBNo 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.