Network · data from 2026-11-12

AS17804 LAODC-AS-AP - Lao Data Center (LaoDC)

Registry name: LAODC-AS-AP - Lao Data Center (LaoDC), LA · not in PeeringDB

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

1IPv6 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 AS17804, seen from no peer

Announced routes

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


103.26.103.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.82.56.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
103.228.101.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
185.19.104.0/22	Valid	RIR databaseAPNIC, RADB	673 100%	68
185.109.87.0/24	Valid	RIR databaseNTTCOM, RADB, RIPE	673 100%	68
2400:81c0::/32	Valid	RIR databaseAPNIC, RADB	636 100%	69

AS-SET

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