bgpreport

Network · data from 2026-11-12

AS142395 PT Global Internet Indonesia

Registry name: IDNIC-GII-GNET-AS-ID - PT Global Internet Indonesia, ID · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
6Route objects not announced registered with origin AS142395, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS142395, 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.172.119.0/24 Valid Other IRR onlyRADB 672 100% 67
103.172.118.0/23 Valid Other IRR onlyRADB 669 99% 68
103.172.118.0/24 Valid Other IRR onlyRADB 666 99% 68

AS-SET

PeeringDB's irr_as_set for AS142395: AS142395:AS-GII-G-NET. 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 (AS142395 isn't in the set, or no route object for AS142395 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 objectsAS142395 in itNot covered
AS142395:AS-GII-G-NET In no IRR database read today.

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

  • Route object: RIR3
  • AS-SET: not found1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR103.172.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.172.118.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.172.118.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
AS-SET: not foundAS142395:AS-GII-G-NETPeeringDB names AS142395:AS-GII-G-NET; no IRR database read has it.

Route objects not announced

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

38.124.168.0/24ALTDBNo ROA
101.1.42.0/24ALTDBNo ROA
134.56.96.0/22ALTDBNo ROA
170.250.182.0/24ALTDBNo ROA
173.203.187.0/24ALTDBNo ROA
200.96.252.0/24ALTDBNo 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.