bgpreport

Network · data from 2026-11-12

AS59245 GCORELABSSA-AS-AP - G-Core Labs S.A

Registry name: GCORELABSSA-AS-AP - G-Core Labs S.A, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59245, 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.

153.56.153.0/24 No ROA RIR databaseRIPE 652 97% 66
2a03:90c0:fff0::/44 No ROA RIR databaseRIPE 31 5%low visibility 23
194.77.232.0/23 Valid Other IRR onlyRADB 651 97% 66
31.56.112.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
78.17.225.0/24 Valid RIR databaseRIPE 651 97% 66
152.237.246.0/23 Valid RIR databaseRADB, RIPE 651 97% 66
154.193.154.0/24 Valid RIR databaseAFRINIC, RADB 650 97% 66
154.193.155.0/24 Valid RIR databaseAFRINIC, RADB 650 97% 66
154.193.161.0/24 Valid RIR databaseAFRINIC, RADB 650 97% 66
45.196.163.0/24 Valid RIR databaseAFRINIC, RADB 649 96% 66
195.13.54.0/23 Valid RIR databaseRIPE 649 96% 66
78.111.101.0/24 Valid RIR databaseRIPE 648 96% 66

AS-SET

AS59245 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: none2
  • Route object: RIR1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none153.56.153.0/24No ROA covers it. Add a ROA for AS59245, maxLength 24.652 of 673
ROA: none2a03:90c0:fff0::/44No ROA covers it. Add a ROA for AS59245, maxLength 44.31 of 636
Route object: RIR194.77.232.0/23Route object only in RADB. Add it in the RIR database for the space.651 of 673

Route objects not announced

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

68.164.67.0/24ARIN, RADBValid
87.76.219.0/24RADB, RIPEValid
102.215.226.0/24RADBValid
179.254.211.0/24RADB, RIPEValid
179.254.222.0/24RADB, RIPEValid
187.14.162.0/24RADB, RIPEValid
200.138.17.0/24RADB, RIPEValid
200.180.175.0/24RADB, RIPEValid
213.189.25.0/24RADB, RIPEValid

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.