bgpreport

Network · data from 2026-11-12

AS147106 Global Erasiber Teknologi

Registry name: IDNIC-GESITNET-AS-ID - PT Global Erasiber Teknologi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS147106, 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.
2401:1fa0::/32 Valid None 1 0%low visibility 2
103.174.236.0/23 Valid Other IRR onlyRADB 673 100% 69
103.174.237.0/24 Valid Other IRR onlyRADB 38 6%low visibility 29
103.174.236.0/24 Valid Other IRR onlyRADB 35 5%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS147106: AS147106:AS-SET-GESITNET. 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 (AS147106 isn't in the set, or no route object for AS147106 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 objectsAS147106 in itNot covered
AS147106:AS-SET-GESITNET 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 5 are in fix.csv.

  • Route object: none1
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2401:1fa0::/32No route object for it. Add a route object with origin AS147106 in the RIR database for the space.1 of 636
Route object: RIR103.174.236.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.174.237.0/24Route object only in RADB. Add it in the RIR database for the space.38 of 673
Route object: RIR103.174.236.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
AS-SET: not foundAS147106:AS-SET-GESITNETPeeringDB names AS147106:AS-SET-GESITNET; no IRR database read has it.

Route objects not announced

Every route object with origin AS147106 is announced.

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.