Network · data from 2026-11-12

AS133504 PAOCLOUD

Registry name: PCLONET-AS-AP - PAOCLOUD CO., LTD., TH · PeeringDB

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

14IPv6 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 AS133504, seen from no peer

Announced routes

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


151.243.55.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
2602:fed2:7e83::/48	Valid	RIR databaseARIN	636 100%	69
2a05:dfc3:f700::/44	Valid	RIR databaseRIPE	636 100%	69
2a05:dfc3:f710::/44	Valid	RIR databaseRIPE	636 100%	69
2a05:dfc3:f720::/44	Valid	RIR databaseRIPE	636 100%	69
2a05:dfc3:f750::/44	Valid	RIR databaseRADB, RIPE	636 100%	67
2a06:1281:80::/44	Valid	RIR databaseRIPE	636 100%	69
2a09:17c0:1000::/48	Valid	RIR databaseRIPE	636 100%	69
2a13:9500:69::/48	Valid	RIR databaseRIPE	636 100%	69
2602:f72e:3f::/48	Valid	RIR databaseARIN	635 100%	69
2602:f96d:fff::/48	Valid	RIR databaseARIN	635 100%	69
2a05:dfc3:f700::/40	Valid	RIR databaseRIPE	635 100%	69
2a05:dfc3:f730::/44	Valid	RIR databaseRIPE	635 100%	69
2401:93e0:5::/48	Valid	RIR databaseAPNIC	634 100%	70
2a05:dfc3:f760::/44	Valid	RIR databaseRIPE	634 100%	70

AS-SET

PeeringDB's irr_as_set for AS133504: AS133504:AS-PCLONET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133504 isn't in the set, or no route object for AS133504 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS133504 in it	Not covered
AS133504:AS-PCLONET	APNIC	1	1	15	Yes	0

Name

Database

ASNs

Sets

Route objects

AS133504 in it

Not covered

AS133504:AS-PCLONET

APNIC

Yes

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 AS133504 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.