bgpreport

Network · data from 2026-11-12

AS9892 ICONZ-Webvisions Pte Ltd

Registry name: ICONZ-WEBVISIONS-AP - Iconz-Webvisions Pte. Ltd., SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9892, 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.
123.100.244.0/23 Valid RIR databaseAPNIC 673 100% 66
202.157.128.0/21 Valid RIR databaseAPNIC 673 100% 66
202.157.160.0/21 Valid RIR databaseAPNIC 673 100% 66
202.157.168.0/21 Valid RIR databaseAPNIC 673 100% 66
203.142.16.0/21 Valid RIR databaseAPNIC 673 100% 66
114.129.33.0/24 Valid RIR databaseAPNIC 671 100% 66
114.129.36.0/24 Valid RIR databaseAPNIC 671 100% 66
114.129.38.0/24 Valid RIR databaseAPNIC 671 100% 66
114.129.41.0/24 Valid RIR databaseAPNIC 671 100% 66
114.129.46.0/24 Valid RIR databaseAPNIC 671 100% 66
123.100.236.0/24 Valid RIR databaseAPNIC 671 100% 66
123.100.237.0/24 Valid RIR databaseAPNIC 671 100% 66
123.100.238.0/23 Valid RIR databaseAPNIC 671 100% 66
123.100.241.0/24 Valid RIR databaseAPNIC 671 100% 66
123.100.251.0/24 Valid RIR databaseAPNIC 671 100% 66
123.100.252.0/24 Valid RIR databaseAPNIC 671 100% 66
202.157.136.0/22 Valid RIR databaseAPNIC 671 100% 66
202.157.142.0/23 Valid RIR databaseAPNIC 671 100% 66
202.157.148.0/24 Valid RIR databaseAPNIC 671 100% 66
202.157.152.0/24 Valid RIR databaseAPNIC 671 100% 66
203.142.27.0/24 Valid RIR databaseAPNIC 671 100% 66
2404:4800::/48 Valid RIR databaseAPNIC 636 100% 70
2404:4800:1::/48 Valid RIR databaseAPNIC 636 100% 70
2404:4800:2::/48 Valid RIR databaseAPNIC 636 100% 70
2404:4800:3::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2404:4800:20::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS9892's PeeringDB record names no 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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

114.129.36.0/22APNICValid
114.129.40.0/23APNICValid
114.129.45.0/24APNICValid
114.129.47.0/24APNICValid
123.100.235.0/24APNICValid
123.100.236.0/22APNICValid
123.100.244.0/24APNICValid
123.100.245.0/24APNICValid
202.157.128.0/20APNICNo ROA
202.157.144.0/22APNICNo ROA
202.157.149.0/24APNICInvalid: origin
202.157.150.0/24APNICInvalid: origin
202.157.152.0/21APNICNo ROA
202.157.160.0/20APNICValid
202.160.120.0/24APNICValid
202.160.121.0/24APNICValid
202.160.122.0/24APNICValid
202.160.123.0/24APNICValid

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.