bgpreport

Network · data from 2026-11-12

AS18115 JGS-AS-AP - JG Group of Companies

Registry name: JGS-AS-AP - JG Group of Companies, PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18115, 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.
115.146.135.0/24 No ROA Other IRR onlyNTTCOM 672 100% 66
27.110.128.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
126.209.42.0/23 Valid RIR databaseAPNIC 672 100% 69
126.209.42.0/24 Valid RIR databaseAPNIC 672 100% 66
126.209.43.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none115.146.135.0/24No ROA covers it. Add a ROA for AS18115, maxLength 24.672 of 673
Route object: RIR115.146.135.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

115.146.128.0/23APNIC, NTTCOM, RADBNo ROA
115.146.128.0/24RADBNo ROA
115.146.129.0/24NTTCOMNo ROA
115.146.132.0/22APNIC, NTTCOM, RADBNo ROA
115.146.132.0/24NTTCOMNo ROA
115.146.133.0/24NTTCOMNo ROA
115.146.134.0/24NTTCOMNo ROA
116.50.147.0/24APNICValid
116.50.148.0/24APNICValid
203.177.228.0/24APNIC, NTTCOMValid

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.