Network · data from 2026-11-12

AS153385 PICO-AS-AP - Pico Public Cloud Limited

Registry name: PICO-AS-AP - Pico Public Cloud Limited, BD · not in PeeringDB

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

3IPv6 routes 66.7% RPKI valid · 66.7% with a route object

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

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

Announced routes

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


2401:d260::/48	Invalid: maxLength	Nonecovered by 2401:d260::/32	105 17%	43
103.12.205.0/24	Valid	RIR databaseAPNIC	670 100%	67
103.18.83.0/24	Valid	RIR databaseAPNIC	670 100%	66
160.191.150.0/24	Valid	RIR databaseAPNIC	670 100%	67
2401:d260::/32	Valid	RIR databaseAPNIC	635 100%	69
2403:9300::/32	Valid	RIR databaseAPNIC	635 100%	69

AS-SET

AS153385 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 2 are in fix.csv.

ROA: maxLength1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2401:d260::/48	ROA 2401:d260::/32 AS153385 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:d260::/48.	105 of 636
Route object: none	2401:d260::/48	No route object for it. A route object for 2401:d260::/32 with origin AS153385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS153385 in the RIR database for the space.	105 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2401:d260::/48

ROA 2401:d260::/32 AS153385 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:d260::/48.

105 of 636

Route object: none

2401:d260::/48

No route object for it. A route object for 2401:d260::/32 with origin AS153385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS153385 in the RIR database for the space.

105 of 636

Route objects not announced

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