Network · data from 2026-11-12
AS135542 LIGHT CLOUD SDN. BHD.
Registry name: LIGHTCLOUD-AS-AP - LIGHT CLOUD TECHNOLOGY, MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135542, 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.247.247.0/24 | Invalid: origin | Other origin only | 3 0%low visibility |
| 144.79.118.0/24 | Valid | None | 672 100% |
| 144.79.119.0/24 | Valid | None | 672 100% |
| 31.57.65.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 217.217.8.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 103.64.13.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.78.242.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 141.140.14.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS135542: AS-SET-LIGHTCLOUD. 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 (AS135542 isn't in the set, or no route object for AS135542 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 | AS135542 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-SET-LIGHTCLOUD | In no IRR database read today. | |||||
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 11 are in fix.csv.
- ROA: origin1
- Route object: none3
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 151.247.247.0/24 | ROAs covering it name AS834, not AS135542. If AS135542 should announce it, add a ROA for AS135542. |
| Route object: none | 151.247.247.0/24 | Route objects for it name AS834. Add a route object with origin AS135542 in the RIR database for the space. |
| Route object: none | 144.79.118.0/24 | No route object for it. Add a route object with origin AS135542 in the RIR database for the space. |
| Route object: none | 144.79.119.0/24 | No route object for it. Add a route object with origin AS135542 in the RIR database for the space. |
| AS-SET: not found | AS-SET-LIGHTCLOUD | PeeringDB names AS-SET-LIGHTCLOUD; no IRR database read has it. |
Route objects not announced
Route objects with origin AS135542 whose prefix no peer sees AS135542 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.64.12.0/23 | APNIC | Valid |
| 103.78.242.0/23 | APNIC | Valid |
| 109.66.88.0/23 | RADB, RIPE | Valid |
| 2001:df2:8e00::/48 | APNIC | Valid |
| 2402:f5c0::/32 | APNIC | Valid |
| 2a13:9500:ee::/48 | RIPE | 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.