bgpreport

Network · data from 2026-11-12

AS131642 Pittqiao Network Information Co.

Registry name: PNI-AS-TW - Pittqiao Network Information Co.,Ltd., TW · PeeringDB

54IPv4 routes 100.0% RPKI valid · 96.3% with a route object
3IPv6 routes 100.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
68Route objects not announced registered with origin AS131642, seen from no peer

Announced routes

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

2405:cdc0:1::/48 Valid Nonecovered by 2405:cdc0::/32 634 100% 69
103.127.219.49/32 Valid Nonecovered by 103.127.219.0/24 6 1%low visibility 8
103.137.246.85/32 Valid Nonecovered by 103.137.246.0/24 6 1%low visibility 8
2a13:2200::/47 Valid Other IRR onlyRADB 635 100% 69
103.23.108.0/24 Valid RIR databaseAPNIC 673 100% 67
103.64.21.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.69.80.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.69.81.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.99.138.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.99.139.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
187.79.247.0/24 Valid RIR databaseAPNIC 673 100% 67
103.254.212.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.254.213.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.64.20.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
103.69.80.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
103.99.138.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
103.137.62.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
103.137.246.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
103.137.246.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.148.72.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.157.42.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
103.157.42.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.157.43.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.180.20.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.180.21.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
211.76.176.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
103.127.218.0/23 Valid RIR databaseAPNIC, RADB 670 100% 68
187.79.240.0/21 Valid RIR databaseAPNIC, RADB 670 100% 68
187.79.240.0/23 Valid RIR databaseAPNIC 670 100% 68
103.20.98.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.20.99.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.64.20.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.99.142.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.99.143.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.127.216.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.127.217.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.255.210.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
103.255.211.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
160.191.168.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
160.191.169.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
202.47.172.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
202.47.173.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
2405:cdc0::/32 Valid RIR databaseAPNIC, RADB 633 100% 70
103.69.48.0/24 Valid RIR databaseAPNIC, RADB 421 63% 65
103.137.62.0/24 Valid RIR databaseAPNIC, RADB 366 54% 64
103.137.63.0/24 Valid RIR databaseAPNIC, RADB 366 54% 64
211.76.176.0/24 Valid RIR databaseAPNIC 366 54% 64
211.76.177.0/24 Valid RIR databaseAPNIC 366 54% 64
103.148.73.0/24 Valid RIR databaseAPNIC, RADB 293 44% 59
103.180.20.0/24 Valid RIR databaseAPNIC, RADB 293 44% 59
103.255.40.0/24 Valid RIR databaseAPNIC, RADB 293 44% 59
103.255.41.0/24 Valid RIR databaseAPNIC, RADB 293 44% 59
103.127.218.0/24 Valid RIR databaseAPNIC, RADB 200 30% 56
103.148.72.0/24 Valid RIR databaseAPNIC, RADB 197 29% 57
187.79.240.0/24 Valid RIR databaseAPNIC 197 29% 56
103.127.219.0/24 Valid RIR databaseAPNIC, RADB 184 27% 56
202.148.222.0/23 Valid RIR databaseAPNIC, RADB 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS131642: AS-PQS. 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 (AS131642 isn't in the set, or no route object for AS131642 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 objectsAS131642 in itNot covered
AS-PQS ARIN 121760 Yes 2
APNIC (also) 121759 Yes 2

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

  • Route object: none3
  • Route object: RIR1
  • Route object: not announced68
ChangePrefix or setDetailFull-table peers
Route object: none2405:cdc0:1::/48No route object for it. A route object for 2405:cdc0::/32 with origin AS131642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131642 in the RIR database for the space.634 of 636
Route object: none103.127.219.49/32No route object for it. A route object for 103.127.219.0/24 with origin AS131642 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131642 in the RIR database for the space.6 of 673
Route object: none103.137.246.85/32No route object for it. A route object for 103.137.246.0/24 with origin AS131642 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131642 in the RIR database for the space.6 of 673
Route object: RIR2a13:2200::/47Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

23.188.72.0/24ARINInvalid: origin
23.188.168.0/24ARINInvalid: origin
45.12.62.0/23RADBNo ROA
103.6.124.0/23APNICInvalid: origin
103.6.124.0/24APNICInvalid: origin
103.6.125.0/24APNICInvalid: origin
103.20.98.0/23APNIC, RADBValid
103.23.108.0/23APNICValid
103.23.109.0/24APNICValid
103.69.48.0/23APNIC, RADBValid
103.69.49.0/24APNIC, RADBValid
103.69.52.0/23RADBNo ROA
103.69.52.0/24RADBNo ROA
103.69.53.0/24RADBNo ROA
103.69.54.0/23RADBNo ROA
103.69.54.0/24RADBNo ROA
103.69.55.0/24RADBNo ROA
103.99.140.0/23RADBNo ROA
103.99.140.0/24RADBNo ROA
103.99.141.0/24RADBNo ROA
103.99.142.0/23APNIC, RADBValid
103.127.216.0/23APNIC, RADBValid
103.137.247.0/24APNIC, RADBValid
103.254.212.0/23APNIC, RADBValid
103.255.40.0/23APNIC, RADBValid
103.255.210.0/23APNIC, RADBValid
160.191.168.0/23APNIC, RADBValid
187.79.240.0/22APNICValid
187.79.241.0/24APNICValid
187.79.242.0/23APNICValid
187.79.242.0/24APNICValid
187.79.243.0/24APNICValid
187.79.244.0/22APNICValid
187.79.244.0/23APNICValid
187.79.244.0/24APNICValid
187.79.245.0/24APNICValid
187.79.246.0/23APNICValid
187.79.246.0/24APNICValid
202.47.172.0/23APNIC, RADBValid
202.148.222.0/24APNICValid
202.148.223.0/24APNICValid
207.174.132.0/23ARINValid
207.174.134.0/23ARINValid
2001:470:21e::/48ARINValid
2400:5120::/32RADBNo ROA
2401:26a0::/32RADBNo ROA
2401:2720::/32RADBNo ROA
2401:28e0::/32RADBNo ROA
2401:29e0::/32RADBNo ROA
2401:2a60::/32RADBNo ROA
2401:2b60::/32RADBNo ROA
2401:2fa0::/32RADBNo ROA
2401:3060::/32RADBNo ROA
2401:30a0::/32RADBNo ROA
2401:30e0::/32RADBNo ROA
2401:3920::/32RADBNo ROA
2401:3960::/32RADBNo ROA
2401:39a0::/32RADBNo ROA
2401:39e0::/32RADBNo ROA
2401:3a20::/32RADBNo ROA
2401:4f20::/32RADBNo ROA
2401:d3a0::/32RADBNo ROA
2404:aac0::/32RADBNo ROA
2404:aac0::/44NTTCOM, RADBNo ROA
2404:bac0::/32NTTCOM, RADBNo ROA
2406:9740::/32RADBNo ROA
2602:f825::/40ARINInvalid: origin
2602:f836::/40ARINInvalid: origin

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.