bgpreport

Network · data from 2026-11-12

AS134176 Rainbow network

Registry name: CLOUDIE-AS-AP - Cloudie Limited, HK · PeeringDB

29IPv4 routes 65.5% RPKI valid · 86.2% with a route object
3IPv6 routes 66.7% RPKI valid · 0.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
7No ROA 7 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
54Route objects not announced registered with origin AS134176, seen from no peer

Announced routes

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

23.172.217.0/24 Invalid: origin Other origin only 12 2%low visibility 12
77.90.154.0/24 Invalid: origin Other origin only 3 0%low visibility 3
108.165.214.0/24 Invalid: origin Other origin only 1 0%low visibility 1
185.253.54.0/24 Invalid: origin None 1 0%low visibility 1
2602:f6a0::/40 No ROA Other origin only 629 99% 68
103.149.132.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.149.133.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.185.228.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.185.229.0/24 No ROA Other IRR onlyRADB 671 100% 67
172.247.36.0/24 No ROA Other IRR onlyRADB, RIPE-NONAUTH 670 100% 67
172.247.37.0/24 No ROA Other IRR onlyRADB, RIPE-NONAUTH 670 100% 67
2a0b:4340:83::/48 Valid None 630 99% 69
2a0b:4340:82::/48 Valid None 3 0%low visibility 3
103.236.224.0/24 Valid Other IRR onlyRADB 671 100% 67
103.236.225.0/24 Valid Other IRR onlyRADB 671 100% 67
104.234.48.0/24 Valid Other IRR onlyRADB 669 99% 67
185.92.209.0/24 Valid Other IRR onlyRADB 669 99% 67
206.206.91.0/24 Valid Other IRR onlyRADB 666 99% 67
43.243.170.0/24 Valid RIR databaseAPNIC, RADB, RIPE-NONAUTH 671 100% 67
43.243.171.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.38.254.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.51.146.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.115.67.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
194.163.70.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
209.33.176.0/24 Valid RIR databaseRIPE 671 100% 67
43.240.14.0/24 Valid RIR databaseAPNIC, RADB 666 99% 67
64.113.11.0/24 Valid RIR databaseARIN, RADB 666 99% 67
192.228.124.0/23 Valid RIR databaseARIN, RADB 666 99% 67
74.115.6.0/24 Valid RIR databaseARIN, RADB 665 99% 67
185.190.81.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 663 99% 67
74.80.151.0/24 Valid RIR databaseARIN 1 0%low visibility 1
74.80.187.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS134176: AS-PIGNETWORK. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS134176 isn't in the set, or no route object for AS134176 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS134176 in itNot covered
AS-PIGNETWORK RADB 521146,736 Yes 7
RIPE (also) 2183 Yes 7

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

  • ROA: origin4
  • ROA: none7
  • Route object: none7
  • Route object: RIR11
  • Route object: not announced54
ChangePrefix or setDetailFull-table peers
ROA: origin23.172.217.0/24ROAs covering it name AS20057, AS398741, AS400992, not AS134176; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS134176 should announce it, add a ROA for AS134176.12 of 673
Route object: none23.172.217.0/24Route objects for it name AS20057, AS398741, AS400992. Add a route object with origin AS134176 in the RIR database for the space.12 of 673
ROA: origin77.90.154.0/24ROAs covering it name AS42821, not AS134176. If AS134176 should announce it, add a ROA for AS134176.3 of 673
Route object: none77.90.154.0/24Route objects for it name AS42821. Add a route object with origin AS134176 in the RIR database for the space.3 of 673
ROA: origin108.165.214.0/24ROAs covering it name AS211373, not AS134176. If AS134176 should announce it, add a ROA for AS134176.1 of 673
Route object: none108.165.214.0/24Route objects for it name AS60721, AS211373. Add a route object with origin AS134176 in the RIR database for the space.1 of 673
ROA: origin185.253.54.0/24ROAs covering it name AS198831, AS212815, AS215607, not AS134176. If AS134176 should announce it, add a ROA for AS134176.1 of 673
Route object: none185.253.54.0/24No route object for it. Add a route object with origin AS134176 in the RIR database for the space.1 of 673
ROA: none2602:f6a0::/40No ROA covers it. Add a ROA for AS134176, maxLength 40.629 of 636
Route object: none2602:f6a0::/40Route objects for it name AS13875. Add a route object with origin AS134176 in the RIR database for the space.629 of 636
ROA: none103.149.132.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.671 of 673
Route object: RIR103.149.132.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.149.133.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.671 of 673
Route object: RIR103.149.133.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.185.228.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.671 of 673
Route object: RIR103.185.228.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.185.229.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.671 of 673
Route object: RIR103.185.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none172.247.36.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.670 of 673
Route object: RIR172.247.36.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673
ROA: none172.247.37.0/24No ROA covers it. Add a ROA for AS134176, maxLength 24.670 of 673
Route object: RIR172.247.37.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673
Route object: none2a0b:4340:83::/48No route object for it. Add a route object with origin AS134176 in the RIR database for the space.630 of 636
Route object: none2a0b:4340:82::/48No route object for it. Add a route object with origin AS134176 in the RIR database for the space.3 of 636
Route object: RIR103.236.224.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.236.225.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.234.48.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR185.92.209.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.206.91.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

23.185.184.0/24ARINNo ROA
24.249.245.0/24RADBValid
43.241.166.0/24NTTCOM, RADBNo ROA
43.243.170.0/23RIPE-NONAUTHNo ROA
45.121.208.0/22NTTCOM, RADBNo ROA
49.128.208.0/24RADBNo ROA
103.62.48.0/22NTTCOM, RADBNo ROA
103.74.200.0/22NTTCOM, RADBNo ROA
103.101.28.0/22RADBNo ROA
103.101.29.0/24RADBNo ROA
103.104.148.0/22NTTCOM, RADBNo ROA
103.107.196.0/22NTTCOM, RADBNo ROA
103.116.8.0/22NTTCOM, RADBNo ROA
103.118.40.0/22APNIC, NTTCOMValid
103.118.40.0/23APNICValid
103.118.40.0/24APNICValid
103.118.41.0/24APNICValid
103.118.42.0/23APNICValid
103.118.42.0/24APNICValid
103.118.43.0/24APNICValid
103.118.255.0/24RADBValid
103.122.116.0/22NTTCOMNo ROA
103.122.224.0/22NTTCOM, RADBNo ROA
103.131.148.0/22RADBNo ROA
103.137.12.0/22NTTCOM, RADBNo ROA
103.139.198.0/23NTTCOM, RADBNo ROA
103.140.202.0/23NTTCOM, RADBNo ROA
103.142.244.0/23NTTCOM, RADBNo ROA
103.149.132.0/23APNIC, RADBNo ROA
103.170.72.0/24APNICValid
103.212.224.0/22NTTCOM, RADBNo ROA
103.231.84.0/23RADBNo ROA
109.121.34.0/24RADBValid
114.199.64.0/20NTTCOM, RADBNo ROA
114.199.69.0/24NTTCOM, RADBNo ROA
142.248.112.0/22RADBNo ROA
150.242.36.0/22RADBNo ROA
150.242.38.0/24RADBNo ROA
156.227.28.0/22NTTCOMNo ROA
172.247.33.0/24RADBNo ROA
184.178.169.0/24RADBValid
185.203.36.0/22NTTCOM, RADBNo ROA
194.163.69.0/24RIPEInvalid: origin
195.180.179.0/24RADBNo ROA
195.252.172.0/24RIPEInvalid: origin
203.81.176.0/21NTTCOM, RADBNo ROA
204.235.240.0/24ARINValid
204.235.242.0/24ARINValid
207.228.200.0/24ARIN, RADBValid
207.228.201.0/24ARIN, RADBValid
207.228.202.0/24ARIN, RADBValid
207.228.203.0/24ARIN, RADBValid
2a0b:4340:80::/48RIPEValid
2a0b:4340:81::/48RIPEValid

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.