bgpreport

Network · data from 2026-11-12

AS198010 TelecomMalaysia KINHOSHI COMMUNICATION SDN. BHD

Registry name: TelecomMalaysia KINHOSHI COMMUNICATION SDN. BHD, MY · not in PeeringDB

0IPv4 routes
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
4Route objects not announced registered with origin AS198010, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198010, 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.
2a01:a40::/29 Valid RIR databaseRIPE 629 99% 67

AS-SET

AS198010 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 4 are in fix.csv.

  • Route object: not announced4

Route objects not announced

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

153.76.232.0/21RADB, RIPENo ROA
153.76.232.0/24RIPEInvalid: origin
202.171.40.0/21RADBNo ROA
202.171.40.0/24RADBNo 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.