bgpreport

Network · data from 2026-11-12

AS9255 CONNECTPLUS-AS - Singapore Telecom

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

40IPv4 routes 70.0% RPKI valid · 75.0% with a route object
55IPv6 routes 83.6% RPKI valid · 83.6% with a route object
8RPKI invalid 8 origin · 0 maxLength
13No ROA 19 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
72Route objects not announced registered with origin AS9255, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9255, 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.
2001:c20:48e9::/48 Invalid: origin None 20 3%low visibility 12
2001:c20:48ea::/48 Invalid: origin None 20 3%low visibility 12
2001:c20:c816::/48 Invalid: origin None 20 3%low visibility 12
2001:c20:c81a::/48 Invalid: origin None 20 3%low visibility 12
2001:c20:c81d::/48 Invalid: origin None 20 3%low visibility 12
2001:c20:c81e::/48 Invalid: origin None 19 3%low visibility 11
2001:c20:c81f::/48 Invalid: origin None 19 3%low visibility 11
2001:d98:29::/127 Invalid: origin None 1 0%low visibility 1
122.200.28.0/24 No ROA Other origin only 673 100% 67
144.46.124.0/24 No ROA Other origin onlycovered by 144.46.124.0/23 673 100% 67
144.46.125.0/24 No ROA Other origin onlycovered by 144.46.124.0/23 673 100% 67
158.155.250.0/24 No ROA Other origin only 673 100% 67
103.102.235.0/24 No ROA None 671 100% 67
143.223.80.0/24 No ROA None 671 100% 67
143.223.81.0/24 No ROA None 671 100% 67
185.82.163.0/24 No ROA None 671 100% 67
206.221.40.0/24 No ROA None 669 99% 67
103.108.252.0/24 No ROA Other origin only 665 99% 67
2001:df0:30f::/48 No ROA None 632 99% 68
157.234.216.0/24 No ROA Other IRR onlyRADB 673 100% 67
138.103.32.0/22 No ROA RIR databaseRIPE 672 100% 67
118.201.16.0/20 Valid RIR databaseAPNIC 673 100% 67
118.201.81.0/24 Valid RIR databaseAPNIC 673 100% 67
128.106.9.0/24 Valid RIR databaseAPNIC 673 100% 67
151.192.0.0/21 Valid RIR databaseAPNIC 673 100% 67
151.192.8.0/21 Valid RIR databaseAPNIC 673 100% 67
151.192.16.0/21 Valid RIR databaseAPNIC 673 100% 67
151.192.24.0/21 Valid RIR databaseAPNIC 673 100% 67
151.192.32.0/21 Valid RIR databaseAPNIC 673 100% 67
151.192.48.0/24 Valid RIR databaseAPNIC 673 100% 67
180.255.29.0/24 Valid RIR databaseAPNIC 673 100% 67
194.124.188.0/24 Valid RIR databaseRIPE 673 100% 67
203.125.128.0/24 Valid RIR databaseAPNIC 673 100% 67
203.126.8.0/24 Valid RIR databaseAPNIC 673 100% 67
203.126.130.0/24 Valid RIR databaseAPNIC 673 100% 67
203.126.133.0/24 Valid RIR databaseAPNIC 673 100% 67
203.126.134.0/24 Valid RIR databaseAPNIC 673 100% 67
203.126.147.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.3.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.10.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.31.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.104.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.181.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.201.0/24 Valid RIR databaseAPNIC 673 100% 67
203.127.202.0/24 Valid RIR databaseAPNIC 673 100% 67
118.201.12.0/22 Valid RIR databaseAPNIC 672 100% 67
128.106.8.0/24 Valid RIR databaseAPNIC 671 100% 67
128.106.84.0/22 Valid RIR databaseAPNIC 671 100% 67
128.106.156.0/23 Valid RIR databaseAPNIC 671 100% 67
2001:c20:4849::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:485e::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:485f::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:486c::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4871::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4874::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:487e::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4884::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4887::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:488c::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:488d::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:488f::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4892::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4894::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:4895::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48a0::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48a6::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48ae::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48af::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48b0::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48b8::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48c2::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48c4::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48c6::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48cc::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48da::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48dc::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48e6::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48e7::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48f0::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c819::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c824::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c825::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c826::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c827::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c831::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c835::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c839::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c83f::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c844::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c847::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c84e::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:c856::/48 Valid RIR databaseAPNIC 635 100% 69
2001:c20:48db::/48 Valid RIR databaseAPNIC 634 100% 69
2001:c20:489a::/48 Valid RIR databaseAPNIC 4 1%low visibility 4
2001:c20:48d6::/48 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

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

  • ROA: origin8
  • ROA: none13
  • Route object: none19
  • Route object: RIR1
  • Route object: not announced72
ChangePrefix or setDetailFull-table peers
ROA: origin2001:c20:48e9::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.20 of 636
Route object: none2001:c20:48e9::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.20 of 636
ROA: origin2001:c20:48ea::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.20 of 636
Route object: none2001:c20:48ea::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.20 of 636
ROA: origin2001:c20:c816::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.20 of 636
Route object: none2001:c20:c816::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.20 of 636
ROA: origin2001:c20:c81a::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.20 of 636
Route object: none2001:c20:c81a::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.20 of 636
ROA: origin2001:c20:c81d::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.20 of 636
Route object: none2001:c20:c81d::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.20 of 636
ROA: origin2001:c20:c81e::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.19 of 636
Route object: none2001:c20:c81e::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.19 of 636
ROA: origin2001:c20:c81f::/48ROAs covering it name AS3758, not AS9255. If AS9255 should announce it, add a ROA for AS9255.19 of 636
Route object: none2001:c20:c81f::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.19 of 636
ROA: origin2001:d98:29::/127ROAs covering it name AS18106, not AS9255. If AS9255 should announce it, add a ROA for AS9255.1 of 636
Route object: none2001:d98:29::/127No route object for it. Add a route object with origin AS9255 in the RIR database for the space.1 of 636
ROA: none122.200.28.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.673 of 673
Route object: none122.200.28.0/24Route objects for it name AS3758. Add a route object with origin AS9255 in the RIR database for the space.673 of 673
ROA: none144.46.124.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.673 of 673
Route object: none144.46.124.0/24Route objects for it name AS19905. A route object for 144.46.124.0/23 with origin AS9255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9255 in the RIR database for the space.673 of 673
ROA: none144.46.125.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.673 of 673
Route object: none144.46.125.0/24Route objects for it name AS19905. A route object for 144.46.124.0/23 with origin AS9255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9255 in the RIR database for the space.673 of 673
ROA: none158.155.250.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.673 of 673
Route object: none158.155.250.0/24Route objects for it name AS2687. Add a route object with origin AS9255 in the RIR database for the space.673 of 673
ROA: none103.102.235.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.671 of 673
Route object: none103.102.235.0/24No route object for it. Add a route object with origin AS9255 in the RIR database for the space.671 of 673
ROA: none143.223.80.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.671 of 673
Route object: none143.223.80.0/24No route object for it. Add a route object with origin AS9255 in the RIR database for the space.671 of 673
ROA: none143.223.81.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.671 of 673
Route object: none143.223.81.0/24No route object for it. Add a route object with origin AS9255 in the RIR database for the space.671 of 673
ROA: none185.82.163.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.671 of 673
Route object: none185.82.163.0/24No route object for it. Add a route object with origin AS9255 in the RIR database for the space.671 of 673
ROA: none206.221.40.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.669 of 673
Route object: none206.221.40.0/24No route object for it. Add a route object with origin AS9255 in the RIR database for the space.669 of 673
ROA: none103.108.252.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.665 of 673
Route object: none103.108.252.0/24Route objects for it name AS137456. Add a route object with origin AS9255 in the RIR database for the space.665 of 673
ROA: none2001:df0:30f::/48No ROA covers it. Add a ROA for AS9255, maxLength 48.632 of 636
Route object: none2001:df0:30f::/48No route object for it. Add a route object with origin AS9255 in the RIR database for the space.632 of 636
ROA: none157.234.216.0/24No ROA covers it. Add a ROA for AS9255, maxLength 24.673 of 673
Route object: RIR157.234.216.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none138.103.32.0/22No ROA covers it. Add a ROA for AS9255, maxLength 22.672 of 673

Route objects not announced

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

116.12.224.0/24APNICValid
118.201.157.0/24APNICValid
129.192.198.0/23RADBNo ROA
144.46.124.0/23RADBNo ROA
146.255.124.0/22RADBValid
185.170.127.0/24RIPENo ROA
203.120.124.0/24APNICValid
203.126.137.0/24APNICValid
203.127.2.0/24APNICValid
203.127.111.0/24APNICValid
203.127.135.0/24APNICValid
203.127.146.0/24APNICValid
203.127.148.0/24APNICValid
203.127.200.0/24APNICValid
2001:c20:405::/48APNICValid
2001:c20:4844::/48APNICValid
2001:c20:484a::/48APNICValid
2001:c20:4861::/48APNICValid
2001:c20:4865::/48APNICValid
2001:c20:4868::/48APNICValid
2001:c20:486a::/48APNICValid
2001:c20:486e::/48APNICValid
2001:c20:4875::/48APNICValid
2001:c20:4878::/48APNICValid
2001:c20:4879::/48APNICValid
2001:c20:487b::/48APNICValid
2001:c20:487f::/48APNICValid
2001:c20:4885::/48APNICValid
2001:c20:4886::/48APNICValid
2001:c20:488b::/48APNICValid
2001:c20:488e::/48APNICValid
2001:c20:4891::/48APNICValid
2001:c20:4893::/48APNICValid
2001:c20:4896::/48APNICValid
2001:c20:4898::/48APNICValid
2001:c20:48a2::/48APNICValid
2001:c20:48a3::/48APNICValid
2001:c20:48a4::/48APNICValid
2001:c20:48aa::/48APNICValid
2001:c20:48ab::/48APNICValid
2001:c20:48ad::/48APNICValid
2001:c20:48b1::/48APNICValid
2001:c20:48b2::/48APNICValid
2001:c20:48b5::/48APNICValid
2001:c20:48b6::/48APNICValid
2001:c20:48b7::/48APNICValid
2001:c20:48b9::/48APNICValid
2001:c20:48ba::/48APNICValid
2001:c20:48c6::/47APNICValid
2001:c20:48ce::/48APNICValid
2001:c20:48d0::/48APNICValid
2001:c20:48d5::/48APNICValid
2001:c20:48d8::/48APNICValid
2001:c20:48e8::/48APNICValid
2001:c20:5009::/48APNICValid
2001:c20:8409::/48APNICValid
2001:c20:c80a::/48APNICValid
2001:c20:c80d::/48APNICValid
2001:c20:c80e::/48APNICValid
2001:c20:c80f::/48APNICValid
2001:c20:c811::/48APNICValid
2001:c20:c814::/48APNICValid
2001:c20:c815::/48APNICValid
2001:c20:c833::/48APNICValid
2001:c20:c837::/48APNICValid
2001:c20:c840::/48APNICValid
2001:c20:c842::/48APNICValid
2001:c20:c84c::/48APNICValid
2001:c20:c84d::/48APNICValid
2001:c20:c854::/48APNICValid
2001:c20:c855::/48APNICValid
2001:c20:e808::/48APNICValid

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.