bgpreport

Network · data from 2026-11-12

AS9911 CONNECTPLUS-AP - Singapore Telecom

Registry name: CONNECTPLUS-AP - Singapore Telecom, SG · not in PeeringDB

12IPv4 routes 8.3% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
11No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
183Route objects not announced registered with origin AS9911, seen from no peer

Announced routes

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

101.192.76.0/22 No ROA Other IRR onlyRADB 671 100% 67
101.192.80.0/22 No ROA Other IRR onlyRADB 671 100% 67
101.193.84.0/22 No ROA Other IRR onlyRADB 671 100% 67
101.193.88.0/22 No ROA Other IRR onlyRADB 671 100% 67
101.193.92.0/22 No ROA Other IRR onlyRADB 671 100% 67
117.120.200.0/22 No ROA Other IRR onlyRADB 671 100% 67
117.120.204.0/22 No ROA Other IRR onlyRADB 671 100% 67
117.120.240.0/22 No ROA Other IRR onlyRADB 671 100% 67
117.120.244.0/22 No ROA Other IRR onlyRADB 671 100% 67
211.102.176.0/22 No ROA Other IRR onlyRADB 671 100% 67
211.102.180.0/22 No ROA Other IRR onlyRADB 671 100% 67
103.114.72.0/22 Valid Other IRR onlyRADB 670 100% 67

AS-SET

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

  • ROA: none11
  • Route object: RIR12
  • Route object: not announced183
ChangePrefix or setDetailFull-table peers
ROA: none101.192.76.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR101.192.76.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none101.192.80.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR101.192.80.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none101.193.84.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR101.193.84.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none101.193.88.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR101.193.88.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none101.193.92.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR101.193.92.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none117.120.200.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR117.120.200.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none117.120.204.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR117.120.204.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none117.120.240.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR117.120.240.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none117.120.244.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR117.120.244.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none211.102.176.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR211.102.176.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none211.102.180.0/22No ROA covers it. Add a ROA for AS9911, maxLength 22.671 of 673
Route object: RIR211.102.180.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.114.72.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

91.103.9.0/24RIPENo ROA
131.197.228.0/24RADBNo ROA
131.197.229.0/24RADBNo ROA
131.197.238.0/23RADBNo ROA
156.48.252.0/24RADBNo ROA
158.116.216.0/24RADBNo ROA
161.51.16.0/22RADBNo ROA
192.23.168.0/24RADBNo ROA
192.88.175.0/24RADBNo ROA
192.232.67.0/24RADBNo ROA
192.232.69.0/24RADBNo ROA
199.33.84.0/22RADBNo ROA
202.27.16.0/24RADBNo ROA
202.27.17.0/24RADBNo ROA
202.27.18.0/24RADBNo ROA
202.27.20.0/24RADBNo ROA
202.27.21.0/24RADBNo ROA
202.27.23.0/24RADBNo ROA
202.40.224.0/19APNICValid
202.40.224.0/20APNICValid
202.40.224.0/21APNICValid
202.40.224.0/22APNICValid
202.40.224.0/23APNICValid
202.40.224.0/24APNIC, RADBValid
202.40.225.0/24APNIC, RADBValid
202.40.226.0/23APNICValid
202.40.226.0/24APNIC, RADBValid
202.40.227.0/24APNIC, RADBValid
202.40.228.0/22APNICValid
202.40.228.0/23APNICValid
202.40.228.0/24APNICValid
202.40.229.0/24APNICValid
202.40.230.0/23APNICValid
202.40.230.0/24APNICValid
202.40.231.0/24APNIC, RADBValid
202.40.232.0/21APNICValid
202.40.232.0/22APNICValid
202.40.232.0/23APNICValid
202.40.232.0/24APNICValid
202.40.233.0/24APNIC, RADBValid
202.40.234.0/23APNICValid
202.40.234.0/24APNIC, RADBValid
202.40.235.0/24APNICValid
202.40.236.0/22APNICValid
202.40.236.0/23APNICValid
202.40.236.0/24APNICValid
202.40.237.0/24APNICValid
202.40.238.0/23APNICValid
202.40.238.0/24APNICValid
202.40.239.0/24APNIC, RADBValid
202.40.240.0/20APNICValid
202.40.240.0/21APNICValid
202.40.240.0/22APNICValid
202.40.240.0/23APNICValid
202.40.240.0/24APNICValid
202.40.241.0/24APNICValid
202.40.242.0/23APNICValid
202.40.242.0/24APNICValid
202.40.243.0/24APNIC, RADBValid
202.40.244.0/22APNICValid
202.40.244.0/23APNICValid
202.40.244.0/24APNICValid
202.40.245.0/24APNICValid
202.40.246.0/23APNICValid
202.40.246.0/24APNICValid
202.40.247.0/24APNICValid
202.40.248.0/21APNICValid
202.40.248.0/22APNICValid
202.40.248.0/23APNICValid
202.40.248.0/24APNICValid
202.40.249.0/24APNICValid
202.40.250.0/23APNICValid
202.40.250.0/24APNICValid
202.40.251.0/24APNICValid
202.40.252.0/22APNICValid
202.40.252.0/23APNICValid
202.40.252.0/24APNICValid
202.40.253.0/24APNICValid
202.40.254.0/23APNICValid
202.40.254.0/24APNICValid
202.40.255.0/24APNICValid
202.91.32.0/21RADBNo ROA
202.176.192.0/19APNICValid
202.176.192.0/24APNIC, RADBValid
202.176.193.0/24APNIC, RADBValid
202.176.194.0/24APNIC, RADBValid
202.176.195.0/24APNIC, RADBValid
202.176.196.0/24APNIC, RADBValid
202.176.197.0/24APNIC, RADBValid
202.176.198.0/24APNIC, RADBValid
202.176.199.0/24APNIC, RADBValid
202.176.200.0/24APNIC, RADBValid
202.176.201.0/24APNIC, RADBValid
202.176.202.0/24APNIC, RADBValid
202.176.203.0/24APNIC, RADBValid
202.176.204.0/24APNIC, RADBValid
202.176.205.0/24APNIC, RADBValid
202.176.206.0/24APNIC, RADBValid
202.176.207.0/24APNIC, RADBValid
202.176.208.0/24APNICValid
202.176.209.0/24APNIC, RADBValid
202.176.210.0/24APNICValid
202.176.211.0/24APNICValid
202.176.212.0/24APNICValid
202.176.213.0/24APNICValid
202.176.214.0/24APNICValid
202.176.215.0/24APNICValid
202.176.216.0/24APNIC, RADBValid
202.176.217.0/24APNIC, RADBValid
202.176.218.0/24APNIC, RADBValid
202.176.219.0/24APNIC, RADBValid
202.176.220.0/24APNIC, RADBValid
202.176.221.0/24APNIC, RADBValid
202.176.222.0/24APNIC, RADBValid
202.176.223.0/24APNIC, RADBValid
203.208.128.0/24APNICValid
203.208.144.0/24APNIC, RADBValid
203.208.224.0/19APNIC, RADBValid
203.208.224.0/24APNIC, RADBValid
203.208.225.0/24APNIC, RADBValid
203.208.226.0/24RADBValid
203.208.227.0/24APNIC, RADBValid
203.208.228.0/24APNIC, RADBValid
203.208.229.0/24APNIC, RADBValid
203.208.230.0/24APNIC, RADBValid
203.208.231.0/24APNIC, RADBValid
203.208.232.0/24APNIC, RADBValid
203.208.233.0/24APNIC, RADBValid
203.208.235.0/24APNIC, RADBValid
203.208.236.0/24APNIC, RADBValid
203.208.237.0/24APNIC, RADBValid
203.208.238.0/24APNICValid
203.208.239.0/24APNIC, RADBValid
203.208.240.0/24APNIC, RADBValid
203.208.241.0/24APNIC, RADBValid
203.208.242.0/24APNIC, RADBValid
203.208.243.0/24APNIC, RADBValid
203.208.244.0/24APNIC, RADBValid
203.208.245.0/24RADBValid
203.208.246.0/24APNIC, RADBValid
203.208.247.0/24APNIC, RADBValid
203.208.248.0/24APNIC, RADBValid
203.208.249.0/24APNIC, RADBValid
203.208.250.0/24APNIC, RADBValid
203.208.251.0/24APNIC, RADBValid
203.208.252.0/24APNIC, RADBValid
203.208.253.0/24APNIC, RADBValid
203.208.254.0/24APNIC, RADBValid
203.208.255.0/24APNICValid
216.245.49.0/24RADBNo ROA
216.245.50.0/24RADBNo ROA
216.245.51.0/24RADBNo ROA
216.245.52.0/24RADBNo ROA
216.245.53.0/24RADBNo ROA
216.245.54.0/24RADBNo ROA
216.245.55.0/24RADBNo ROA
216.245.56.0/24RADBNo ROA
216.245.57.0/24RADBNo ROA
216.245.58.0/24RADBNo ROA
216.245.60.0/24RADBNo ROA
216.245.61.0/24RADBNo ROA
216.245.62.0/24RADBNo ROA
2404:5800::/40APNICValid
2404:5800:100::/48APNICValid
2404:5800:101::/48APNICValid
2404:5800:102::/48APNICValid
2404:5800:103::/48APNICValid
2404:5800:104::/46APNICValid
2404:5800:104::/48APNICValid
2404:5800:105::/48APNICValid
2404:5800:106::/48APNICValid
2404:5800:107::/48APNICValid
2404:5800:108::/45APNICValid
2404:5800:110::/44APNICValid
2404:5800:120::/43APNICValid
2404:5800:140::/42APNICValid
2404:5800:180::/41APNICValid
2404:5800:200::/39APNICValid
2404:5800:800::/37APNICValid
2404:5800:1000::/36APNICValid
2404:5800:2000::/35APNICValid
2404:5800:4000::/34APNICValid
2404:5800:8000::/33APNICValid

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.