Network · data from 2026-11-12

AS136356 Purenet Telecom India

Registry name: PURENETT-AS - Purenet Telecom India Pvt. Ltd., IN · PeeringDB

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

1IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS136356, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136356, 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:df1:100::/48	No ROA	RIR databaseAPNIC	636 100%	70
103.91.62.0/24	Valid	RIR databaseAPNIC	672 100%	66
103.153.250.0/24	Valid	RIR databaseAPNIC	672 100%	66

AS-SET

AS136356'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 1 are in fix.csv.

ROA: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2001:df1:100::/48	No ROA covers it. Add a ROA for AS136356, maxLength 48.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2001:df1:100::/48

No ROA covers it. Add a ROA for AS136356, maxLength 48.

636 of 636

Route objects not announced

Every route object with origin AS136356 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.