bgpreport

Network · data from 2026-11-12

AS138433 GLOBALSIGN-AS-AP - GMO GlobalSign Pte Ltd

Registry name: GLOBALSIGN-AS-AP - GMO GlobalSign Pte Ltd, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138433, 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.
209.146.58.0/23 No ROA Other IRR onlyRADB 673 100% 67
103.142.236.0/23 Valid RIR databaseAPNIC 673 100% 67
2001:df1:9580::/48 Valid RIR databaseAPNIC 635 100% 69
116.51.29.96/27 Valid RIR databaseAPNIC, NTTCOM 28 4%low visibility 22

AS-SET

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

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none209.146.58.0/23No ROA covers it. Add a ROA for AS138433, maxLength 23.673 of 673
Route object: RIR209.146.58.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS138433 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.