Network · data from 2026-11-12

AS151333 ASCON TEL (PRIVATE) LIMITED

Registry name: ASCONTEL-AS-AP - ASCON TEL (PRIVATE) LIMITED, PK · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 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

0Route objects not announced registered with origin AS151333, seen from no peer

Announced routes

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


103.199.140.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.199.141.0/24	Valid	RIR databaseAPNIC	672 100%	66
163.52.244.0/24	Valid	RIR databaseAPNIC	672 100%	66
163.52.245.0/24	Valid	RIR databaseAPNIC	672 100%	66
2001:df2:70c0::/48	Valid	RIR databaseAPNIC	636 100%	69
2001:df2:70c1::/48	Valid	RIR databaseAPNIC	636 100%	69
2001:df7:9440::/48	Valid	RIR databaseAPNIC	636 100%	69

AS-SET

AS151333's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS151333 is announced.

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.