Network · data from 2026-11-12

AS134186 Paradise Technologies

Registry name: PARADISETEC-AS-AP - Paradise Technologies Limited, BD · PeeringDB

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

10IPv6 routes 100.0% RPKI valid · 90.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

5Route objects not announced registered with origin AS134186, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134186, 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:df6:a940::/48	Valid	None	636 100%	70
45.117.60.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.40.166.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.138.24.0/24	Valid	RIR databaseAPNIC	672 100%	66
103.40.167.0/24	Valid	RIR databaseAPNIC	671 100%	67
103.137.73.0/24	Valid	RIR databaseAPNIC	671 100%	68
123.253.223.0/24	Valid	RIR databaseAPNIC	671 100%	67
163.61.153.0/24	Valid	RIR databaseAPNIC	671 100%	68
2402:5e80:1::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:2::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:3::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:4::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:5::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:6::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:7::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:8::/48	Valid	RIR databaseAPNIC	636 100%	70
2402:5e80:9::/48	Valid	RIR databaseAPNIC	636 100%	70

AS-SET

AS134186'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 6 are in fix.csv.

Route object: none1
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	2001:df6:a940::/48	No route object for it. Add a route object with origin AS134186 in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2001:df6:a940::/48

No route object for it. Add a route object with origin AS134186 in the RIR database for the space.

636 of 636

Route objects not announced

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


103.117.110.0/24	APNIC	Valid
2402:5e80::/32	APNIC	Valid
2402:5e80::/48	APNIC	Valid
2402:5e80:a::/48	APNIC	Valid
2402:5e80:b::/48	APNIC	Valid

103.117.110.0/24

APNIC

Valid

2402:5e80::/32

APNIC

Valid

2402:5e80::/48

APNIC

Valid

2402:5e80:a::/48

APNIC

Valid

2402:5e80:b::/48

APNIC

Valid

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.