bgpreport

Network · data from 2026-11-12

AS55508 INTERNET-LA

Registry name: INTERNET-LA - Lao National Internet Center (LANIC), LA · PeeringDB

11IPv4 routes 81.8% RPKI valid · 81.8% with a route object
0IPv6 routes
2RPKI invalid 0 origin · 2 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS55508, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55508, 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.1.234.0/24 Invalid: maxLength Nonecovered by 103.1.232.0/22 151 22% 57
103.1.235.0/24 Invalid: maxLength Nonecovered by 103.1.232.0/22 112 17% 48
103.1.232.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.1.233.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
157.119.180.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
157.119.180.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
157.119.181.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
157.119.182.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
157.119.183.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.9.76.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
203.110.64.0/20 Valid RIR databaseAPNIC, RADB 673 100% 68

AS-SET

AS55508'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 10 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.1.234.0/24ROA 103.1.232.0/22 AS55508 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.1.234.0/24.151 of 673
Route object: none103.1.234.0/24No route object for it. A route object for 103.1.232.0/22 with origin AS55508 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55508 in the RIR database for the space.151 of 673
ROA: maxLength103.1.235.0/24ROA 103.1.232.0/22 AS55508 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.1.235.0/24.112 of 673
Route object: none103.1.235.0/24No route object for it. A route object for 103.1.232.0/22 with origin AS55508 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55508 in the RIR database for the space.112 of 673

Route objects not announced

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

103.8.0.0/22RADBNo ROA
103.8.0.0/24RADBNo ROA
103.8.1.0/24RADBNo ROA
103.8.2.0/24RADBNo ROA
103.8.3.0/24RADBNo ROA
2001:df0:bf::/48NTTCOMNo ROA

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.