bgpreport

Network · data from 2026-11-12

AS55706 AIGGS-MY - G1 Enterprise 1 Technology Park Malaysia

Registry name: AIGGS-MY - G1 Enterprise 1 Technology Park Malaysia, MY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55706, 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.
167.247.20.0/24 No ROA None 673 100% 67
2620:13f:701a::/47 No ROA None 636 100% 67
167.247.23.0/24 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none167.247.20.0/24No ROA covers it. Add a ROA for AS55706, maxLength 24.673 of 673
Route object: none167.247.20.0/24No route object for it. Add a route object with origin AS55706 in the RIR database for the space.673 of 673
ROA: none2620:13f:701a::/47No ROA covers it. Add a ROA for AS55706, maxLength 47.636 of 636
Route object: none2620:13f:701a::/47No route object for it. Add a route object with origin AS55706 in the RIR database for the space.636 of 636
ROA: none167.247.23.0/24No ROA covers it. Add a ROA for AS55706, maxLength 24.671 of 673
Route object: RIR167.247.23.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

167.247.12.0/22NTTCOM, RADBNo ROA
167.247.12.0/23NTTCOM, RADBNo ROA
167.247.12.0/24NTTCOM, RADBNo ROA
167.247.13.0/24NTTCOM, RADBNo ROA
167.247.14.0/23NTTCOM, RADBNo ROA
167.247.14.0/24NTTCOM, RADBNo ROA
167.247.15.0/24NTTCOM, RADBNo ROA
167.247.16.0/24NTTCOM, RADBNo ROA
167.247.108.0/24NTTCOMNo ROA
167.247.252.0/22NTTCOM, RADBNo ROA
167.247.252.0/23NTTCOM, RADBNo ROA
167.247.252.0/24NTTCOM, RADBNo ROA
167.247.253.0/24NTTCOM, RADBNo ROA
167.247.254.0/23NTTCOM, RADBNo ROA
167.247.254.0/24NTTCOM, RADBNo ROA
167.247.255.0/24NTTCOM, RADBNo ROA
2620:13f:7004::/47RADBNo 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.