Network · data from 2026-11-12

AS63940 DRAGONHISPEED-AS-AP - dragonhispeed

Registry name: DRAGONHISPEED-AS-AP - dragonhispeed, TH · not in PeeringDB

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

0IPv6 routes

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 AS63940, seen from no peer

Announced routes

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


27.254.152.0/23	Valid	RIR databaseAPNIC, RADB	673 100%	66
27.254.146.0/23	Valid	RIR databaseAPNIC, RADB	672 100%	66
27.254.146.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
27.254.147.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
27.254.152.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
27.254.153.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
43.241.56.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	68
43.241.56.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
43.241.57.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
43.241.58.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
43.241.59.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
103.4.216.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	68
103.4.216.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
103.4.217.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
103.4.218.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
103.4.219.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68

AS-SET

AS63940 isn't in PeeringDB, where networks name their 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 AS63940 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.