Network · data from 2026-11-12
AS131189 LIVECOMLIMTED-AS-AP - Livecom Limited
Registry name: LIVECOMLIMTED-AS-AP - Livecom Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131189, 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.
| 200.95.189.176/28 | No ROA | None | 1 0%low visibility |
| 103.38.144.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 103.85.212.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 103.198.18.0/23 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 194.6.97.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS131189 isn't in PeeringDB, where networks name their 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 5 are in fix.csv.
- ROA: none4
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.95.189.176/28 | No ROA covers it. Add a ROA for AS131189, maxLength 28. |
| Route object: none | 200.95.189.176/28 | No route object for it. Add a route object with origin AS131189 in the RIR database for the space. |
| ROA: none | 103.38.144.0/24 | No ROA covers it. Add a ROA for AS131189, maxLength 24. |
| ROA: none | 103.85.212.0/24 | No ROA covers it. Add a ROA for AS131189, maxLength 24. |
| ROA: none | 103.198.18.0/23 | No ROA covers it. Add a ROA for AS131189, maxLength 23. |
Route objects not announced
Every route object with origin AS131189 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.