bgpreport

Network · data from 2026-11-12

AS136552 COMNet Malaysia

Registry name: PACIFICCOMNET-AS-AP - Pacific Comnet (M) Sdn. Bhd., MY · PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS136552, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136552, 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.92.150.0/24 Invalid: origin Other origin only 1 0%low visibility 1
103.92.148.0/24 Valid RIR databaseAPNIC 673 100% 68
103.92.149.0/24 Valid RIR databaseAPNIC 673 100% 68
210.24.100.0/24 Valid RIR databaseAPNIC 673 100% 68
210.24.101.0/24 Valid RIR databaseAPNIC 673 100% 68
210.24.102.0/24 Valid RIR databaseAPNIC 673 100% 68
210.24.103.0/24 Valid RIR databaseAPNIC 673 100% 68
2400:1700:200::/48 Valid RIR databaseAPNIC 634 100% 69
2400:1700:210::/48 Valid RIR databaseAPNIC 634 100% 69
2400:1700:211::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS136552: AS136552:AS-COMNET. 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 (AS136552 isn't in the set, or no route object for AS136552 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.

NameDatabaseASNsSets Route objectsAS136552 in itNot covered
AS136552:AS-COMNET APNIC 2118 Yes 1

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin103.92.150.0/24ROAs covering it name AS134809, not AS136552. If AS136552 should announce it, add a ROA for AS136552.1 of 673
Route object: none103.92.150.0/24Route objects for it name AS134809. Add a route object with origin AS136552 in the RIR database for the space.1 of 673

Route objects not announced

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

103.92.148.0/23APNICValid
210.24.100.0/22APNICValid
210.24.100.0/23APNICValid
210.24.102.0/23APNICValid
2402:36c0::/32APNICValid

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.