bgpreport

Network · data from 2026-11-12

AS154162 ISIF SaaS

Registry name: ISIF-AS-AP - ISIF LIMITED, HK · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
97Route objects not announced registered with origin AS154162, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS154162, 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.
49.143.250.0/24 Valid RIR databaseAPNIC 671 100% 66
2402:2520::/48 Valid RIR databaseAPNIC 632 99% 69

AS-SET

AS154162'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 97 are in fix.csv.

  • Route object: not announced97

Route objects not announced

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

49.143.250.0/23APNIC, RADBValid
49.143.251.0/24APNICValid
209.248.32.0/19RADBValid
209.248.32.0/20RADBValid
209.248.32.0/21RADBValid
209.248.32.0/22RADBValid
209.248.32.0/23RADBValid
209.248.32.0/24RADBValid
209.248.33.0/24RADBValid
209.248.34.0/23RADBValid
209.248.34.0/24RADBValid
209.248.35.0/24RADBValid
209.248.36.0/22RADBValid
209.248.36.0/23RADBValid
209.248.36.0/24RADBValid
209.248.37.0/24RADBValid
209.248.38.0/23RADBValid
209.248.38.0/24RADBValid
209.248.39.0/24RADBValid
209.248.40.0/21RADBValid
209.248.40.0/22RADBValid
209.248.40.0/23RADBValid
209.248.40.0/24RADBValid
209.248.41.0/24RADBValid
209.248.42.0/23RADBValid
209.248.42.0/24RADBValid
209.248.43.0/24RADBValid
209.248.44.0/22RADBValid
209.248.44.0/23RADBValid
209.248.44.0/24RADBValid
209.248.45.0/24RADBValid
209.248.46.0/23RADBValid
209.248.46.0/24RADBValid
209.248.47.0/24RADBValid
209.248.48.0/20RADBValid
209.248.48.0/21RADBValid
209.248.48.0/22RADBValid
209.248.48.0/23RADBValid
209.248.48.0/24RADBValid
209.248.49.0/24RADBValid
209.248.50.0/23RADBValid
209.248.50.0/24RADBValid
209.248.51.0/24RADBValid
209.248.52.0/22RADBValid
209.248.52.0/23RADBValid
209.248.52.0/24RADBValid
209.248.53.0/24RADBValid
209.248.54.0/23RADBValid
209.248.54.0/24RADBValid
209.248.55.0/24RADBValid
209.248.56.0/21RADBValid
209.248.56.0/22RADBValid
209.248.56.0/23RADBValid
209.248.56.0/24RADBValid
209.248.57.0/24RADBValid
209.248.58.0/23RADBValid
209.248.58.0/24RADBValid
209.248.59.0/24RADBValid
209.248.60.0/22RADBValid
209.248.60.0/23RADBValid
209.248.60.0/24RADBValid
209.248.61.0/24RADBValid
209.248.62.0/23RADBValid
209.248.62.0/24RADBValid
209.248.63.0/24RADBValid
2402:2520::/32RADBNo ROA
2402:2520:1000::/44APNICValid
2402:2520:1000::/45APNICValid
2402:2520:1000::/46APNICValid
2402:2520:1000::/47APNICValid
2402:2520:1000::/48APNICValid
2402:2520:1001::/48APNICValid
2402:2520:1002::/47APNICValid
2402:2520:1002::/48APNICValid
2402:2520:1003::/48APNICValid
2402:2520:1004::/46APNICValid
2402:2520:1004::/47APNICValid
2402:2520:1004::/48APNICValid
2402:2520:1005::/48APNICValid
2402:2520:1006::/47APNICValid
2402:2520:1006::/48APNICValid
2402:2520:1007::/48APNICValid
2402:2520:1008::/45APNICValid
2402:2520:1008::/46APNICValid
2402:2520:1008::/47APNICValid
2402:2520:1008::/48APNICValid
2402:2520:1009::/48APNICValid
2402:2520:100a::/47APNICValid
2402:2520:100a::/48APNICValid
2402:2520:100b::/48APNICValid
2402:2520:100c::/46APNICValid
2402:2520:100c::/47APNICValid
2402:2520:100c::/48APNICValid
2402:2520:100d::/48APNICValid
2402:2520:100e::/47APNICValid
2402:2520:100e::/48APNICValid
2402:2520:100f::/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.